To put things in perspective, the special use TLD defined according to RFC 6761 account for about 4% of the traffic seen at the L root, according to https://ithi.research.icann.org/graph-m3.html. Of those, ".local" account for a bit more than 3%, ".localhost" a bit less than 0.5%, and ".invalid" a bit more than 0.25%. The other reserved names see very little traffic.
There are other sources of noise at the root, including traffic to ".home" (more than 2.5%), ".lan" (a bit less than 1%), ".internal", ".ip", ".dhcp" and ".localdomain", each accounting for about 0.5% of traffic. This pales in comparison to the computer generated unique names, which account for 50% of the traffic seen at the root -- about equally spread between generated lengths of 7 to 15 characters. -- Christian Huitema On 8/16/2019 8:59 AM, Steve Crocker wrote: > Ack. Tnx. > > On Fri, Aug 16, 2019 at 11:56 AM Joe Abley <jab...@hopcount.ca > <mailto:jab...@hopcount.ca>> wrote: > > On 16 Aug 2019, at 10:59, Steve Crocker <st...@shinkuro.com > <mailto:st...@shinkuro.com>> wrote: > > > At the risk of revealing that I haven't been following this > thread carefully, I don't understand how a resolver is supposed to > know all of the special names. Resolvers that are configured to > know that invalid, local, onion, and test are special will not > know about the next name that's put on the special list. > > The pragmatic answer right now is that vendors and package > maintainers do a good job with their default configurations. DNS > software tends to get upgraded frequently enough in applications > with significant user bases that this goes some of the distance. > > I can see your point though that there might be some merit in > having a way to retrieve a current list, or at least telling > whether the list you have is up-to-date. I don't know that I think > it's a particularly pressing problem though (I think DNSSEC trust > anchor distribution for the root zone is higher up the priority > list, for example). > > > Joe > > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
