DNSCrypt

See also Anonymizing yourself

DNSCrypt is a local DNS resolver and uses elliptic-curve cryptography when passing messages to and from the DNS server—which is extremely useful for mitigating MITM attacks on DNS. It is best used alongside a caching DNS server like Unbound.

Only a few servers are known to currently support DNSCrypt, however, adoption is growing.

Installation

Unix-like

Requirements & dependencies

`--  dev-libs/libsodium
`--  net-libs/ldns
`--  virtual/pkgconfig

Arch users can install dnscrypt-proxy and set it up manually. Gentoo users can easily compile DNSCrypt from scratch from the main repository. Debian users can install it from the package dnscrypt-proxy, but only in testing or unstable.

Building

1. git clone git://github.com/jedisct1/dnscrypt-proxy.git
2. cd dnscrypt-proxy
3. ./autogen.sh
4. CFLAGS="-O3 -march=native" ./configure --prefix=/usr
5. make -jn (where n is the number of threads you want to spawn)
6. sudo make install

Windows

Use SimpleDNSCrypt, it just werks. If it doesn't, go talk to the developer.

iOS

You will need a jailbroken iOS device (>=5.1.1) in order to install DNSCrypt.

1. Download the pre-compiled binary for iOS;
2. Copy the {bin,sbin,share} directories of the archive into the {bin,sbin,share} directories of the device;

Configuration

Linux

If you would rather run the commands yourself at boot time, this section is for you. However, the following step is common amongst all Linux distros: you must edit your /etc/resolv.conf file to look like this:

/etc/resolv.conf

domain home
nameserver <the DNSCrypt you picked for --local-address>
options edns0

Lock it with sudo chattr +i /etc/resolv.conf, and then, either move on to systemd/OpenRC, or run the following script every time you boot up your PC:

sudo dnscrypt-proxy --local-address=<ip>[:port] --daemonize --resolver-address=<Server address> --provider-name=<Provider name> --provider-key=<Public key> --edns-payload-size=4096 --logfile=/var/log/dnscrypt-proxy.log

Note: Be aware that you will need to use a port that is not in use by other programs. The default is 53.

Tip: Security considerations.

systemd

If you didn't remove the systemd depedency, the source distribution includes the dnscrypt-proxy.socket and dnscrypt-proxy.service files. As such, in order to activate them, you need only edit them (to pick the server), place them in /etc/systemd/system and run systemctl enable dnscrypt-proxy.service, and then systemctl start dnscrypt-proxy.

You can check if it's running by issuing systemctl status dnscrypt-proxy.service.

Note: DNSCrypt's systemd socket uses port 53 by default. You can easily change that at will.

Other init

/etc/init.d/dnscrypt-proxy

#!/sbin/runscript

## Note: This shebang may need to be changed to /bin/bash or something
## else depending on what init your system uses.

# This script is Copyright (C) 1999-2014 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2

# Uncomment if you use the System V init
#. /etc/init.d/dnscrypt-proxy

  # $Id$
 
 DNSCRYPT_LOGFILE=${DNSCRYPT_LOGFILE:-/var/log/dnscrypt-proxy.log}
 
 rundir=${rundir:-/var/run/dnscrypt-proxy}
 pidfile=${pidfile:-${rundir}/dnscrypt-proxy.pid}
 rundir=${rundir:-/var/run/dnscrypt-proxy}
 runas_user=${runas_user:-dnscrypt}
 runas_group=${runas_user:-dnscrypt}
 
 depend() {
 	use net
 	before dns
 	after logger
 }
 
 start() {
 	if [ ! -d "${rundir}" ]; then
 		mkdir "${rundir}"
 		if [ -n "${runas_user}" ]; then
 			touch "${DNSCRYPT_LOGFILE}"
 			chown ${runas_user}:${runas_group} "${DNSCRYPT_LOGFILE}"
 			chown -R ${runas_user}:${runas_group} "${rundir}"
 		fi
 	fi
 
 	ebegin "Starting dnscrypt-proxy"
 	start-stop-daemon --start --quiet \
 		--exec /usr/sbin/dnscrypt-proxy \
 		-- \
 		--pidfile="${pidfile}" \
 		--logfile="${DNSCRYPT_LOGFILE}" \
 		--daemonize --user=${runas_user} \
 		--local-address=${DNSCRYPT_LOCALIP}:${DNSCRYPT_LOCALPORT} \
 		--resolver-address=${DNSCRYPT_RESOLVERIP}:${DNSCRYPT_RESOLVERPORT} \
 		--provider-name=${DNSCRYPT_PROVIDER_NAME} \
 		--provider-key=${DNSCRYPT_PROVIDER_KEY}
 	eend $?
 }
 
 stop() {
 	ebegin "Stopping dnscrypt-proxy"
 	start-stop-daemon --stop --quiet --exec /usr/sbin/dnscrypt-proxy
 	eend $?
 }

You will need to make it executable, sudo chmod +x /etc/init.d/dnscrypt-proxy.

This init script will of course require a configuration file, located here /etc/conf.d/dnscrypt-proxy file. Pick two servers (one will work as the fallback server), whilst making sure they are compatible with the options you will want to use later on (DNSSEC with unbound, for instance), and add the following text:

/etc/conf.d/dnscrypt-proxy

DNSCRYPT_LOCALIP=127.0.0.1
DNSCRYPT_LOCALPORT=40
DNSCRYPT_USER=dnscrypt
 
DNSCRYPT_PROVIDER_NAME=
DNSCRYPT_PROVIDER_KEY=
DNSCRYPT_RESOLVERIP=
 
DNSCRYPT_PROVIDER_NAME=
DNSCRYPT_PROVIDER_KEY=
DNSCRYPT_RESOLVERIP=

DNSCRYPT_OPTIONS="--edns-payload-size=4096"
 
DNSCRYPT_RESOLVERPORT=443

Alternatively, you could use this script to get information directly from the csv file containing the data from /usr/share/dnscrypt-proxy (you would need to move the csv there yourself):

/etc/init.d/dnscrypt-proxy

#!/sbin/runscript

## Note: This shebang may need to be changed to /bin/bash or something
## else depending on what init your system uses.


# Copyright 1999-2014 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2


# Uncomment if you use the System V init
#. /etc/init.d/dnscrypt-proxy

# $Id$

DNSCRYPT_LOGFILE=${DNSCRYPT_LOGFILE:-/var/log/dnscrypt-proxy.log}
DNSCRYPT_RESOLVERS_LIST=${DNSCRYPT_RESOLVERS_LIST:-/usr/share/dnscrypt-proxy/dnscrypt-resolvers.csv}

rundir=${rundir:-/var/run/dnscrypt-proxy}
pidfile=${pidfile:-${rundir}/dnscrypt-proxy.pid}
rundir=${rundir:-/var/run/dnscrypt-proxy}
runas_user=${runas_user:-dnscrypt}
runas_group=${runas_user:-dnscrypt}

depend() {
	use net
	before dns
	after logger
}

start() {
	if [ ! -d "${rundir}" ]; then
		mkdir "${rundir}"
		if [ -n "${runas_user}" ]; then
			touch "${DNSCRYPT_LOGFILE}"
			chown ${runas_user}:${runas_group} "${DNSCRYPT_LOGFILE}"
			chown -R ${runas_user}:${runas_group} "${rundir}"
		fi
	fi

	if [ -n "$DNSCRYPT_RESOLVER_NAME" -a -n "$DNSCRYPT_RESOLVERIP" ]; then
		eerror "You must set exactly one of DNSCRYPT_RESOLVER_NAME or DNSCRYPT_RESOLVERIP!"
		return 1
	elif [ -n "$DNSCRYPT_RESOLVER_NAME" ]; then
		resolver_opts="--resolvers-list=${DNSCRYPT_RESOLVERS_LIST} --resolver-name=${DNSCRYPT_RESOLVER_NAME}"
	elif [ -n "$DNSCRYPT_RESOLVERIP" ]; then
		resolver_opts="--resolver-address=${DNSCRYPT_RESOLVERIP}:${DNSCRYPT_RESOLVERPORT} --provider-name=${DNSCRYPT_PROVIDER_NAME} --provider-key=${DNSCRYPT_PROVIDER_KEY}"
	else
		eerror "You must set exactly one of DNSCRYPT_RESOLVER_NAME or DNSCRYPT_RESOLVERIP!"
		return 1
	fi

	ebegin "Starting dnscrypt-proxy"
	start-stop-daemon --start --quiet \
		--exec /usr/sbin/dnscrypt-proxy \
		-- \
		${DNSCRYPT_OPTIONS} \
		--pidfile="${pidfile}" \
		--logfile="${DNSCRYPT_LOGFILE}" \
		--daemonize --user=${runas_user} \
		--local-address=${DNSCRYPT_LOCALIP}:${DNSCRYPT_LOCALPORT} \
		$resolver_opts
	eend $?
}

stop() {
	ebegin "Stopping dnscrypt-proxy"
	start-stop-daemon --stop --quiet --exec /usr/sbin/dnscrypt-proxy
	eend $?
}

Make sure to substitute where appropriate. You will also have to manually create a user called dnscrypt, with:

/etc/passwd

dnscrypt:x:117:991:/var/empty:/sbin/nologin

You'll also have to create a group:

/etc/group

...
dnscrypt:x:991:

If you're using OpenRC, to activate the init script, issue sudo rc-update add dnscrypt-proxy.

One last alternative is a simplistic and minimalist init.d configuration that declares all the vars in one file:

/etc/init.d/dnscrypt-proxy

#! /bin/sh
### BEGIN INIT INFO
# Provides:          dnscrypt-proxy
# Required-Start:    $local_fs $network
# Required-Stop:     $local_fs
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: dnscrypt-proxy
# Description:       dnscrypt-proxy secure DNS client
### END INIT INFO

# Authors (in part): https://github.com/simonclausen/dnscrypt-autoinstall/graphs/contributors

PATH=/usr/sbin:/usr/bin:/sbin:/bin
DAEMON=/usr/local/sbin/dnscrypt-proxy
NAME=dnscrypt-proxy
ADDRESS=[Proxy IPv4 or IPv6]
PNAME=[Name of Provider]
PKEY=[Key Fingerprint]
LOG=/var/log/dnscrypt-proxy.log
EDNS=4096

case "$1" in
  start)
    echo "Starting $NAME"
    $DAEMON --local-address=127.0.0.1:40 --daemonize --ephemeral-keys --user=dnscrypt --resolver-address=$ADDRESS --provider-name=$PNAME --provider-key=$PKEY --edns-payload-size=$EDNS --logfile=$LOG
    ;;
  stop)
    echo "Stopping $NAME"
    pkill -f $DAEMON
    ;;
  restart)
    $0 stop
    $0 start
    ;;
  *)
    echo "Usage: /etc/init.d/dnscrypt-proxy {start|stop|restart}"
    exit 1
    ;;
esac

exit 0

Mac OS X

Use the dnscrypt-osxclient.

iOS

1. Edit the org.dnscrypt.osx.DNSCryptProxy.plist file to set the resolver name to use, by editing this string <string>--resolver-name=***CHANGETHIS***</string>;
2. Copy the org.dnscrypt.osx.DNSCryptProxy.plist file into /Libary/LaunchDaemons on the device;

To get it working, simply:

1. Reboot or type launchctl load org.dnscrypt.osx.DNSCryptProxy.plist;
2. Change your wifi settings to use 127.0.0.1 as a DNS resolver;
3. Enjoy being less susceptible to MITM attacks whilst on public WiFis.

Additional considerations

Picking a server

One must take a few considerations when picking a server:

• Does it keep logs? Ideally, it shouldn't.
• Is the server located in a country where servers are mandated by law to hold data for over n months? If it is, previous point is moot.
• Does it support the DNSCrypt protocol specification?
• Does it support DNSSEC (assuming you want to use it in conjunction with DNSCrypt, and use Unbound to enforce it)? Highly recommendable. Your security is only as strong as the weakest link.
• Is the latency low enough? Ping it.
• Is the company or individual running the server trustworthy, or do they appear to have ulterior motives?

By default, DNSCrypt's configuration is set to dnscrypt-eu servers, as it is often considered the most trustworthy resolvers. However, if you have no need for DNSSEC support, you can look into the various cryptostorm servers (if you're not in Europe), or the OpenNIC ones, if you'd like to make use of their extra TLDs.

Fallback DNS servers

It is also recommended to add a second, or even a third nameserver (that you know works) to your resolv.conf file. The default maximum you can have is 6, but you can change this number to whatever you want, by hacking MAXDNSRCH and defdname in resolv.h and recompiling the then patched libc. A resolv.conf (with more than 6 nameservers) may look like this.

Note: the fallback servers listed in resolv.conf will NOT go through DNSCrypt, meaning they will not be encrypted and your local network will be vulnerable to DNS spoofing (unless you're visiting a DNSSEC page and using Unbound or something else to enforce it). In order to have DNSCrypt fallback servers, you'll need to run multiple instances of the program.

Sandboxing

It is possible to sandbox DNSCrypt, and even recommended. You can also create an extra user/group to run it, with no privileges, and no home folder for an additional layer of protection.

To sandbox DNSCrypt, simply install firejail, and edit your systemd/OpenRC scripts, adding the prefix 'firejail' before dnscrypt. Firejail comes bundled with a profile for DNSCrypt and many more, which you can analyse, and even edit, by issuing vim /etc/firejail/dnscrypt-proxy.profile.

Troubleshooting

Run hostip example.com. If that outputs an IP, then DNSCrypt is working and the problem lies with whatever DNS cache you're using (most likely Dnsmasq, or Unbound not forwarding the right address/port). If not, then your DNS server might be down, in which case you should ping it, and maybe issue sudo chattr -i /etc/resolv.conf to unlock your resolv.conf, and temporarily change the nameserver to a DNS server of your choice until you fix the issue (not necessary if you have fall-back DNS servers, as you should).

Sometimes, the issue is that NetworkManager edits the resolv.conf file on boot, which would mean you didn't properly lock the file with chattr.

If none of this fixes it, look at /var/log/dnscrypt-proxy.log and figure it out yourself, or are you not a true /g/entooman?

Tip: If you are using Unbound, or another caching DNS server of that sort, it is possible something is wrong with it and thus, you should also visit that program's log file and look for potential errors or warnings.

External links

• DNSCrypt Homepage
• Official project page
• Official DNSCrypt servers
• DNS leak test