Pi-Hole Not Responding to DNS, HTTP, requests or denying them

The issue: pi-hole does not respond to any DNS requests or HTTP requests or rejects them. SSH is also rejected. A power cycle does fix the problem.

When it happens: This used to happen once a week so I put a smart plug that would power turn off & and on the orange pi every night now it happens every 2-3 hours

System: an orange pi zero 512mb runing pi-hole 5.2.2 web interface 5.2.2 FTL 5.3.4 and remote.it. on debian_stretch_server_linux5.3.5_v1.0

I have changed nothing since the first time install

I suspect remote. it. I will re-install Debian without a remote.it I will report back my findings
debug log: https://tricorder.pi-hole.net/bduhun4v3a


after 4 days. Pi-Hole does not resolve DNS requests. the web page is not responding.

log:https://tricorder.pi-hole.net/tcfcyrzrao

The output you're showing means there's a networking issue between the client and the Pi. You're using the IP address of the Pi so there is no DNS involved.

Futher, the debug log you uploaded shows that Pi-hole itself is working.

[i] Default IPv4 gateway: 192.168.0.1
   * Pinging 192.168.0.1...
[✓] Gateway responded.
[i] Default IPv6 gateway: fe80::aa5e:45ff:fe06:d7f0
   * Pinging fe80::aa5e:45ff:fe06:d7f0...
[✓] Gateway responded.

IPv4 is working for resolving, but you have issues with IPv6, both on the LAN and remotely:

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] c5.zedo.com is 0.0.0.0 via localhost (127.0.0.1)
[✓] c5.zedo.com is 0.0.0.0 via Pi-hole (192.168.0.104)
[✓] doubleclick.com is 216.58.212.14 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
[✓] videojohny.eu is :: via localhost (::1)
[✗] Failed to resolve videojohny.eu via Pi-hole (2002:<<redact>>:cf75)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)

Your ssh failures are on IPv4 though.

I think you need to check your networking. Are you assigning the Pi address as a DHCP client or are you doing it statically via /etc/dhcpcd.conf? The debug shows there is a DHCP server offering .104, if you have set a reservation on the router then check /etc/dhcpcd.conf to make sure you're not also setting a static IP address.

1 Like

I forgot to mention: I took these debug logs after the reboot.
my isp does not support ipv6.

yes i have also set a static ip adress on the orangepi . i am disabling the routers ip adress binding :image

i will try using pi-hole thanks for the help

It has been 5 days and I never had a problem since. I would like to thank everyone who helped to make this awesome shoftware, and especially DanSchaper for helping me out!

1 Like

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.