diff options
Diffstat (limited to 'network/dnscrypt-proxy/README.Slackware')
| -rw-r--r-- | network/dnscrypt-proxy/README.Slackware | 34 |
1 files changed, 18 insertions, 16 deletions
diff --git a/network/dnscrypt-proxy/README.Slackware b/network/dnscrypt-proxy/README.Slackware index 6af60acaab..b5a6388c56 100644 --- a/network/dnscrypt-proxy/README.Slackware +++ b/network/dnscrypt-proxy/README.Slackware @@ -1,21 +1,22 @@ A. Setup An init script and configuration file have been provided to run dnscrypt-proxy -as a daemon. To configure dnscrypt-proxy, edit /etc/dnscrypt-proxy.conf with -the desired settings. By default dnscrypt-proxy will use a random DNS server -and will run on localhost (127.0.0.1), port 53. +as a daemon. To configure dnscrypt-proxy, edit +/etc/dnscrypt-proxy/dnscrypt-proxy.toml with the desired settings. By default +dnscrypt-proxy will use a random DNS server and will run on localhost +(127.0.0.1), port 53. -The configuration file is setup to use a dnscrypt user by default, and to -chroot into that user's home directory to maximize security. In order to use -the default configuration you should create a dnscrypt user and group with the -following commands: +The configuration file is setup to use a dnscrypt user by default. In order to +use the default configuration you should create a dnscrypt user and group with +the following commands: groupadd -g 293 dnscrypt useradd -u 293 -g 293 -c "DNSCrypt" -d /run/dnscrypt -s /bin/false dnscrypt -If you decide to use another user you should edit the CHROOTDIR option in -/etc/default/dnscrypt-proxy and the User setting in /etc/dnscrypt-proxy.conf -(there are example settings provided for the user 'nobody'). +If you decide to use another user you should edit the USER setting in +/etc/default/dnscrypt-proxy and the user_name setting in +/etc/dnscrypt-proxy/dnscrypt-proxy.toml (there are example settings provided +for the user 'nobody'). In order to send all DNS requests through dnscrypt-proxy, you will need to update /etc/resolv.conf to point to localhost. If using dhcpcd, the easiest way @@ -44,13 +45,14 @@ To properly stop dnscrypt-proxy on system shutdown, add the following to B. DNS Cache -dnscrypt-proxy provides limited control over how it caches DNS queries. In -order to minimize the number of external DNS lookups, you can also run a local -caching DNS server. A sample configuration for dnsmasq (included with -Slackware) is provided at /usr/doc/dnscrypt-proxy-@VERSION@/dnsmasq.conf. A -sample configuration for bind/named that also does local DNSSEC validation (if +dnscrypt-proxy provides control over how it caches DNS queries via its +configuration file. However, you can also run your own local caching DNS +server. A sample configuration for dnsmasq (included with Slackware) is +provided at /usr/doc/dnscrypt-proxy-@VERSION@/dnsmasq.conf. A sample +configuration for bind/named that also does local DNSSEC validation (if supported by the upstream DNS server) is also provided at /usr/doc/dnscrypt-proxy-@VERSION@/named.conf. Both configurations run on port 53, forwarding lookups to dnscrypt-proxy running on port 55. In order to use these configurations you will need to change the port dnscrypt-proxy runs on in -/etc/dnscrypt-proxy.conf. +/etc/dnscrypt-proxy/dnscrypt-proxy.toml. If you perform your own DNS caching, +it makes sense to disable dnscrypt-proxy's caching in its configuration file. |