4 ms·

> the problem is that DNS providers and any intermediary that can MitM have been applying content filtering at the DNS level. It can also be used to track users

> the problem is that DNS providers and any intermediary that can MitM have been applying content filtering at the DNS level. It can also be used to track users to an extent. DoH is necessary to reduce the set of parties who are able to see what domains you are accessing, in conjunction with ECH. I am my DNS provider. I choose to apply content filtering. DoH just increases the set of parties who see my traffic.

jchw 3y ago
> DoH just increases the set of parties who see my traffic. DNS-over-HTTPS has nothing to do with your traffic being sent to somewhere you didn't intend for it to. If you experienced something like this, it's because some software decided to ignore your configured DNS resolver, which has absolutely nothing to do with DNS-over-HTTPS and is not how it is implemented in all software. If a piece of software wishes to, it can use any name resolver it wants, and bypass the DNS system altogether. You can also run your own DNS-over-HTTPS resolver. It's probably even a good idea to.