Re: Bind 9.2.3 ignores listen on option

> named.conf contains:
>
> options {
> directory "/etc/named";
> listen-on {
> 192.168.0.0/16;
> 127.0.0.1;
> };
> listen-on-v6 { none; };
> allow-query {
> 192.168.0.0/16;
> 127.0.0.1;
> };
> version "Go away!";
> };
>
> Yet the following is logged on startup:
>
> Jan 30 17:58:27 brickwall named[2870]: starting BIND 9.2.3 -u named -t /var/n
> amed/chroot
> Jan 30 17:58:27 brickwall named[2870]: using 1 CPU
> Jan 30 17:58:27 brickwall named[2870]: loading configuration from '/etc/named
> .conf'
> Jan 30 17:58:27 brickwall named[2870]: listening on IPv4 interface lo, 127.0.
> 0.1#53
> Jan 30 17:58:27 brickwall named[2870]: listening on IPv4 interface eth0, 192.
> 168.1.1#53
> Jan 30 17:58:27 brickwall named[2870]: listening on IPv4 interface eth1, 192.
> 168.2.1#53
> Jan 30 17:58:27 brickwall named[2870]: listening on IPv4 interface eth2, 66.5
> 6.20.170#53
> Jan 30 17:58:27 brickwall named[2870]: couldn't add command channel 127.0.0.1
> #953: not found
> Jan 30 17:58:27 brickwall named[2870]: couldn't add command channel ::1#953:
> not found
> Jan 30 17:58:27 brickwall named[2870]: running
> Jan 30 12:58:27 brickwall named: named startup succeeded
>
> You will note that eth2 is used despite not contain in the listen-on option.
> What am I
> doing wrong?

Usually this is because the poster is looking at the wrong
version on named.conf. In this case you should be looking at
"/var/named/chroot/etc/named.conf" or wherever it points, if it
is a symlink, taking into account the chroot call.

--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org