[dns-operations] Deprecating infrastructure .INT domains
Colleagues, I wanted to draw your attention to an Internet Draft we’ve developed, its goal is to formally deprecate a number of historic “.int” domains that were designated for Internet infrastructure purposes decades ago and appear for all intents and purposes obsolete. After some limited consultation on developing the approach so far, it would be useful to get some additional eyes on it so we have greater confidence there is nothing we’ve missed. You can find the draft at https://www.ietf.org/archive/id/draft-davies-int-historic-01.html It’s a short document, but at its heart we’ve identified the following domains that are referenced in places but seem to be obsolete: atma.int, ip4.int, nsap.int, rdi.int, reg.int, tpc.int Most of these are not delegated in the int zone any longer, but there are lingering references online to them. Thanks in advance for any insight, and apologies if you get this message in duplicate, kim ___ dns-operations mailing list dns-operations@lists.dns-oarc.net https://lists.dns-oarc.net/mailman/listinfo/dns-operations
[dns-operations] azure-dns / edge-global.plcm.vc resolution problems
Dear List Members, I'd like your advice on my dns resolution problems for edge-global.plcm.vc/A When I can successfully resolve it is 1392byte / 84 A or a 1216bytes / 73 A Records answer. But 50% of the requests get SERVFAILs or self referrals (testing from AS8560). Testing from outside AS 8560 with RIPE atlas (see https://atlas.ripe.net/measurements/32509300) looks the same. Using Quad1/8/9 I see these services needing sometimes >2000ms to generate the answer. Thanks Thomas ___ dns-operations mailing list dns-operations@lists.dns-oarc.net https://lists.dns-oarc.net/mailman/listinfo/dns-operations
Re: [dns-operations] DNSviz and G-root: EDNS issue?
On Tue, Oct 12, 2021 at 01:01:08PM -0400, Matthew Pounsett wrote a message of 11 lines which said: > > This might be a known intermittent IPv6 routing issue with DNSviz, do > > you see this problem for v4 and/or v6 ? > > That would show up as a non-answer over IPv6, rather than an apparent > PMTU/EDNS problem. DNSviz (and similar tools) may wrongly diagnose a PMTU problem if there are random losses. 1) Try with bufsize=4096. No answer, because of a random packet loss. 2) Retry with bufsize=1024. Answer received, therefore it must be a PMTU problem. ___ dns-operations mailing list dns-operations@lists.dns-oarc.net https://lists.dns-oarc.net/mailman/listinfo/dns-operations
