I've re-read the Chrome instructions at They say "set your OS to use OpenDNS, and then enable Secure DNS in the chrome settings" This suggests that Chrome is going to use your OS's DNS. I've already shown that 146.112.61.106 is the IP of the block page) (Answer: it does a DNS lookup, as it does with any other domain. How does your browser know the IP address for ""? This will *also* work, even if he has a VPN plugin in Chrome (again subject to the caveat that OpenDNS knows about the VPN provider in use) If he further blocks port 853 on his router, he will prevent DoT from working (AKA Android's "Private DNS" setting) (which come to think of it, if the OP was using Chrome on an android device, with private DNS set, then your answer would be worthless even blocking port 53 wouldn't help, because unless he is blocking the proxy/anonymizer category, his "Private DNS" will work)
Thus I assert that, if the OP sets to block proxy/anonymizer, it will prevent Google's (or anyone else's) DOH from working (provided, of course, that OpenDNS has recognized that they are a DOH provider). (first one is there to prove it's the OpenDNS block page) I have proxy/anonymizer blocked in my OpenDNS settings, and gues what? *every domain listed in that thread* is blocked: cloudflare-dns *IS* (one of) their DOH endpoint(s). There used to be a help article that suggested using the proxy/anonymizer cateogry block would block DOH requests I can't seem to find it now, but I didn't come up with that idea on my own suggests that it was a known thing months ago, that the proxy/anonymizer category was blocking DOH requests dns.google *IS* thieir DOH endpoint. My answer will help THOSE users as well as the OP. Your answer does answer the OP's question because the question text specifically mentions "Chrome", however, the question *title* does not, and users of other browsers may come here for an answer as well. Considering that seems to indicate that *ENABLING* secure DNS in Chrome is an "experimental" feature, this would seem like something the OP would know they had done.įurthermore, even with secure DNS enabled in Chrome, if Chrome is set to use Cloudflare's 1.1.1.1 service (as an example), OpenDNS's "proxy/anonoymizer" category *WILL* block it, even if the setting is enabled in Chrome, it won't matter, because is blocked.
0 kommentar(er)
