Can we stop emitting an error for managed-keys.bind?
Doug Barton
dougb at dougbarton.us
Wed Jan 25 07:26:52 UTC 2012
On 01/24/2012 23:24, Mark Andrews wrote:
> In message <4F1F98FE.5080006 at dougbarton.us>, Doug Barton writes:
>> Thanks Mark and Evan for the responses. I think that's the right solution.
>>
>> For fun I just tried started named with no options and an empty
>> named.conf. The other error that happens with that (lack of
>> configuration) is:
>>
>> <daemon.warn> named[10741]: Warning:
>> 'empty-zones-enable/disable-empty-zone' not set: disabling RFC 1918
>> empty zones
>>
>> Shouldn't that just be enabled by default? We don't see that in FreeBSD
>> because I disable some by default to include larger covering zones with
>> real zone statements.
>
> BIND 9.9.0 has
>
> 3255. [func] No longer require that a empty zones be explicitly
> enabled or that a empty zone is disabled for
> RFC 1918 empty zones to be configured. [RT #27139]
You guys rock. :)
--
It's always a long day; 86400 doesn't fit into a short.
Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price. :) http://SupersetSolutions.com/
More information about the bind-users
mailing list