Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • Thank you so much for the detailed response! I'm testing a solution based on your recommendations and updating my question accordingly with additional detail (adding a "Follow-up" section). The changes I've made seemed to make a difference which I'll describe above. I'm going to run things for a little bit to see how it behaves over time (since this has been an intermittent issue). If everything checks out, the bounty is absolutely yours! Commented Jan 19, 2018 at 10:09
  • Still experiencing CPU spikes - the difference I noticed initially was just misinterpreted. I've added as much detail regarding all of this in the Folllow-up section above. Commented Jan 19, 2018 at 10:35
  • Also -- I discovered that when I restart dnsmasq, journalctl -f shows me "no servers found in /run/dnsmasq/resolv.conf, will retry". So, I decided to see what the contents of that file were and it is nameserver 127.0.0.53. Commented Jan 19, 2018 at 10:43
  • Preliminary update: I've replaced the contents of /run/dnsmasq/resolv.conf with nameserver 127.0.0.1 and the output of journalctl -f only shows 127.0.0.1 now. No CPU spiking since doing it and wildcard DNS is still functioning. I will update after I've let it run like this for a little bit. Commented Jan 19, 2018 at 10:51
  • With the info here, I was able to solve this issue! Please see "Update #3" in my question above for more detail. Bounty will be available in 15 hours at which point I will award it to you. Thank you again for your help!! Commented Jan 19, 2018 at 11:58