10.in-addr.arpa Forwarder Zone

2012-09-28 Thread Eric R
I have configured a simple forward zone like the following in BIND: zone "3.10.in-addr.arpa" { type forward; forward only; forwarders { 1.2.3.4; } ; }; This is the only zone I have configured. When I query for, as an example, 1.2.3.10.inaddr.arpa (PTR), I expect BIND to

Re: 10.in-addr.arpa Forwarder Zone

2012-09-28 Thread Mark Andrews
In message , Eric R writ es: > I have configured a simple forward zone like the following in BIND: > > zone "3.10.in-addr.arpa" { > type forward; > forward only; > forwarders { 1.2.3.4; } ; > }; > > This is the only zone I have configured. > > When I query for, as an exa

Re: 10.in-addr.arpa Forwarder Zone

2012-09-28 Thread Michael McNally
On 9/27/12 4:06 PM, Eric R wrote: When I query for, as an example, 1.2.3.10.inaddr.arpa (PTR), I expect BIND to query the 1.2.3.4 forwarder and return the response provided by 1.2.3.4. With BIND version 9.6.1-P1, this works as expected. However with version 9.9.1-P3, BIND > does not attempt to

Re: 10.in-addr.arpa Forwarder Zone

2012-09-28 Thread Michael McNally
On 9/28/12 9:38 AM, Michael McNally wrote: Empty zone behavior has changed in 9.9, and the 10.0.0.0/8 zone is part of the changes. You can find a good explanation of the differences in this ISC Knowledge Base article: https://deepthought.isc.org/article/AA-00804 Oh drat -- that's the wron

Re: 10.in-addr.arpa Forwarder Zone

2012-09-28 Thread Eric R
Thank you for the quick responses. I have solved my issue by setting the empty-zones-enable option to no. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org