Created attachment 431182 [details, diff] fix to this bug When I install and run `dnscrypt-proxy-1.6.1' with default configuration, `systemctl status dnscrypt-proxy' reports that `resolver-name' is not specified. I figured out it is because in 1.6.0-r1 ebuild the newer confd file (files/dnscrypt-proxy.confd-1.6.0-r1) started to be used. With this confd the option for DNSCRYPT_RESOLVER_NAME is enabled by default instead of DNSCRYPT_RESOLVERIP while dnscrypt-proxy.service isn't updated accordingly. The fix is to create an additional service file `files/dnscrypt-proxy.service-1.6.0-r1' and use it by default for `>=net-dns/dnscrypt-proxy-1.6.0-r1'. The patch attached should resolve the issue.
I noticed the `dnscrypt-proxy.initd-1.6.0-r1` is updated while `dnscrypt-proxy.service-1.6.0-r1` isn't. Perhaps it's just the maintainer forget to test it for systemd users.
Closing this, 1.6.0-r1 is no longer in tree. since 1.9.5 dnscrypt uses upstream provided systemd unit. Please let me know if you still have the problem after trying 1.9.5 https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0ee515fb8a5ff324983ec37c38ec1e2dc8d7aaa6
