1. centralization of all dns lookups is worrisome
2. Dns should not be handled by applications. It should be handled by the operating system.
I see a lot of people conflating the two in the comments.
1. centralization of all dns lookups is worrisome
2. Dns should not be handled by applications. It should be handled by the operating system.
I see a lot of people conflating the two in the comments.
I disagree. It has become common for the OS to handle DNS globally. This can provide nice cache efficiency/centralized configuration benefits. But it is also much less flexible and unlike e.g. the OS's Certificate Authority Registry there's no update/revocation benefits.
DNS over HTTPS being configurable in the browser gives us more flexibility. For example you want to AdBlock but not risk breaking OS Updates, you want to split-tunnel a VPN connection then pick which resolver for the browser, or you even want to use a different non-"internet"/non-ICANN network only in a single browser/instance you now can. That's powerful.
DNS by the OS is common in 2019. But saying it "should" without explanation isn't a strong argument except towards the status quo.
PS - If you think of a web browser like an "app ecosystem" this line of thinking makes a heck of a lot of sense. The OS is just a host for a sub-"OS" ecosystem. There's a reason browsers already have their own configuration for e.g. web cams, microphones, sound/mute, language, 3D acceleration, and security that already end-run around what the OS is trying to dictate.
I agree with #1 but why it should be managed by the OS?
If you are currently using private DNS server with internal domains and don't know about changes firefox is going to make, firefox will resolve you domains incorectly while all your tools like nslookup and dig will show correct information.
And then when you do figure it out, you will have to go to every single user and help them fix firefox setup. (because most of such small businesses don't have their own AD)
I first though about blocking it at companies firewall level, but thats tricky, because you don't want to break everything else that uses cloudflare.
Example: Say you use hosts file to block porn and other shady sites for your kid, all they have to do is use chrome.
A bug that I cannot reproduce. Chrome follows my HOSTS file fine on Windows 10. But even if it didn't it would still be off-topic.