On Sun, Feb 22, 2026 at 1:48 PM John R. Levine via NANOG <nanog@lists.nanog.org> wrote:
But anyway, Verisign talks to registrars, and registrars talk to customers. If a glue record is broken, you need to talk to the registrar that is responsible for it. If we knew what the record was we could easily tell which registrar it is.
hazarding a guess: adns.net looks wonky :( a.gtld-servers.net says: ( for and NS set query) ;; ADDITIONAL SECTION: ns1.adns.net. 172800 IN A 199.5.157.2 ns2.adns.net. 172800 IN A 199.5.157.3 czones1.american-webmasters.net. 172800 IN A 199.5.157.129 czones2.american-webmasters.net. 172800 IN A 199.5.156.253 kovu.adns.net. 172800 IN A 199.5.157.52 nebula.adns.net. 172800 IN A 3.134.129.157 and the first in that list that replies fo dns requests: 3.134.129.157 / nebula.adns.net. says: NS1.ADNS.NET. 3600 IN A 199.5.157.2 NS2.ADNS.NET. 3600 IN A 199.5.157.3 KOVU.ADNS.NET. 3600 IN A 199.5.157.52 NEBULA.ADNS.NET. 3600 IN A 3.134.129.157 QUASAR.ADNS.NET. 3600 IN A 198.180.140.2 NS1.ADNS.NET. 3600 IN AAAA 2602:f813::1:c705:9d02 NS2.ADNS.NET. 3600 IN AAAA 2602:f813::1:c705:9d03 KOVU.ADNS.NET. 3600 IN AAAA 2602:f813::1:c705:9d34 NEBULA.ADNS.NET. 3600 IN AAAA 2600:1f16:ec1:a1b4:767d:df35:b9b9:2581 QUASAR.ADNS.NET. 3600 IN AAAA 2602:f813::1:c6b4:8c02 NONE of the 199.5/16 ips reply at all for dns.. that seems bad :( or at least 'sub optimal'. In that second answer the only not-aws IPv4 address that replies is: 198.180.140.2 -chris (yes this is the 'additional section' content from dig NS @<thing> domain)