Upgrading from 9.8.3 to 9.9.4

[Mike Bernhardt]

Thanks for that. I just remembered there was also the change to the db file
having a default raw format on slaves unless specified.

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



On 01/16/14 16:39, Mike Hoskins (michoski) wrote:
> -----Original Message-----
> From: Mike Bernhardt <bernhardt at bart.gov>
> Date: Thursday, January 16, 2014 4:09 PM
> To: "bind-users at lists.isc.org" <bind-users at lists.isc.org>
> Subject: RE: Upgrading from 9.8.3 to 9.9.4
> 
>> 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?
> 
> 
> You don't have to do this.  BIND won't enable the empty zone if you 
> already have it defined.
> 
> 

The problem I was referring to is mentioned in the feedback to this KB
article:

https://kb.isc.org/article/AA-00803/0/Why-are-queries-for-some-PTR-records-n
o-longer-forwarded-since-upgrading-to-BIND-9.9.0.html

Though, from 9.9.4 Release Notes, that's probably addressed by this bug fix:

Fix forwarding for  forward only "zones" beneath automatic empty zones.
[RT #34583]


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