Reverse Lookups with Forwarders

[btb at bitrate.net]

On Jul 12, 2013, at 09.14, sumsum 2000 <sum2hike at gmail.com> wrote:

> Along the same lines as that of ipv4 address: 
> i have the following zone  file  configuration for reverse lookup: 
> 
>   Goal: 192.168.100.128/26  to be directed to 10.213.246.15
> 
> In this, the network part it 192.168.100.128 and  
> network range is 191.168.100.129 - 191.168.100.190
> 
> in this specific case, this is what i end up with zone file configuration:
>                         zone "128.100.168.192.in-addr.arpa" IN {
>                                 type forward;
>                                 forwarders {10.213.246.15;};
>                                 forward only;
>                         };
> 
> In other cases, where my network is 192.168.100,  the configuration is as follows and this works
>                         zone "128.100.168.192.in-addr.arpa" IN {
>                                 type forward;
>                                 forwarders {10.213.246.15;};
>                                 forward only;
>                         };
> 
> 
>  
> When i do a dig  -x  191.168.100.129  it does not go to the configured DNS.

please don't hijack existing threads for your questions, even if they're similar.

if you declare a zone for 128.100.168.192.in-addr.arpa, that is only for the single ip address 192.168.100.128.  nothing else [e.g. not 191.168.100.129].  for netblocks smaller than /24, you'll need to use classless arpa delegation.  see rfc 2317 for details on this concept.  also please make note of the paragraph at the end of section 4 suggesting you not actually use "/" as is used in the examples.  too many people seem to miss this.

-ben