[Bug 1670959] Re: systemd-resolved using 100% CPU

Andreas Hasenack andreas at canonical.com
Tue Jul 31 13:22:29 UTC 2018

I don't know what is the use case you guys have that you have to have
dnsmasq and resolvconf installed. Maybe there is none and this is just
an artifact from a release upgrade.

In Bionic, I only have dnsmasq-base (not dnsmasq) installed, and no

Looking at the initscript from dnsmasq, there seem to be a few options to disable it for local dns resolving, like the one suggested in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1670959/comments/32, which I reproduce below:
Added this line to /etc/default/dnsmasq:


Then restarting dnsmasq:

    sudo systemctl daemon-reload
    sudo systemctl restart dnsmasq

That will prevent the code quoted in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1670959/comments/47 from running.

You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.

  systemd-resolved using 100% CPU

To manage notifications about this bug go to:

More information about the Ubuntu-server-bugs mailing list