>>>>> "Shane" == Shane Kerr <[EMAIL PROTECTED]> writes:
Shane> Okay, I'll bite. What does it mean to have a PTR record in
Shane> anything other than the in-addr.arpa tree?
It just means there's a PTR record in a zone outside the in-addr.arpa
tree. Whether that has any significance or not depends on whether
something knows to look for that PTR record. For instance a server
might come across it by following a CNAME when resolving a query. This
is how some folk implement simplified RFC2317 style reverse lookups.
Take a look at 6.242.6.62.in-addr.arpa for example.
- Re: Should a nameserver know a... Robert Elz
- Re: Should a nameserver know a... George Michaelson
- Re: Should a nameserver know a... Bruce Campbell
- Re: Should a nameserver know a... Mark . Andrews
- Re: Should a nameserver know a... James Raftery
- Re: Should a nameserver know a... D. J. Bernstein
- Re: Should a nameserver know about itself? Cricket Liu
- Re: Should a nameserver know about itself? Robert Elz
- Re: Should a nameserver know about itself? Shane Kerr
- Re: Should a nameserver know about itse... Cricket Liu
- Re: Should a nameserver know about itse... Jim Reid
- Re: Should a nameserver know about itse... Peter Koch
- Re: Should a nameserver know about itself? Kenneth Porter
- Re: Should a nameserver know about itself? Olaf Kolkman
- Re: Should a nameserver know about itself? itojun
- Re: Should a nameserver know about itself? Mark . Andrews
- Re: Should a nameserver know about itself? Sam Trenholme
