DNS-over-HTTPS Update

blog.mozilla.org

39 points·bzbarsky··9 comments

Some dubious arguments there. Why should I trust Cloudflare? Yes, EDNS client subnet leaks the IP address to the authoritative server of a domain. But in almost all cases, a DNS lookup is followed by a connection to an IP address of that domain anyway, so my IP address will be known by the domain owners.

> .. will check locally if the browser has a Facebook login cookie

I can't believe I read this on Mozilla. I have no cookies - Private windows. What a mess.

> ..portion of our United States-based users in the Release channel will receive the DoH treatment...will use Cloudflare’s DNS-over-HTTPS

That's it. That was the last straw. And thank you for the fish.

Or... you know, you could just disable it in your browser?

Defaults matter. That's what 99.9% will use. Well played, CF

Just like you can disable Windows telemetry, Facebook personalized ads, Google's personalized ads - most people don't and it's actively harmful for their privacy. But I'm not surprised Mozilla has done this, they have ran "experiments" before that hurt people's privacy.

Does anyone know how switching to DNS-over-HTTPS affects adblocker apps on Android like Blockada, DNS66, etc.?

They will break unless DoH is redirected.

Is this good or bad?

It depends on who you ask. I think it’s a major positive because I’m not getting filtered 53 traffic now.

Reply on news.ycombinator.com