Upgrading from 9.8.3 to 9.9.4

[Mike Bernhardt]

Sorry for the double post, but I forgot to ask this:
And if it is indeed enabled regardless of my RFC1918 ranges, I would imagine
that for my internal servers which have those ranges, I would want to add
"disable-empty-zone ".";" to my global options? And for my external-facing
server which of course has no RFC1918, I would leave it to the default
setting?

-----Original Message-----
From: Mike Bernhardt [mailto:bernhardt at bart.gov] 
Sent: Thursday, January 16, 2014 1:03 PM
To: 'bind-users at lists.isc.org'
Subject: RE: Upgrading from 9.8.3 to 9.9.4

Am I correct in understanding that the change to "enabled by default" was in
9.9.x, not in 9.8.x? The 9.9.x specifically states that is enabled by
default whereas the 9.8.x documentation does not.

-----Original Message-----
From: Lawrence K. Chen, P.Eng. [mailto:lkchen at ksu.edu]
Sent: Tuesday, January 14, 2014 11:47 AM
To: bind-users at lists.isc.org
Subject: Re: Upgrading from 9.8.3 to 9.9.4

IIRC, The main change I ran into when I upgraded to 9.9.2-P1 (from
9.7.6-P4) was the change in default for empty-zones.  All are enabled by
default, including RFC1918 ranges whether you have any defined or not.

On 01/14/14 12:16, Mike Bernhardt wrote:
> Is there anything I need to know regarding changes in default 
> operation when upgrading from 9.8.3 to 9.9.4? I'm specifically looking 
> for changes that must be addressed in named.conf options in order to 
> keep an upgrade as transparent as possible.
> 
> Thanks,
> 
> Mike
> 
> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to 
> unsubscribe from this list
> 
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
> 

--
Who: Lawrence K. Chen, P.Eng. - W0LKC - Sr. Unix Systems Administrator
For: Enterprise Server Technologies (EST) -- & SafeZone Ally