I also had this problem, but I'm on Ubuntu 16.04, so the original solution did not work. However, this page had the solution.
Add DNSStubListener=no in /etc/systemd/resolved.conf and then restart the systemd-resolved service. Now, the built-in dnsmasq should not start automatically.
You will also need to make sure that dns=dnsmasq is commented out in /etc/NetworkManager/NetworkManager.conf, like the previous answer specifies.
Edit
/etc/NetworkManager/NetworkManager.conf
with the following command:gksu gedit /etc/NetworkManager/NetworkManager.conf
Enter in your password when prompted.
Comment out the line
dns=dnsmasq
, so it looks like this:and then restart Network Manager with
Ta-da! You're all set!
If this still does not work for you, like was my case with Ubuntu 16.10. Then check who is using this port with:
And if you for example have "systemd-r", then you have to stop the service with:
I also had this problem, but I'm on Ubuntu 16.04, so the original solution did not work. However, this page had the solution.
Add
DNSStubListener=no
in /etc/systemd/resolved.conf and then restart the systemd-resolved service. Now, the built-in dnsmasq should not start automatically.You will also need to make sure that
dns=dnsmasq
is commented out in /etc/NetworkManager/NetworkManager.conf, like the previous answer specifies.