Reverse DNS PTR not working - with Delegation set to us...

[hostmedic]

We have the delegation set for our Reverse DNS

DNS Stuff states
Asking phlshare-one.servername.com. for 200.0-255.xx.xxx.216.in-addr.arpa. PTR record: Reports that no PTR records exist [from 216.xxx.xx.200].

Answer:
No PTR records exist for 216.xxx.xx.200. [Neg TTL=3600 seconds]

Details:
phlshare-one.servername.com. (an authoritative nameserver for xx.xxx.216.in-addr.arpa., which is in charge of the reverse DNS for 216.xxx.xx.200)
says that there are no PTR records for 216.xxx.xx.200.

However our servers do have the entries - and when we dig against them and/or nslookup using them - we get the resolution needed


> 216.xxx.xx.200
Server: ns.ourserver.com
Address: 216.xxx.xx.239

Name: phlshare-one.servername.com
Address: 216.xxx.xx.200

Any suggestions ?

FSM / PSM
and another org have looked @ the issue ---
Keep in mind we have the delegation assigned for all our Class C's over to us.

 

[chirpy]

Have you restricted recursion or other lookups in the options in named.conf? It might be worth opening them back up to test whether any restrictions are the cause.

I know you've said that you have the IP's delegated, but have you checked that your nameservers are listed for the delegations in RIPE/APNIC/ARIN - whichever you use.