As a temporary workaround until this gets proper handling/fix you might (depending on preference and on how static or not your config is): a) switch back from resolved to dnsmasq as described in [1], you need to follow both answers since you are also running Network Manager b) set your DNS address in a file in /etc/resolvconf/resolv.conf.d/ c) we understand why/how NetworkManager is stopping/avoiding dhclient to place the info as it had doen for me in /run/resolvconf/interface/eth0.dhclient and fix that. The update hook should be /etc/dhcp/dhclient-enter-hooks.d/resolvconf
[1]: https://askubuntu.com/questions/898605/how-to-disable-systemd-resolved-and-resolve-dns-with-dnsmasq -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1688364 Title: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1688364/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
