Not sure what the benefits of ever having this new service it always seems to break working systems. Next we turn off systemd-resolved, it gets in the way. Sudo systemctl stop dnscrypt-proxy.socket I found using the restart could be problematic. Tell systemd that some files have changed and then stop and restart DNSCrypt. This is what we want as we need to check DNSCrypt is woring okay before adding in dnsmasq. Port 53 it the default port for DNS queries. Here we are changing the default listening IP address, leave the port number at 53. Sudo nano /lib/systemd/system/dnscrypt-proxy.socket Save the file and exit then reload the next file. You can ignore the setting for LocalAddress as it will not be used, or you can comment it out. Even though fvz-anyone is supposed to work from anywhere. Update the line for ResolverName changing the value from fvz-anyone to cisco. To configure DBNSCrypt is reasonably simple to do just a couple of files to update. We want to test out DNSCrypt without dnsmasq to start with. Now dnsmasq is installed we stop the daemon as it will use the same port as DNSCrypt. We start off by installing dnsmasq on its own.
This gives a known good starting point without the bloat of a full desktop install. It works by encrypting all DNS traffic between the user and OpenDNS, preventing any spying, spoofing or man-in-the-middle attacks.”.Īs usual I do all my testing on Virtual machines, using an Ubuntu 18.04 Minimal Server Installation. To quote from the OpenDNS website “DNSCrypt is a piece of lightweight software that everyone should use to boost online privacy and security. dnsmasq is used for local domains and DHCP while we use DNSCrypt as our forwarding DNSD server. This is how I got DNSCrypt and dnsmasq on Ubuntu 18.04 working together.