Up until recently, I've used it with quad9 DNS, which is fine, but as people found out, we can make it work with dnscrypt-proxy, which allows us to use DNSCrypt, which basically is a protocol that encrypts, authenticates and optionally anonymizes communications between a DNS client and a DNS resolver. It prevents DNS spoofing. It uses cryptographic signatures to verify that responses originate from the chosen DNS... Source: about 1 year ago

DNSCrypt (open source) can use a blacklist https://dnscrypt.info/. Source: about 1 year ago

If I wasn't doing all that, I would probably just stick with something like DNScrypt. Source: over 1 year ago

Https://dnscrypt.info/ - Totally free and fun but intense bunch of programs. If you are willing to learn, its ready and waiting, unrestricted and free. The guides are easy and after a good sitting you will have the confidence needed to surf. - Source: dev.to / over 1 year ago

Running your own local recursive caching DNS resolver is always good. Something like a Pihole for home networks works well. You can also host your own DNS resolver on a VPS, and then connect to it using DNSCrypt. Source: over 1 year ago

Which DNS do you use for your external queries? We like to use a shadow DNS setup where Windows Server DC's do most of the local lookups but they reference another local server running Simple DNS Plus which handles anything external (both outgoing and incoming as we host our own DNS records); it has some nice performance / security features and helps insulate our DCs. Ultimately though we use Google / Quad9 for... Source: over 1 year ago