Reverse DNS Dig returning PTR results only with trace option

[Chris Hills]

On 10/11/09 18:25, Raj Adhikari wrote:
> Now I can do a dig for an hour or so. But again I run into same problem.
> It wont return PTR record unless I explicitly do dig on ns1.cyzap.net.
> Also, the last did showing ns1.cyzap.net as Authority NS for this IP.
> But trace showing ns1.moneytreesystems.com as final sender.
>
> Could someone shed a light on this?

254.63.in-addr.arpa.    86400   IN      NS      NS3.MCLEODUSA.NET.
254.63.in-addr.arpa.    86400   IN      NS      NS1.MCLEODUSA.NET.
254.63.in-addr.arpa.    86400   IN      NS      NS2.MCLEODUSA.NET.
;; Received 112 bytes from 192.42.93.32#53(y.arin.net) in 173 ms

228.134.254.63.in-addr.arpa. 7200 IN    NS      ns1.cyzap.net.
228.134.254.63.in-addr.arpa. 7200 IN    NS      ns2.cyzap.net.
;; Received 90 bytes from 209.253.113.19#53(NS3.MCLEODUSA.NET) in 159 ms

228.134.254.63.in-addr.arpa. 3600 IN    NS      ns2.moneytreesystems.com.
228.134.254.63.in-addr.arpa. 3600 IN    NS      ns1.moneytreesystems.com.
;; BAD (HORIZONTAL) REFERRAL
;; Received 160 bytes from 64.253.181.53#53(ns2.cyzap.net) in 167 ms

You should not chain a delegation in this manner. Either make the 
servers ns1.cyzap.net. and ns2.cyzap.net. authoritative for 
228.134.254.63.in-addr.arpa. or have your ISP change the NS records to 
point directly to ns1.moneytreesystems.com. and 
ns2.moneytreesystems.com. The cyzap servers do not respond with the 
authority bit set ("aa" in dig).

Regards,

Chris