Do we have any sense of why so many .local queries are escaping? On Mon, Aug 15, 2022 at 01:09 Christian Huitema <[email protected]> wrote:
> > On 8/14/2022 8:28 PM, Tim Wicinski wrote: > > On Sun, Aug 14, 2022 at 11:16 PM John Levine <[email protected]> > <[email protected]> wrote: > > > It appears that Tim Wicinski <[email protected]> <[email protected]> said: > > -=-=-=-=-=- > > as someone who looks at lots of caching resolver logs, you could add > > .local > > to this. > But even those query loads are not what I consider a problem . > > It's not the query loads, it's the data leakage. I gather that the stuff > that leaks out to public DNS .CORP queries is quite amazing. > > R's, > John > > > > Yes, I agree, and the .local data leakage has become enough > of an issue that it is being addressed. > > According to the stats published here ( > https://ithi.research.icann.org/graph-m3.html), the following names are > among the most frequently seen at the ICANN Managed Root Servers: > > .local: 7.3% > .internal: 4.1% > .home: 1.7% > .dhcp: 1.5% > .bbrouter: 1.4% > .ctc: 1.1% > > The numbers here are % of traffic seen at the root, as in, "out of 100 > queries to the root, on average 7.3 will be for <something>.local". > > .corp is also visible, but with 0.3% of root traffic it ranks 13th among > the top leaked domains. .onion is barely visible, with 0.01% of root > traffic. > > -- Christian Huitema > > > _______________________________________________ > DNSOP mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dnsop >
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
