Re: Reverse DNS Dig returning PTR results only with trace option

2009-11-10 Thread Raj Adhikari
ig @ns2.cyzap.net -x 63.254.134.177 and then dig -x 63.254.134.177 +trace, it will not give PTR record if it traces to ns1.cyzap.net. That is why sometimes I am getting PTR from trace option and sometimes not. Something is broken here. Thank you, Raj Kevin Darcy wrote: > Raj Adhikari wrote

Re: Reverse DNS Dig returning PTR results only with trace option

2009-11-10 Thread Raj Adhikari
t? Maybe now you understand why most people uses > aliases a la RFC 2317. It's often the lesser of two evils. > > - Kevin > > Chris Hills wrote: >> 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 >>> prob

Re: Reverse DNS Dig returning PTR results only with trace option

2009-11-10 Thread Raj Adhikari
er of the subnet. If a true owner delegates the subnet to its client ISP, can't this ISP again delegate the classless subnet agin to its client ISP? Thank you, Rajendra Adhikari Chris Hills wrote: > On 10/11/09 18:25, Raj Adhikari wrote: >> Now I can do a dig for an hour or so. B

Reverse DNS Dig returning PTR results only with trace option

2009-11-10 Thread Raj Adhikari
Hi Guys, I have a 63.254.134.224/28 delegated from ns1.cyzap.net to ns1.moneytreesystems.com. The dig with trace only shows the PTR record. Surprisingly, it starts acting normal after I do the dig on ns1.cyzap.net. See the dig output below. Here is the output: Simple dig to 63.254.234.228. $ dig -