>I believe that with the considerable sleuthing abilities of the IETF >community, we ought to be able to take this initial set of observed data >and treat it as a call to action for the IETF community, for someone to >step forward and tell us *why* those names are in use, are leaking out >to the root name servers, and what the intended use is for these names.
Um, we already know. They're used to name things on private networks, often behind a NAT, and they leak out for random not particularly interesting reasons, such as people taking their laptops on trips which then look for the printer that lives on their office LAN when they're connected to the wifi at a coffee shop. On my home network I have a couple of dozen hosts, what with all the networked printers, phones, tablets, laptops, and so forth, and because I am a lazy guy, I give them names like kindle.lan rather than longer global names. My local DNS cache resolves those names to addresses in 192.168/16. I think that's pretty typical of small business networks. It's useful, but I don't see anything worth standardizing other than don't resolve .LAN on the global Internet. R's, John _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
