I just installed pihole, never owned a raspberry pi before. My Linux knowledge is pretty scarce, I just tried to follow the installation guide. It's set to static 192.168.0.125 and I'm using my router as DHCP and have put 192.168.0.125 as DNS. At first I only had StevenBlacks blocklist and tried it out but no ad was blocked on msn.com or cnn.com.
I thought it might be outdated and added some more popular blocklists from Firebog. When I then tried to update gravity I get the error [✗] DNS resolution is currently unavailable.
I also have this error in the pi-hole admin interface:
|2025-03-11 19:06:33|NTP|Error in NTP client:
Cannot resolve NTP server address: Try again|
Also when trying to upload the debug log:
* curl failed, contact Pi-hole support for assistance.
* Error message: curl: (6) Could not resolve host: tricorder.pi-hole.net
[✗] There was an error uploading your debug log.
Please try again or contact the Pi-hole team for assistance.
A local copy of the debug log can be found at: /var/log/pihole/pihole_debug.log
Edit: I later discovered that I had no internet access at all when I removed the secondary DNS server in my router. So when only routing to my pihole DNS I can't access the internet. I removed the pihole DNS and put it back to 8.8.8.8 and now I could upload the debug log after using sudo pihole -d
## Expected Behaviour:
Update gravity without error and no errors when uploading. Being able to access internet when using 192.168.0.125 as the only DNS in my router.
## Actual Behaviour:
[✗] DNS resolution is currently unavailable
No internet access from devices using pihole as DNS.
Unless you are also running unbound on your pi, setting the DNS to itself will not work. Try to go into the pi-hole WebUI and configure a upstream DNS server such as Quad9 or Cloudflare.
If you are using docker, you'll need to put the variables into the container's configuration.
I'm not running Unbound yet. Sorry if I was unclear but I'm using my pi ip as DNS in my router. In my pihole webgui I have checked Cloudflare as upstream DNS. Also no docker.
That's probably because I removed my pi-hole as DNS when I tried to get a debug log. When I used 192.168.0.125 as DNS in my router I could not upload a debug log token.
Now I have changed back to using 192.168.0.125 as DNS and I instantly get this error in Pi-hole interface:
|2025-03-12 14:49:00|NTP|Error in NTP client:
philip@pi:~ $ nslookup tricorder.pi-hole.net
;; communications error to 192.168.0.1#53: timed out
;; communications error to 192.168.0.1#53: timed out
;; communications error to 192.168.0.1#53: timed out
;; communications error to 8.8.8.8#53: timed out
;; no servers could be reached
philip@pi:~ $ nslookup tricorder.pi-hole.net 192.168.0.1
;; communications error to 192.168.0.1#53: timed out
;; communications error to 192.168.0.1#53: timed out
;; communications error to 192.168.0.1#53: timed out
;; no servers could be reached
philip@pi:~ $ nslookup tricorder.pi-hole.net 8.8.8.8
;; communications error to 8.8.8.8#53: timed out
;; communications error to 8.8.8.8#53: timed out
;; communications error to 8.8.8.8#53: timed out
;; no servers could be reached
Trying to upload a picture of how I use my pihole as DNS through my router:
EDIT:
I now changed back my router settings to 1.1.1.1 and manually changed on my phone and PC to use 192.168.0.125 as DNS and it seems to work? When browsing I see querier + queries blocked gradually go up. Maybe the settings I did in the router was wrong? I thought what I did was to make the router give out my Pi-hole DNS to all devices connected.
You are probably correct in assuming this. From the image posted, you put the correct DNS info in the WAN section instead of the LAN. Try looking to see if there is a LAN section and input your Pi-hole IP as the primary DNS server.
It should be in your manual.at support.dlink.com. Take a look at page 51 network section. Leave the DNS relay enable and check out the advance settings and see if it allows you to input your pihole DNS.
