The original post: /r/pihole by /u/No-Row-7771 on 2024-10-09 15:45:32.

Hello all,

I have pihole running on DietPi OS on a Raspberry 2B, and everythings -seems- to be functioning well. I have adblocking on all devices, everything is connected, no issues anywhere in functionality.

However, something still seems to be wrong. After getting everything to work, I can’t install PiVPN on my pi because github fails to respond. I can ping/dig/nslookup google just fine, but I can’t ping 8.8.8.8

I can’t upload a debug log because

curl: (7) Failed to connect to tricorder.pi-hole.net port 443 after 3163 ms: Couldn't connect to serve

Otherwise, there are some errors in ipv4 and ipv6 resolution:

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] www.gazetowo-swiatowo.pl is 0.0.0.0 on lo (127.0.0.1)
[✓] www.gazetowo-swiatowo.pl is 0.0.0.0 on eth0 (192.168.3.14)
[✓] www.gazetowo-swiatowo.pl is 0.0.0.0 on tailscale0 (100.126.243.59)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] msimonconsulting.com is :: on lo (::1)
[✓] msimonconsulting.com is :: on eth0 (2001:4958:22f0:6801:ba27:ebff:fe92:32a9)
[✓] msimonconsulting.com is :: on eth0 (2001:4958:2466:b001:ba27:ebff:fe92:32a9)
[✗] Failed to resolve msimonconsulting.com on eth0 (fe80::ba27:ebff:fe92:32a9)
[✓] msimonconsulting.com is :: on tailscale0 (fd7a:115c:a1e0::8001:f33e)
[✗] Failed to resolve msimonconsulting.com on tailscale0 (fe80::cc56:f464:9c7c:3352)
[✓] doubleclick.com is 2607:f8b0:4020:807::200e via a remote, public DNS server (2001:4860:4860::8888)

And for gateways:

[i] Default IPv4 gateway(s):
     192.168.3.1
   * Pinging first gateway 192.168.3.1...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)

[i] Default IPv6 gateway(s):
     fe80::6e99:61ff:febb:a838
   * Pinging first gateway fe80::6e99:61ff:febb:a838...
[✓] Gateway responded.

Any ideas what the issue may be? For further context- my pi isn’t currently appearing as a connected device on my router which appears odd to me. This may be why it’s acting strange? Though it’s clearly still getting internet as I can SSH into it, use the web interface, etc.

I do also have unbound installed but I am not currently using it because everything seems to SERVFAIL with it