DNSCrypt Protocol VS Simple DNSCrypt

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

You could also use dnscrypt-proxy (or Simple DNSCrypt for a GUI) with custom blocklists to prevent known malicious sites from loading. Source: over 1 year ago

That or just install Simple-DNSCrypts or just enabling DNS-Over-HTTPS. Source: over 1 year ago

You can try encrypting your DNS request through Simple DNSCrypt (https://simplednscrypt.org/) and see if that fixes the issue. Source: about 2 years ago

So I've opted for dnscrypt which encrypts the DNS traffic. Source: about 2 years ago

For Windows users can use SimpleDNSCrypt for easier setup. Source: about 2 years ago