Expected Behaviour:
PiHole properly functioning as expected behaving as current home network's DNS server; normal levels of CPU usage, and no errors.
Actual Behaviour:
This morning logging on my main home PC, DNS wasn't functioning as intended - I could ping out just fine over IP, but DNS was not resolving - I swapped my home router's DNS to point to just Cloudflare (1.1.1.1, 1.0.0.1) for the time being to get functional again, instead of my PiHole instance.
However, even with my router no longer pointing to my PiHole instance, and reboots of the actual Pi itself, the CPU immediately spikes to 100%, even with no client querying the PiHole instance any longer for DNS.
I suspected that it was possible having Conditional Forwarding enabled was causing the issue, so I did disable that, but that did not seem to fix anything.
I also went ahead and tried both repairing and re-installing my PiHole instance using pihole -r, but that also did not alleviate the issue.
Only other items I have really done with this Pi device thus far outside PiHole have been installing Wireguard, and making use of fail2ban, but both of those have been in place for some time - nothing new.
I am able to successfully update Gravity with no issue - tested that a few times now and it seems to update appropriately.
I am also getting the following error on the System tab itself, but searching this error I have not found anything particularly specific to the symptoms I am currently seeing, especially since I do not have my router pointing to the Pi at this time:
There was a problem applying your settings.
Debugging information:
PHP error (2): fsockopen(): unable to connect to 127.0.0.1:4711 (Connection refused) in /var/www/html/admin/scripts/pi-hole/php/FTL.php:47
FTL version: 5.23