Package: dnscrypt-proxy
Version: 1.6.1-1
Severity: normal
# What local IP the daemon will listen to, with an optional port.
# The default port is 53. If using systemd, this is not used and must be
# specified in dnscrypt-proxy.socket.
#DNSCRYPT_PROXY_LOCAL_ADDRESS=127.0.0.1:2053
DNSCRYPT_PROXY_LOCAL_ADDRESS=127.0.0.2:3053
# Remote DNS(Crypt) resolver.
# You can find a list of resolvers at
# /usr/share/dnscrypt-proxy/dnscrypt-resolvers.csv.
DNSCRYPT_PROXY_RESOLVER_NAME=dnscrypt.eu-dk
#DNSCRYPT_PROXY_RESOLVER_NAME=dnscrypt.org-fr
# Extra flags to pass to dnscrypt-proxy
DNSCRYPT_PROXY_OPTIONS="--edns-payload-size=4096 --ephemeral-keys"
with the above, the resolver local address above is not used, but still
the default one from init.d is used instead - 127.0.2.1:53
# What local IP the daemon will listen to, with an optional port.
# The default port is 53. If using systemd, this is not used and must be
# specified in dnscrypt-proxy.socket.
DNSCRYPT_PROXY_LOCAL_ADDRESS=127.0.0.1:2053
DNSCRYPT_PROXY_LOCAL_ADDRESS=127.0.0.2:3053
# Remote DNS(Crypt) resolver.
# You can find a list of resolvers at
# /usr/share/dnscrypt-proxy/dnscrypt-resolvers.csv.
DNSCRYPT_PROXY_RESOLVER_NAME=dnscrypt.eu-dk
DNSCRYPT_PROXY_RESOLVER_NAME=dnscrypt.org-fr
# Extra flags to pass to dnscrypt-proxy
DNSCRYPT_PROXY_OPTIONS="--edns-payload-size=4096 --ephemeral-keys"
is it possible to use 2 resolvers concurrently with the service?
if not, please accept feature request
the above gives the error below:
$ sudo service dnscrypt-proxy status
● dnscrypt-proxy.service - DNSCrypt proxy
Loaded: loaded (/lib/systemd/system/dnscrypt-proxy.service; enabled;
vendor
preset: enabled)
Active: failed (Result: start-limit) since Wed 2016-02-17 17:11:31 AEDT;
2min 6s ago
Docs: man:dnscrypt-proxy(8)
Process: 31144 ExecStart=/usr/sbin/dnscrypt-proxy --resolver-
name=${DNSCRYPT_PROXY_RESOLVER_NAME} $DNSCRYPT_PROXY_OPTIONS (code=exited,
status=0/SUCCESS)
Main PID: 31144 (code=exited, status=0/SUCCESS)
Feb 17 17:11:31 systemd[1]: Started DNSCrypt proxy.
Feb 17 17:11:31 systemd[1]: dnscrypt-proxy.service: Service hold-off time
over, scheduling restart.
Feb 17 17:11:31 systemd[1]: Stopped DNSCrypt proxy.
Feb 17 17:11:31 systemd[1]: dnscrypt-proxy.service: Start request
repeated too
quickly.
Feb 17 17:11:31 systemd[1]: Failed to start DNSCrypt proxy.
Feb 17 17:11:31 systemd[1]: dnscrypt-proxy.service: Unit entered failed
state.
Feb 17 17:11:31 systemd[1]: dnscrypt-proxy.service: Failed with result
'start-
limit'.
Feb 17 17:12:30 systemd[1]: Stopped DNSCrypt proxy.
-- System Information:
Debian Release: stretch/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.3.0-1-amd64
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages dnscrypt-proxy depends on:
ii adduser 3.113+nmu3
ii init-system-helpers 1.24
ii libc6 2.21-7
ii libsodium18 1.0.8-5
ii libsystemd0 228-6
dnscrypt-proxy recommends no packages.
Versions of packages dnscrypt-proxy suggests:
pn resolvconf <none>
-- Configuration Files:
/etc/default/dnscrypt-proxy changed:
DNSCRYPT_PROXY_LOCAL_ADDRESS=127.0.0.2:3053
DNSCRYPT_PROXY_RESOLVER_NAME=dnscrypt.eu-dk
DNSCRYPT_PROXY_OPTIONS="--edns-payload-size=4096 --ephemeral-keys"
-- no debconf information
