Date: Wed, 11 Jul 2007 10:16:04 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Michael Butler <imb@protected-networks.net>, stable@freebsd.org, Jeremy Chadwick <koitsu@FreeBSD.org> Subject: Re: bind: unknown option Message-ID: <46951054.8030602@FreeBSD.org> In-Reply-To: <20070711145330.GA14435@eos.sc1.parodius.com> References: <4694E56E.2030302@protected-networks.net> <20070711145330.GA14435@eos.sc1.parodius.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46951054.8030602>
