-
Notifications
You must be signed in to change notification settings - Fork 1k
Configuration Sources
Instead of manually adding servers to the static
section, these can be read from lists. Human-readable lists, with nice descriptions, and the corresponding stamps.
Here is an example of such a list: https://download.dnscrypt.info/dnscrypt-resolvers/v2/public-resolvers.md
Which is even more readable once rendered as Markdown: https://github.com/DNSCrypt/dnscrypt-resolvers/blob/master/v2/public-resolvers.md
What is the point of these lists?
First, you don't have to manually enter names and stamps any more. In fact, the [static]
section is generally useless unless you run your own servers.
dnscrypt-proxy
can download lists, verify them, and automatically download updates. All the resolvers defined in a list can then be used just by adding their name to the resolver_names
property.
For example, the public-resolvers
list above is loaded by the example configuration file. So you can use any resolver names it contains without having to provide any other information. This, for example, should work out of the box:
resolver_names = ['scaleway-fr', 'cloudflare']
In somecases if you want to run dnscrypt-proxy as a non-root user you'll get the error "[FATAL] listen udp 0.0.0.0:53: bind: permission denied"
to solve this problem you can run the following command and allow dnscrypt to have access to a low level port :
sudo setcap cap_net_bind_service=+ep $(which dnscrypt-proxy)
- Home
- Installation
- Configuration
- 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