Everything is working fine. However, I have a work laptop (that I use on my home network) that runs a script to check if it is connected to the internet. It does this by pinging 8.8.8.8 However, this does not work in my network (request timed out). I am guessing that pi-hole knows that this is a DNS server and blocks the ping. Disabling blocking does not make any difference.
Is there anything I can do to allow the ping through please?
Being unable to ping would not be a pihole issue but rather a network issue of somekind. You could try running tracert 8.8.8.8 and see where its failing ( assuming you're using Windows ).
Thanks for the reply. I am able to ping OpenDNS and DNS.Watch so it looks like it is only a problem with Google DNS. 192.168.0.1 is my router, and 192.168.0.3 is my pi.hole.
Here is the output
C:\Users\Nick>tracert 8.8.8.8
Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:
1 <1 ms <1 ms 1 ms pi.hole [192.168.0.3]
2 1 ms 1 ms <1 ms 192.168.0.1
3 1 ms <1 ms 1 ms 192.168.0.1
4 2 ms 1 ms * pi.hole [192.168.0.3]
5 2 ms * 6 ms 192.168.0.1
6 * * 6 ms 192.168.0.1
7 * * * Request timed out.
8 4 ms 2 ms * 192.168.0.1
9 * * * Request timed out.
10 3 ms 2 ms 5 ms 192.168.0.1
11 * * * Request timed out.
12 3 ms * * 192.168.0.1
13 3 ms 3 ms * 192.168.0.1
14 * * * Request timed out.
15 10 ms 3 ms 6 ms 192.168.0.1
16 * * * Request timed out.
17 3 ms * * 192.168.0.1
18 * * * Request timed out.
19 8 ms 14 ms * 192.168.0.1
20 * * * Request timed out.
21 5 ms 7 ms 5 ms 192.168.0.1
22 * * * Request timed out.
23 5 ms 6 ms * 192.168.0.1
24 * * * Request timed out.
25 6 ms 8 ms 7 ms 192.168.0.1
26 * * * Request timed out.
27 6 ms * * 192.168.0.1
28 * * * Request timed out.
29 7 ms 6 ms 11 ms 192.168.0.1
30 * * * Request timed out.
Trace complete.
Here is the output of OpenDNS (which does work):
C:\Users\Nick>tracert 208.67.222.222
Tracing route to resolver1.opendns.com [208.67.222.222]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 9 ms 7 ms 251.core.plus.net [195.166.130.251]
3 8 ms 8 ms 8 ms 84.93.253.91
4 8 ms 8 ms 8 ms 195.99.125.136
5 8 ms 8 ms * core6-hu0-3-0-15.faraday.ukcore.bt.net [109.159.252.134]
6 9 ms 9 ms 9 ms 166-49-209-194.gia.bt.net [166.49.209.194]
7 * * * Request timed out.
8 10 ms 9 ms 9 ms resolver1.opendns.com [208.67.222.222]
Trace complete.
Wrong guess: Pi-hole isn't capable of rerouting and blocking network traffic indiscriminately.
As a filtering DNS server, all that it ever sees are DNS requests, and only those from clients that are using it for DNS.
All other traffic goes whichever way your router and clients are configured for.
This means that a ping to an IP address does not involve Pi-hole at all.
Run from the Windows client that fails to ping, what's the output of
ipconfig /all
Also, 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:
Other information that may be relevant: I am also running pivpn alongside pi-hole, but this is not being used for any of these tests. I have also tried to ping 8.8.8.8 from another PC on the network and get the same results.
OK - so I have found the problem - apologies for using up your time.
I had a static route setup in my router to send 8.8.8.8 and 8.8.4.4 to pi-hole. I did this a long time ago, but I think it was because I found that Android in some instances was insisting on using these IPs as the DNS and was bypassing pi-hole and serving up ads. Disabling those routes has allowed the ping to work.
Many thanks for making me think more about where the problem could be. I'll work out if I need to re-enable the routes and then raise a different topic if needed.