A recent change
(specifically 2.0.44-5) removed Fedora’s systemd files and falls back to
dnscrypt-proxy’s installation method for service files instead. However, if
dnscrypt-proxy no longer starts, you may need to follow the
instructions I posted here:
Hi, the latest changes to the RPM removed the systemd files and falls back to
dnscrypt-proxy’s method instead. I ran into this issue myself. Since
dnscrypt-proxy doesn’t overwrite the existing service file, the one
previously shipped with Fedora will cause
dnscrypt-proxy to not start.
/etc/systemd/system/dnscrypt-proxy.service and re-run
dnscrypt-proxy -service install.
Since the RPM no longer uses sockets, you might need to edit the config as well to specify listening addresses:
listen_addresses = ['127.0.0.1:53', '[::1]:53']