DNScrypt-proxy 1.6.2, new configuration

Tue, 18 Aug 2015 17:24:15 +0000

The latest version of DNScrypt-proxy does not use anymore a single configuration file (/etc/conf.d/dnscrypt-proxy) but instead completely relies on systemd.
Configuration is now split in two different files.

[root@arch ~]# cat /etc/systemd/system/multi-user.target.wants/dnscrypt-proxy.service
---
[Unit]
Description=DNSCrypt client proxy
Requires=dnscrypt-proxy.socket

[Install]
Also=dnscrypt-proxy.socket
WantedBy=multi-user.target

[Service]
Type=simple
NonBlocking=true
ExecStart=/usr/bin/dnscrypt-proxy \
 --resolver-address=185.97.7.7:27015 \
 --provider-name=2.dnscrypt-cert.fvz-rec-de-fra-01.dnsrec.meo.ws \
 --provider-key=9FCC:EB74:6856:238D:AC57:428B:DE4F:D9C6:E736:5370:E9F9:5415:3BD3:6EBE:A8C2:FAFE \
 --user=nobody

…and…

[root@arch ~]# cat /etc/systemd/system/dnscrypt-proxy.socket
---
[Unit]
Description=dnscrypt-proxy listening socket
After=network.target

[Socket]
ListenStream=127.0.0.2:53
ListenDatagram=127.0.0.2:53

[Install]
WantedBy=sockets.target

pdnsd automatic startup Arch Linux

Sat, 30 Aug 2014 11:01:53 +0000

I have this Arch Linux based ODROID-U3 I use as DLNA server, local web server…etc…and also as local DNS caching server.
For some strange reason pdnsd doesn’t seem to start correctly on Arch Linux.

[root@server ~]# systemctl status pdnsd -l
● pdnsd.service - proxy name server
 Loaded: loaded (/usr/lib/systemd/system/pdnsd.service; enabled)
 Active: failed (Result: exit-code) since Sat 2000-01-01 20:02:07 CET; 14 years 7 months ago
 Process: 182 ExecStart=/usr/bin/pdnsd (code=exited, status=3)
 Main PID: 182 (code=exited, status=3)

Jan 01 20:02:06 server systemd[1]: Starting proxy name server...
Jan 01 20:02:06 server systemd[1]: Started proxy name server.
Jan 01 20:02:06 server pdnsd[182]: Error in config file (line 11): Failed to get IP address of eth0: Cannot assign requested address
Jan 01 20:02:07 server systemd[1]: pdnsd.service: main process exited, code=exited, status=3/NOTIMPLEMENTED
Jan 01 20:02:07 server systemd[1]: Unit pdnsd.service entered failed state.

Adding After=network-online.target and Wants=network-online.target in the Unit section of the startup script doesn’t seem to make any difference.
So far the only workaround which really works is adding the line After=multi-user.target in the service script.

Arch Linux on nagg.eu

DNScrypt-proxy 1.6.2, new configuration

pdnsd automatic startup Arch Linux