This proposal doesn't solve this problem. Rather, it solves the problem of e.g. your ISP intercepting, logging and/or modifying your DNS request.
The solution will then just be to run your own DoH endpoint / proxy.
[0]: https://arstechnica.com/tech-policy/2009/08/comcasts-dns-red...
So does DNS over TLS (DoT). But the Mozilla folks don't seem to be interested in implemented that for some reason.
Right now I have my own dns configuration on my router, and any device that connects to the router is automatically using this dns. With DOH this doesn't seem to be the case though. I'll need to go and change the settings for each device to use my own DOH proxy. But whether I'll be allowed to do so is quite unclear if you ask me.
Becauae what happens when chrome says : "we have you covered, it's best to use only our DNS over HTTPS. If you need something else you can buy enterprise subscription"
But I think what they need is screw all of us, in a way which we won't resist much because it's for our own good.
This could have been DNS over TLS, or any other form of encryption. But it is DNS over HTTPS. This makes sense only for a browser, because they have the https stack already. But if we are talking about libc, it's very different story, there is no Http, let alone HTTPS there.
Yes some middle parties won't be able to tamper with my DNS queries. At what price? Total control for the people providing the DOH endpoints. So chrome for sure will be using Google DNS for this, and with their efforts to remove ad blocking this fits nicely that you won't be able to use simply DNS based blocker.