On 21. 08. 26 12:44, Gert Doering wrote:
Hi,
On Thu, Aug 20, 2026 at 10:06:32AM +0200, Anand Buddhdev wrote:
Most parties managed to update the address records. However, these 4
ccTLDs did not manage to update the glue records, despite all our
frequent and vigorous efforts to reach them by email, phone and regional
contacts. We also opened requests with IANA to update the glue records,
but without approval from the ccTLD contacts, the requests cannot be
processed. Ultimately the ccTLDs are responsible for maintaining the
correct glue records in the root zone.
I'm not really a DNS person, I just sometimes pretend to be one.
Here, I am very confused. Why would glue be required for a nameserver
that sits in a different DNS hierarchy? As in, why is the question of
"correct or incorrect glue" relevant at all here?
I do understand the ".net IN NS a.gtld-servers.net. which can only be
resolved with glue" case, but ".ne IN NS ne.cctld.authdns.ripe.net"
should be fine without any glue?
Emphasis on "should". In theory it is not needed. In practice for some
TLDs resolving their out-of-domain name servers involved delegation
cycles and these are not resolvable without glue. (E.g. cd TLD in 2025.)
Side note: Traditionally permissibility of glue was determined by the
owner zone which contains the delegation - for TLDs the root. I.e. for
TLD any glue goes.
Side note 2: I'm not saying it is a good idea, but it is like that for
last ~ 40 years.
--
Petr Špaček
-----
To unsubscribe from this mailing list or change your subscription options,
please visit: https://mailman.ripe.net/mailman3/lists/dns-wg.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
