> > Any domain can have any RR in it. Any time you're tempted to > > generalise based upon domain name, you're almost invariably > > going to be wrong. > > Okay, I'll bite. What does it mean to have a PTR record in anything > other than the in-addr.arpa tree? While in some ways all domains are > equal, can't we at least say that some domains are more equal than > others? :P See RFC 2317, section 5.2. It suggests that, since you're already adding CNAME RRs to an in-addr.arpa zone, e.g., 1.0.168.192.in-addr.arpa. IN CNAME <something> why not make that <something> a domain name in a zone the delegate already owns, e.g., 1.0.168.192.in-addr.arpa. IN CNAME 1.0.customer.example. Then the customer adds 1.0.customer.example. IN PTR foo.customer.example. to his zone data file. Ergo, a PTR RR in what's traditionally considered a forward-mapping zone. cricket
- Re: Should a nameserver know a... Shane Kerr
- 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
