3 ms·
My issue is with browser based DoH is when it defaults to ON. That was Mozilla's original plan for Firefox. That's a problem for those of us who use DNS to red
by WarOnPrivacy 7y ago
My issue is with browser based DoH is when it defaults to ON.
That was Mozilla's original plan for Firefox. That's a problem for those of us who use DNS to reduce the risk from malware, advertising and other invasive technologies. DoH effectively circumvents those protections.
After a crapstorm, Mozilla walked that back and made DoH a user choice. Even better, Firefox queries the use-application-dns.net zone - which (added to a local DNS server) tells Firefox to turn off DoH. This is super helpful for those who use DNS to safeguard networks.
Now, better than DoH and a more elegant solution overall is DNS over TLS (RFC7858), which is simply encrypted DNS. It's the natural next step. Frankly, we all should have been using it for years. It's just beginning to gain support, tho.
As it stands now only a handful of public DNS resolvers support it (Quad9, Cloudflare, Google, someone in Germany). None of the root servers do. Nor do ISPs'.
My approach is to run a local DNS resolver (Unbound) which forwards it's queries over TLS. Local users' queries are plain text but the forwarded (public network) queries are encrypted.