on Ubuntu 16.10, for some minute after wifi connection,
dnsmasq tend to use almost 150% of CPU.
Is this normal?
Suggested by another Steps of solution
Add the line
sudo nano /etc/default/dnsmasq
Restart dnsmasq via
sudo service systemd-resolved restart
Say Thanks If I helped, It went back to normal and does NOT screw around with other apps, as the previous method DID.
I had the same Problem in 18.04.
dnsmasq tend to loop. I solved it this way:
Add or uncomment the following line in
Create your own
resolv file (
/etc/resolv.personal) to define nameservers. You can use any nameserver here. I took two from OpenNIC.
nameserver 184.108.40.206 nameserver 220.127.116.11
/etc/dnsmasq.conf add or uncomment the following line:
dnsmasq and disable the default resolver:
sudo service dnsmasq restart sudo systemctl stop systemd-resolved sudo systemctl disable systemd-resolved
man systemd-journald; Read
man systemd-resolve; Read
man dnsmasq; Read
Check your log files in
From the little you've said, it looks like a whole bunch of log entries are being made (Investigate why!), and some part of your logging system is trying to resolve "
domain names, IPv4 and IPv6 addresses, DNS resource records or services with the systemd-resolved.service(8) resolver service.". (Read
man 8 systemd-resolved.service.) This "name resolution" is what's taking the time.
Normal? When Linux runs on everything from Systems-On-Chip to members of the Top 50 Supercomputers, what does "Normal" mean?