9.3.0 and ipv6 on linux 2.4.27

R Dicaire rdicaire at comcast.net
Tue Oct 19 19:38:14 UTC 2004


Hi, I've compiled 9.3.0 on a slackware 9.1 box running 2.4.27 kernel.
My configure line is:
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
--with-openssl=/usr/local/ssl --enable-threads --enable-ipv6
--enable-getifaddrs

Bind compiles fine, but when I start it, it doesn't listen on the
specified ipv6 address set in named.conf listen-on-v6 directive.
9.3.0beta4 seemed to work fine, and would bind to the specific ipv6
interface, but the final release of this version that I compiled seems
to just ignore listen-on-v6 altogether, no errors, nothing.

options {
        directory "/etc/named";
        listen-on { 68.47.208.78; 192.168.1.1; };
        pid-file "/etc/named/named.pid";
        allow-recursion { 192.168.1.0/24; ! 0.0.0.0; };
        listen-on-v6 { 3ffe:401d:202b::1000; };
};



Oct 19 15:35:41 rdb named[8528]: starting BIND 9.3.0 -u daemon -t
/var/named
Oct 19 15:35:41 rdb named[8528]: found 1 CPU, using 1 worker thread
Oct 19 15:35:41 rdb named[8533]: loading configuration from
'/etc/named.conf'
Oct 19 15:35:41 rdb named[8533]: listening on IPv4 interface eth0,
68.47.208.78#53
Oct 19 15:35:41 rdb named[8533]: listening on IPv4 interface eth1,
192.168.1.1#53
Oct 19 15:35:41 rdb named[8533]: command channel listening on
192.168.1.1#953

Did I miss something, or is this a legitimate bug?





More information about the bind-users mailing list