On Jun 18 2011, Michael Sinatra wrote:
In theory, you can insert glue records anywhere above the zone in
question. See RFC 2181, section 5.4.1.
As an example, glue for the servers adns1.berkeley.edu and
adns2.berkeley.edu exist in the root zone.
For "fj", "hk", and "xn--j6w193g". These are examples of what some
of the BIND documentation calls "sibling glue".
Of course, at the root zone level, *all* NS records need either
"required glue" or "sibling glue", because every single one of them
is somewhere under the root zone. At least, until the aliens contact
us and we get the Internet spliced into the Galactinet ..
Also, the "required glue" + "sibling glue" desideratum is not always
enough. Consider
foo.com. NS ns1.bar.net.
foo.com. NS ns2.bar.net.
and
bar.net. NS ns1.foo.com.
bar.net. NS ns2.foo.com.
Neither seems to to need glue in either "com" or "net", but without
either the domains cannot be resolved. This was a significant issue
when VeriSign changed the way the *.gltd-servers.net responded last
year.
--
Chris Thompson
Email: c...@cam.ac.uk
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
