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

[Andreas Hasenack]

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
resolvconf.

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:

    DNSMASQ_EXCEPT=lo

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.
https://bugs.launchpad.net/bugs/1670959

Title:
  systemd-resolved using 100% CPU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1670959/+subscriptions