Reverse Lookups with Forwarders

[sumsum 2000]

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.
Any way, i can get this to be looked up for the correct specified DNS, as
there is distinction between the network and the host configuration for
this specific case.

Could you please help on this.


On Tue, Jul 9, 2013 at 1:03 PM, Matus UHLAR - fantomas <uhlar at fantomas.sk>wrote:

> On 09.07.13 11:51, sumsum 2000 wrote:
>
>> I have a reverse lookup zone file configuration as follows:
>> zone "0/24.110.252.173.in-addr.**arpa" {
>>
> [...]
>
>  When I do dig -x 172.252.110.27, I expect it to forward it to
>> 10.10.96.1, but instead, it uses the default resolver.
>>
> [...]
>
>  So if DNS Server X is configured against this zone
>> , then any reverse DNS request for 173.252.110.0-173.252.110.255
>> should be forwarded via DNS Server X
>>
>
>  Currently this is not the case. There is no forwarding in the above
>> scenario ( where CIDR notation x.x.x.x/Mask is used)
>>
>
> Neither the BIND nor DNS does use the CIDR format.
> the resursive resolution searches for 27.110.252.173.in-addr.arpa which
> does
> NOT belong into 0/24.110.252.173.in-addr.arpa, they are two separate names.
>
> You would have to set up either zone 27.110.252.173.in-addr.arpa or
> 110.252.173.in-addr.arpa.
>
>> Only when the zone file is changed to
>>                        zone "110.252.173.in-addr.arpa" IN {
>>
>> All the requests for
>>
>> 173.252.110.0-173.252.110.255  is forwarded to 10.10.96.1.
>>
>
> Use 110.252.173.in-addr.arpa then. You should be aware that the IP range
> belongs to facebook, as already noted.
>
> --
> Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/
> Warning: I wish NOT to receive e-mail advertising to this address.
> Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
> 99 percent of lawyers give the rest a bad name.
> ______________________________**_________________
>
> Please visit https://lists.isc.org/mailman/**listinfo/bind-users<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<https://lists.isc.org/mailman/listinfo/bind-users>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20130712/ac90fe03/attachment.html>