If I now run a dig command against 127.0.0.1 I get a SERVFAIL error, but the dig against 127.0.1.2 still works. I then configure BIND with the forwarder of 127.0.1.2 and this is where it stops working. I can test that this works with the following command: dig (cisco is pre-defined in the included list of compatible resolvers. I'm executing the following command to start dnscrypt-proxy: dnscrypt-proxy -R cisco -a 127.0.1.2 -d -L /usr/share/dnscrypt-proxy/dnscrypt-resolvers.csv -l /var/log/dnscrypt-proxy -m 6 -p /var/run/dnscrypt-proxy

I do have a zone I need to be able to resolve internally. It's important that the local BIND servers are able to respond to queries for internal DNS as well. My goal is to eventually send my traffic to a VPS I use to then forward to my desired DNS servers. dnscrypt-proxy 1.9.4 (compiled from source with libsodium18 1.0.12)įor testing, I'm just trying to use the OpenDNS resolvers with DNSCrypt.Two Debian Jessie servers with BIND 9.9.5-9, fully patched (using stable branch).I'm trying to leverage DNSCrypt in the wake of the recent changes with ISP laws in the USA.

Opendns dnscrypt disabled