2 ms·
Those servers are for looking up real domains, they're not designed to be a detection mechanism for malicious actors. Chrome intentionally fires unresolveable u
by jeroenhd 4y ago
Those servers are for looking up real domains, they're not designed to be a detection mechanism for malicious actors. Chrome intentionally fires unresolveable uncacheable domains at the root servers. That's dishonest use of public infrastructure at the very least.
I doubt Google would be happy if Microsoft or Apple were to build a network availability tool into their systems that executes random Google queries that won't get you a result to see if searches are being redirected.
- tptacek 4y agoSays who? The RFCs disagree: just look at all the resource record types. The DNS standards people have been saying for years that the DNS should also be a secure object storage system, because that's a capability DNSSEC brings. Unlike that purely hypothetical use case, this is real people using the DNS roots for an actually important day-to-day function. There's nothing dishonest about what Chrome is doing: it's sending unresolveable uncachable names specifically to avoid ISP DNS servers caching them and tricking users into believing that NXDOMAINs are clean. This isn't Google using a competitor's resources. It's Google's users using core Internet infrastructure. It's core infra for a reason. We're not required to use it parsimoniously. I have the impression that most of the concerned comments on this thread believe that Chrome's NXDOMAIN detection is somehow a burden on the Internet roots. It is not. It's prominent on a graph, and that's all. The Internet roots are, by necessity, designed to handle immense amounts of traffic.