Re: RFC 6303 and automatic empty zones

2011-08-20 Thread Chris Thompson
On Jul 14 2011, Evan Hunt wrote: [I wrote] Now that RFC 6303 has been published, and includes the fourteen RFC 1918 reverse zones (section 4.1), can we expect future versions of BIND to have them as automatic empty zones - i.e. the "#ifdef notyet" in b

RE: RFC 6303 and automatic empty zones

2011-07-14 Thread Lightner, Jeff
.@lists.isc.org [mailto:bind-users-bounces+jlightner=water@lists.isc.org] On Behalf Of Evan Hunt Sent: Thursday, July 14, 2011 11:16 AM To: Chris Thompson Cc: bind-users@lists.isc.org Subject: Re: RFC 6303 and automatic empty zones > Now that RFC 6303 <http://www.rfc-editor.org/rfc/rfc6303.txt&

Re: RFC 6303 and automatic empty zones

2011-07-14 Thread Evan Hunt
> Now that RFC 6303 has been > published, and includes the fourteen RFC 1918 reverse zones (section 4.1), > can we expect future versions of BIND to have them as automatic empty > zones - i.e. the "#ifdef notyet" in bin/named/server.c to disappear? Yes.

RFC 6303 and automatic empty zones

2011-07-14 Thread Chris Thompson
Now that RFC 6303 has been published, and includes the fourteen RFC 1918 reverse zones (section 4.1), can we expect future versions of BIND to have them as automatic empty zones - i.e. the "#ifdef notyet" in bin/named/server.c to disappear? -- Chris Tho