3 ms·
Chrome (and derivatives) need to start behaving better: > The motivation for the Google’s Chrome browser to do this is pretty obvious. Many ISPs perform NXDOMA
by throw0101a 6y ago
Chrome (and derivatives) need to start behaving better:
> The motivation for the Google’s Chrome browser to do this is pretty obvious. Many ISPs perform NXDOMAIN substitution in their DNS resolvers and replace the “no such domain” response with a synthetic pointer to their own search page, which allows them to monetize all those No such domain” user typos. From Google's perspective this NXDOMAIN substitution is not well regarded. Search is a major path to advertisement placement and advertising is Google's core revenue. So how can Google's Chrome browser platform detect network environments where NXDOMAIN substitution is happening? Simple. Test the DNS with its own nonce random string queries to see if NXDOMAIN substitution is taking place.
> This supposedly innocuous probe of the DNS should’ve been pretty harmless. But there is a lot of Chrome out there these days. Some two thirds of all browser use in today’s Internet is reported to use the Chrome browser, and the number rises when you include products such as Edge that are based on the Chrome engine. Consequently, it is perhaps unsurprising to learn that according to this report these probes are now taking up some 50% of the total root server traffic (Figure 3).
I understand that hijacking NXDOMAIN is bad, but Google is now 'punishing' the root DNS operators with extra traffic when the actual perps are the bad-actor ISPs. A bit of collateral damage there.
And would it be so bad for Google/Chrome to simply let the NXDOMAIN hijacking slide? They seem to be externalizing costs to help their business model.
- remus 6y ago> And would it be so bad for Google/Chrome to simply let the NXDOMAIN hijacking slide? Yes, it would. It's a workaround to a problem created by shitty ISPs, go after the ISPs if you want to solve the problem.
- throw0101a 6y agoGreat. And what is your idea for to "go after the ISPs"? What does 'going after' them entail? And as someone with a non-shitty ISP, why should I be part of the problem of excess traffic to the root servers?
- JdeBP 6y agoYou need to know a bit of history, namely that one of the earliest "bad actors" here was Verisign, the operator of the com. and net. registry, and of the "A" and "J" ICANN root content servers. * http://jdebp.uk./FGA/verisign-internet-coup.html http://jdebp.uk./FGA/verisign-internet-coup.html
- throw0101a 6y agoHow does Verisign's bad behaviour justify Chrome's bad behaviour? * https://yourlogicalfallacyis.com/tu-quoque https://yourlogicalfallacyis.com/tu-quoque * https://en.wikipedia.org/wiki/Tu_quoque https://en.wikipedia.org/wiki/Tu_quoque
- schoolornot 6y agoWhat's the rationale for not hardcoding Google DNS into Chrome the way Firefox has done with Cloudflare for DoH?
- throw0101a 6y agoSplit-horizon DNS in corporate networks for one: how would Chrome look up internal-only records? (Which is one of the reasons that many sysadmins don't like Firefox's DoH, though not the most important one.)
- schoolornot 6y agoFirefox does a pretty nifty trick to determine whether the computer should use DoH or not. Chrome could do something similar.
- throw0101a 6y agoI prefer not to rely on "nifty tricks" for my internal DNS to work, especially one that may be eventually deprecated.