Date: Sun, 19 Sep 2010 14:37:21 -0400 From: Mark Kamichoff <prox@prolixium.com> To: freebsd-stable@freebsd.org Subject: BIND9 built w/--disable-ipv6 on 8.1-STABLE Message-ID: <20100919183721.GA17616@prolixium.com>
next in thread | raw e-mail | index | archive | help
--0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi -=20 I just noticed (well, via a discussion in #ipv6 on freenode) that the default configure arguments for BIND9 on 8.1 include '--disable-ipv6'. % grep CONFIGARGS /usr/src/usr.sbin/named/Makefile=20 CONFIGARGS=3D'--prefix=3D/usr' '--infodir=3D/usr/share/info' '--mandir=3D/usr/share/man' '--enable-threads' '--disable-ipv6' '--enable-getifaddrs' '--disable-linux-caps' '--with-openssl=3D/usr' '--with-randomdev=3D/dev/random' This results in BIND9 not listening on IPv6 sockets, even if the listen-on-v6 directive is explicitly configured in the configuration file. Even worse, and why I didn't pick up on it until now, is that no warnings or errors are emitted about this during startup, although I suppose that is more of a BIND problem than a FreeBSD one. Strangely enough, the control socket still listens on ::1 in addition to 127.0.0.1. Does anyone know why this was done, or if there's any harm in reenabling it and rebuilding? - Mark --=20 Mark Kamichoff prox@prolixium.com http://www.prolixium.com/ --0OAP2g/MAC+5xKAE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkyWWGEACgkQ0TYC9KtF8BOTawCeJU9F41ZC/HJbrfDdcZsVTMlC cREAn2rSCTG8J+4B3EoceibmJhseESoS =2xjh -----END PGP SIGNATURE----- --0OAP2g/MAC+5xKAE--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100919183721.GA17616>