Check RDNS Authority

Hello,

How can I check who is authorative for a reverse DNS IP address? When do an
nslookup on the address from within my own network, I get the reverse ptr but
when I am outside i get the in-addr. AT&T supposedly delegated the reverse
DNS to my DNS server (according to them when I call them). How can I check
who is autorative at the current time for teh IP address?

"Nakie K." <Nakie K.@discussions.microsoft.com> wrote in message
news:48323B78-FCCE-444A-BD6B-...
> Hello,
>
> How can I check who is authorative for a reverse DNS IP address? When do
> an
> nslookup on the address from within my own network, I get the reverse ptr
> but
> when I am outside i get the in-addr. AT&T supposedly delegated the reverse
> DNS to my DNS server (according to them when I call them). How can I check
> who is autorative at the current time for teh IP address?


Jonathan gave you a detailed explanation. You can also simply use nslookup
with the set q=soa switch.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

"J de Boyne Pollard" <> wrote in message
news:88adf7cd-4441-4b0d-9ce1-...
> BM> The easiest way to do this is with the +trace option to dig:
> BM> dig +trace -x <your-IP>
> BM> However, this doesn't follow RFC 2317-style delegation, [...]
>
> The way to do this that I personally find to be the easiest is to
> instrument a resolving proxy DNS server to log all of its queries and
> responses, and just ask it the relevant question then read the
> resultant log entries. (I posted an excerpt from one such log not
> long ago, as a matter of fact.) Of course, this doesn't follow all
> possible paths, but it will use the correct algorithm (which tools
> widely advertised for this purpose, such as "dnstracer", do not).
> Bernstein's "dnstrace" uses the correct algorithm *and* follows all
> possible paths. But I have found in practice that just looking at the
> logs of a resolving proxy DNS server and issuing a few queries
> manually is almost always enough for most purposes.
>
> Some resolving proxy DNS servers largely do this right out of the
> box. I've recently discovered, from an obscure corner of the MSDN,
> that it's possible to configure Microsoft's DNS server to do this,
> too. (M. Fekay, if you're reading this: It's the OperationsLogLevel
> property, documented in the same place as the LameDelegationTtl
> property we were discussing before.) I've not tried it with
> Microsoft's DNS server myself. I tend to just use one of the
> softwares that do it out of the box when I need this capability. (-:


Yes, thanks for pointing that out. The relavent links are:

MSDN 3.1.1.1.1 DNS Server Integer Properties
http://msdn.microsoft.com/en-us/libr...(PROT.10).aspx

MSDN: 7 Appendix B: Product Behavior
http://msdn.microsoft.com/en-us/libr...(PROT.10).aspx

Ace