Yet another reverse DNS problem.

[Mark Andrews]

> I've hit a wall I've never hit before.
> 
> My ISP delegated me reverse DNS for 216.179.125.0/25. Looks like they 
> just created NS records for each IP to point to two of my DNS servers 
> (216.179.125.1 and .3). I created the appropriate zones, etc, but 
> reverse resolution does not work unless one was to query one of my 
> servers directly. dig +trace seems to indicate that my ISP has 
> correctly delegated the IPs to me.

	Really?  NS records take hostnames not IP addresses.

1.125.179.216.in-addr.arpa. 3600 IN     NS      216.179.125.1.
1.125.179.216.in-addr.arpa. 3600 IN     NS      216.179.125.3.
;; Received 98 bytes from 209.94.102.57#53(ns2.bestweb.net) in 741 ms


> Try at home:
> 
> host 216.179.125.35
>    #does not work
> 
> host 216.179.125.35 216.179.125.1
>    #does work
> 
> dig +trace 35.125.179.216.in-addr.arpa
>    # points to 216.179.125.1 and .3
> 
> 
> Recursive vs non-recursive requests: no difference.
> Firewalls: disabling had no effect (grasping at straws) and problems 
> still happen behind the firewall.
> BIND versions: 9.3.0 right now, 9.2.3 didn't work either.
> 
> All other requests seem to go through fine. Its just this zone.
> 
> Anyone got any pointers? (heh.)
> -porkchop
> 
> 
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org