- Checking that your DNS traffic is encrypted
- Automatic Updates
- Server sources
- Combining blocklists
- Public Blocklist and other configuration files
- Building from source
- Run your own DNSCrypt server in under 10 minutes
- DNS stamps specifications
- Windows Tips
- dnscrypt-proxy in the media
- Planned Features
Clone this wiki locally
You can't. Because DNSCrypt is just a specification.
dnscrypt-proxy is a flexible DNS proxy. It runs on your computer or router, and can locally block unwanted content, reveal where your devices are silently sending data to, make applications feel faster by caching DNS responses, and improve security and confidentiality by communicating to upstream DNS servers over secure channels.
- Installation on Windows
- Installation on macOS
- Installation on Linux
- Installation on pfsense
- Installation on Pi-Hole
- Installation on OpenWRT / LEDE
- Installation on Synology
- Installation on OPNsense
- Installation on EdgeOS
- Simple DNSCrypt is a simple management tool to configure dnscrypt-proxy on windows based systems.
- DNSCloak is a full-featured DNSCrypt client for iOS, with filtering, logging, caching, password protection and more. No jailbreak required.
- AdGuard Pro for iOS, Android, macOS and Windows embeds dnscrypt-proxy in a slick user interface.
- dnscrypt-proxy switcher is a plugin for Bitbar on macOS, to control dnscrypt-proxy usage from the menu bar.
- dnscrypt-proxy-android is a Magisk module for Android. Root required.
- Extract and adjust the configuration file dnscrypt-proxy.toml to your needs. In case you started fresh, ensure you backup your modified
Note: You can choose a set of preferred servers in the
# server_names = ['scaleway-fr', 'google', 'yandex']
Change to the servers you would like to use and remove the leading
server_names = ['google', 'cloudflare']
When doing this filters are ignored if you explicitly name the set of resolvers to use
Filters are used when the list is empty, which means
all resolvers from configured sources, matching the filters.
- Make sure that nothing else is already listening to port 53 on your system and run (in a console with elevated privileges on Windows) the
Change your DNS settings to the configured IP address and check that everything works as expected.
./dnscrypt-proxy -resolve example.com
should return one of the chosen DNS servers instead of your ISP's resolver.
- Register as a system service.
Pre-compiled binaries can be verified with Minisign:
(warning: long line, that may require horizontal scrolling if you use a large font. Make sure to copy the whole of it; the last characters are
minisign -Vm dnscrypt-proxy-*.tar.gz -P RWTk1xXqcTODeYttYMCMLo0YJHaFEHn7a3akqHlb/7QvIQXHVPxKbjB5
On Windows, archives are ZIP files, not
.tar.gz files, so use
dnscrypt-proxy-*.zip in the command above.
Assuming that the official package from this repository was installed, here's how to upgrade to a new version:
- Check the change log for configuration files that need to be updated. When in doubt, start over from the example configuration files.
- Check that the new version can properly load the old configuration files:
/path/to/new/dnscrypt-proxy -config /path/to/old/dnscrypt-proxy.toml -check
- Replace the old
dnscrypt-proxyfile with the new one.
- Restart the service.
Are these instructions not clear? Wrong? Insufficient? This documentation page is a Wiki, so you can contribute by improving it!