[dns-operations] All NSs for a TLD being in the TLD itself

Paul Vixie paul at redbarn.org
Fri Oct 25 17:37:43 UTC 2013

> Chris Thompson <mailto:cet1 at cam.ac.uk>
> Friday, October 25, 2013 03:58
> On Oct 25 2013, Andrew Sullivan wrote:
> That depends on whether you think including "sibling glue" [*] is
> mandatory, or at least advisable. All NS records for TLD delegations
> involve either "required glue" if the name is inside the TLD, or
> "sibling glue" if it is inside another TLD. (In theory, it could
> be a name actually in the root zone itself, but of course there
> aren't any such cases.)
> [*] "sibling glue" is what the BIND documentation (e.g. the man page
> for named-checkzone) calls it. It may not be standard terminology.

it's certainly not standard terminology. the goal of sibling glue is to
cover most of the cases where all of A's name servers are in B, and all
of B's name servers are in A. the relaxation is: if the glue is
in-bailiwick for the delegating zone, send it, even if it is not
in-bailiwick for the delegated zone.

it would have been better if the specification outlawed this way of
naming one's nameservers, since there are still cases where zone A
and/or B as described above will be unresolvable. but this is a feeble
attempt at making it work when A and B are "siblings".

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dns-oarc.net/pipermail/dns-operations/attachments/20131025/a06d863a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compose-unknown-contact.jpg
Type: image/jpeg
Size: 770 bytes
Desc: not available
URL: <https://lists.dns-oarc.net/pipermail/dns-operations/attachments/20131025/a06d863a/attachment.jpg>

More information about the dns-operations mailing list