I've noticed that when upgrading to the latest release ( I think from yesterday or today ) , dnscrypt stops working after reboot, if you use any of the options that come commented in the base package. I was using this options:
config dnscrypt-proxy ns1 option address '127.0.0.1' option port '5353' option resolver 'cisco-familyshield' option resolvers_list '/usr/share/dnscrypt-proxy/dnscrypt-resolvers.csv' # ephemeral keys option requires extra CPU cycles and can cause huge system load # option ephemeral_keys '0' # more details at https://github.com/jedisct1/dnscrypt-proxy#public-key-client-authentication # option client_key '/path/to/client_key' **option syslog '1'** ** option syslog_prefix 'dnscrypt-proxy'** ** option query_log_file '/mnt/sda1/dnslogs/dnsqueries.log'** # enable cache may speed up dnscrypt-proxy, see https://github.com/jedisct1/dnscrypt-proxy/wiki/Go-faster **option local_cache '1'** # disable IPv6 may also speed up dnscrypt-proxy, see https://github.com/jedisct1/dnscrypt-proxy/wiki/Go-faster **option block_ipv6 '1'** # Blacklists allow you to block domains, ip, ... see https://github.com/jedisct1/dnscrypt-proxy/wiki/Filtering **list blacklist 'domains:/usr/share/dnscrypt-proxy/dnscrypt-blacklist-domains.txt' 'logfile:/mnt/sda1/dnslogs/dnscrypt-blocked.log'**
I tried several combinations, and for example , running the latest version ( 1.9.5-1 ) , I was able to enable option syslog '1' and option syslog_prefix, but not the others.
Running a dnscrypt-proxy restart logs in the system log something like "plugins are not implemented", and the router is left with no capability to resolve DNS Addresses ( therefore, the whole network goes down )
Not sure how to post this in the maintainer of the package site at github, I would have if I knew how