I have been using Pi-hole for some time without any problems.
My configuration is standard other than I am using Unbound as the upstream DNS resolver.
I recently refreshed my network which involved a change of IP scheme. I changed the static IP configuration on my Raspberry Pi using nmcli.
I can access the Pi-hole admin page from a client, but using that same client I get some strange results. The IP of the Pi here is 192.168.252.254. When querying DNS using the Pi-hole as the server it works for external domains but I cannot resolve "pi.hole".
Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:
Hey @bigfella9852, sorry your debug log expired. We couldn't see anything too obvious in there though. There is a suspicion that if you have any antivirus software installed it's taking over your DNS requests. Some AV software does this to prevent DNS hijacking, but of course they are ironically doing the very same thing themselves.
Are you still seeing a problem? By all means please create a fresh debug log and post the token and I'll have another look and we can explore some tests.
No problem, when I had the issue I switched my DHCP scope to point DNS requests to my firewall until I worked through the issue.
I have since switched it back to the Pihole, and it is working as expected, "pi.hole" also resolves correctly. I am not 100% certain what the cause was, perhaps local client DNS cache?
Okay, interesting, perhaps it was some caching aspect then after all. Whenever I see Pi-hole's IP being interrogated but seemingly not Pi-hole answering, it starts to look like DNS interference. That's more common these days with browsers doing it in-browser, Apple's private relay doing it, anti-virus packages doing it, and even some ISPs doing it, sometimes silently in the name of keeping us safe.
I'm glad it's working now though. If you hit any problems by all means search the forum and docs and post again if needed.
