-
Notifications
You must be signed in to change notification settings - Fork 1k
Installation on Arch Linux
pacman -S dnscrypt-proxy
There are two mutually exclusive ways to start dnscrypt-proxy
: either with systemd socket activation, or the systemd service file.
Note: Make sure to edit your /etc/dnscrypt-proxy/dnscrypt-proxy.toml
accordingly (use an empty set for your listen_addresses
, aka. listen_addresses = [ ]
).
Activate & start the systemd socket (defaults to port 53 for ipv4), which will automatically start the service:
systemctl enable --now dnscrypt-proxy.socket
Note: Make sure to edit your /etc/dnscrypt-proxy/dnscrypt-proxy.toml
accordingly (setup listen_addresses
).
Enable & start the systemd service directly, without using socket activation:
systemctl enable --now dnscrypt-proxy.service
For more on the dnscrypt-proxy
package, refer to its Arch Wiki page. Consider also the forums if you have questions.
Refer to the official systemd manual pages for more on how to work with services and sockets.
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