bind: unknown option
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It seems that the recent updates to /etc/namedb/named.conf cause named on -stable to fail, e.g. named[56153]: starting BIND 9.3.4 -t /var/named -u bind named[56153]: /etc/namedb/named.conf:17: unknown option 'disable-empty-zone' named[56153]: /etc/namedb/named.conf:18: unknown option 'disable-empty-zone' named[56153]: /etc/namedb/named.conf:19: unknown option 'disable-empty-zone' named[56153]: loading configuration: failure named[56153]: exiting (due to fatal error) Perhaps these should be commented out pending an MFC? Michael -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGlOVuQv9rrgRC1JIRAiT8AKC78f5B3dfzUX0byyHfThYZwn8ufgCgkUSM 4C8q5sM2LVMbLHi4/aNqvAI= =X/RT -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bind: unknown option
On Wed, Jul 11, 2007 at 10:13:02AM -0400, Michael Butler wrote: It seems that the recent updates to /etc/namedb/named.conf cause named on -stable to fail, e.g. named[56153]: starting BIND 9.3.4 -t /var/named -u bind named[56153]: /etc/namedb/named.conf:17: unknown option 'disable-empty-zone' named[56153]: /etc/namedb/named.conf:18: unknown option 'disable-empty-zone' named[56153]: /etc/namedb/named.conf:19: unknown option 'disable-empty-zone' named[56153]: loading configuration: failure named[56153]: exiting (due to fatal error) Perhaps these should be commented out pending an MFC? I can confirm this problem as well on RELENG_6. The disable-empty-zone option was introduced in 9.4.1 and isn't available in 9.3.4: http://www.isc.org/sw/bind/view/?release=9.4.1#NOTES * New options: empty-server, empty-contact, empty-zones-enable and disable-empty-zone. Doug, did you test any of this on RELENG_6 before committing? :-) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bind: unknown option
Jeremy Chadwick wrote: On Wed, Jul 11, 2007 at 10:13:02AM -0400, Michael Butler wrote: It seems that the recent updates to /etc/namedb/named.conf cause named on -stable to fail, e.g. named[56153]: starting BIND 9.3.4 -t /var/named -u bind named[56153]: /etc/namedb/named.conf:17: unknown option 'disable-empty-zone' named[56153]: /etc/namedb/named.conf:18: unknown option 'disable-empty-zone' named[56153]: /etc/namedb/named.conf:19: unknown option 'disable-empty-zone' named[56153]: loading configuration: failure named[56153]: exiting (due to fatal error) Perhaps these should be commented out pending an MFC? I can confirm this problem as well on RELENG_6. The disable-empty-zone option was introduced in 9.4.1 and isn't available in 9.3.4: Right you are, sorry for the confusion. Doug, did you test any of this on RELENG_6 before committing? :-) Yes, of course I tested it. The problem is that I forgot I was also regression testing 9.4.1 on RELENG_6 at the same time. I sent re@ a request last night for guidance on whether to MFC 9.4.1 to RELENG_6. By the end of today I will either do that, or comment out those options in named.conf. Thanks to all who wrote me about this issue. :) Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
