Robert Elz writes: > Whether that happens for in-addr.arpa domains or not I am not sure, but > if you believe the reasoning for doing this (which is largely to force > glue to be provided) then it probably should. Right. If you create a reverse zone in the simplest possible way with tinydns, namely ./add-ns 3.2.1.in-addr.arpa 1.2.3.144, you get 3.2.1.in-addr.arpa. NS a.ns.3.2.1.in-addr.arpa. a.ns.3.2.1.in-addr.arpa. A 1.2.3.144 so that glue is always provided. Unfortunately, neither ARIN nor RIPE supports glue, despite the last paragraph of RFC 1034 section 4.2.2, so reverse lookups on the Internet are unnecessarily rickety. ---Dan
- Re: Checks performed during delega... Mats Dufberg
- Re: Should a nameserver know about itself? James Raftery
- Re: Should a nameserver know about itself? Randy Bush
- Re: Should a nameserver know about itself? Mans Nilsson
- Re: Should a nameserver know about itself? Cathy Murphy
- Re: Should a nameserver know about itself? Mats Dufberg
- Re: Should a nameserver know about itself? Cathy Murphy
- Re: Should a nameserver know about itself? Robert Elz
- Re: Should a nameserver know about itself? Bill Manning
- Re: Should a nameserver know about itse... Robert Elz
- Re: Should a nameserver know about... D. J. Bernstein
- Re: Should a nameserver know about... Shane Kerr
- Re: Should a nameserver know about... bert hubert
- Re: Should a nameserver know about... Robert Elz
- Re: Should a nameserver know about... Bruce Campbell
- Re: Should a nameserver know about... Bill Manning
- Re: Should a nameserver know about... D. J. Bernstein
- Re: Should a nameserver know about... Robert Elz
- Re: Should a nameserver know about... Shane Kerr
- Re: Should a nameserver know about... Robert Elz
- Re: Should a nameserver know about... George Michaelson
