dohot VS dnscrypt-proxy

most ISPs override dns requests done over http, even if they're going directly to root servers. to be sure your ISP isn't logging, you need a DoH server. to be sure the DoH server isn't logging, you need to connect to it through Tor. this known as DoHoT, or DNS over HTTPS over Tor. if you're interested in setting it up, take a look at this: https://github.com/alecmuffett/dohot. bone thing to be aware of when setting this up with pihole is that dnscrypt-proxy listens on the same port 53 as pihole by default, so be sure to change that in the dnscrypt config.

dnns over https over tor is the answer https://github.com/alecmuffett/dohot www.anonymousplanet.org

DoHoT: making practical use of DNS over HTTPS over Tor https://github.com/alecmuffett/dohot

DNSCrypt-proxy (to achieve DoHoT)

Added reference to the DoHoT project in the DNS section https://github.com/alecmuffett/dohot and updated the DNS illustration with this possibility

There is more than one way to do this but I have decided to use dnscrypt-proxy. We will not be using dnscrypt for the dnscrypt protocol though you could elect to use that as the underlying DNS protocol. dnscrypt-proxy lets's us use a SOCKS5 proxy through which the DNS queries will be sent. We will use a Tor SOCKS5 proxy here. You can choose which protocols should be enabled and which ones should be disabled. There are two points:

I tried installing the RPM from the Fedora repos but it's out-of-date and there were no instructions on how to get it operational, so I went with the manual approach as per their wiki: https://github.com/DNSCrypt/dnscrypt-proxy/wiki/Installation-linux

This is awesome, thanks -- going to look into that now. I found SmartDNS interesting and thought I would share it, it's pretty simple to setup. I can see why it's Chinese focused, they have "interesting" internet access over there :-).

I have been looking into DNS quite a bit lately (Unbound, etc), as DNS lookup performance has been pretty subpar lately. I'm in Perth, Australia, and we're pretty remote so our latency is meh at best, and Cloudflare performance has been all over the shop lately, I think they're having issues in WA). DNS can also cause really routing issues here sometimes as we get better latency to Singapore than Sydney, so we might get shunted off to SG.

I've also been using dnscrypt-proxy2 (https://github.com/DNSCrypt/dnscrypt-proxy) for a while, but the above issues with Cloudflares DNS is what triggered me to look into other options.

I use a min-cache-ttl of 15 minutes, which seems to work well.

Thank you for sharing this tip about, looking into this now :).

Sure. I run dnscrypt_proxy behind a pihole. https://github.com/DNSCrypt/dnscrypt-proxy