Hi,
ok so you don't have an <interface>.dhclient that provides your dns resolution
as provided by dhcp.
Furthermore I see you have a networkmanager config while I have none.
Networkmanager is not in use on Ubuntu Server, but on Desktop. So I
assume you are running a [ULK..]Ubuntu Desktop edition while running
into this issue?
Also just to confirm your system gets its IP and DNS infos via dhcp is that
correct?
I assume that in your case somehow network manager is soaking that up which
leads to the issue of dnsmasq not being able to find the info when starting up.
This more and more leaves my area of expertise :-/
Adding a networkmanager task as well for now.
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
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
