2 ms·
> I am inclined to think most users use client-side content blocking, and not DNS-based content blocking, I think you're missing the point, here. A lot of ent
by CarelessExpert 6y ago
> I am inclined to think most users use client-side content blocking, and not DNS-based content blocking,
I think you're missing the point, here.
A lot of enterprises run their own delegating DNS server for a variety of reasons that have nothing to do with ad blocking.
DoH breaks that en masse.
Firefox has always struggled to gain adoption in corporate settings, and this looks like a nail in the coffin .
- shawnz 6y agoIf you control the workstation, you could just set your DNS server by a policy. See: https://github.com/mozilla/policy-templates/blob/master/README.md#dnsoverhttps https://github.com/mozilla/policy-templates/blob/master/READ... Of course that could be easily bypassed, but such a restriction could be easily bypassed by determined employees regardless of whether Firefox natively supports DoH or not. Local intranet sites will still continue to work without any changes because by default it will fall back to the native resolver if DoH can't resolve the domain. So there should be no breakage by default besides for content blocking use cases.