3 ms·
Because if I do that, then I have to worry about my ISP hijacking the recursive requests it makes.
by josephcsible 4y ago
Because if I do that, then I have to worry about my ISP hijacking the recursive requests it makes.
- jeroenhd 4y agoDNSSEC protects against that for well-configured domains, though you can't assume people put in the effort. You can use ODoH (https://blog.cloudflare.com/oblivious-dns/ https://blog.cloudflare.com/oblivious-dns/) to double-encrypt your DNS requests and forward them through an external server, disconnecting your query from your response, and encrypting your upstream DNS requests. You can pick any relay from this list: https://download.dnscrypt.info/dnscrypt-resolvers/v3/odoh-relays.md https://download.dnscrypt.info/dnscrypt-resolvers/v3/odoh-re... (need to de-base64 them to get the actual domain) and any upstream DOH server you prefer.
- josephcsible 4y ago> DNSSEC protects against that for well-configured domains This isn't effective against DNS-level censorship, though. A DNSSEC validation error is just as effective as a fake NXDOMAIN or bogus IP at keeping me from visiting the correct site.
- jeroenhd 4y agoIt works in the sense that at least you can know your ISP is messing with your DNS. If they mess with DNS, they might as well just block an IP (range), so a DNS alternative probably won't bypass most censorship. You're better off with a decent VPN at that point.
- josephcsible 4y agoI temporarily agree with this, but once TLS ECH gets widely deployed then I won't. I can see an ISP blocking a single domain, but not all of Cloudflare just because it's hosted there.
- tptacek 4y agoAre you wondering whether your ISP is messing with your DNS? Let me help you with that: if you're in North America, your ISP is messing with your DNS.
- sliken 4y agoNo different than using 8.8.8.8. I've been meaning to track which (if any) root servers support DNS over HTTPS/TLS, that seems the ideal solution.