Unable to resolve DNS

Help Community Help
1

**The issue I am facing:**My pihole randomly stops resolving DNS requests. It does not happen all the time but every once in a while it will go down. Everytime I run pihole -d the diagnosis always looks something like this https://tricorder.pi-hole.net/gddOkyyX/

  1. Pihole ip is the DNS for my router, that was the easiest set up for me
  2. I have even tried setting individual devices to use pihole ip as their DNS

The issue usually goes away after I restart the system a few times. Also when this issue is happening pihole can locally resolve dns lookups when I connect it to a monitor and connect a keyboard.
It is worth noting that I also have issues SSH-ing into the device despite opening that port

**Details about my system:**Orange Pi zero 2
ufw enabled with all the necessary ports open for pihole to work on ipv4 and ipv6 (despite this being disabled at the router)
Also running snowflake in a docker container
Running DoH via cloudflared

**What I have changed since installing Pi-hole:**Disabled systemd and tried changing ports to see if something was interfering with it. I have also manually created the file once before. I run debug logs when the system is working again.

2

About this part of your title:

Actually the file lighttpd.conf exits (full path /etc/lighttpd/lighttpd.conf):

*** [ DIAGNOSING ]: contents of /etc/lighttpd
-rw-r--r-- 1 root root 2.2K Dec 30  2021 /etc/lighttpd/lighttpd.conf

If you are talking about this message:

*** [ DIAGNOSING ]: contents of /etc/lighttpd/conf.d
/etc/lighttpd/conf.d does not exist.

This is expected on Ubuntu installs (this directory only exists in Fedora/CentOS/RedHat).

3

Ahh and I am guessing nothing in the debug log screams dropping connection.. sad.
Any recommendations for troubleshooting? My main issue is that devices using the pihole as DNS do not seem to have internet connection. And this problem is intermittent. Should I open a separate topic for that? Also here is another debug log.. this time it could not find any devices connected on IPv4 despite having it explicitly declared as the DNS for at least 1 device. here is another debug log https://tricorder.pi-hole.net/Xd2Y7gra/ . thank you in advance and sorry for the trouble.

4

No need... you can edit the title to remove the part about lighttpd.conf.

Since this is an intermittent issue, let's remove unrelated items and try to test only Pi-hole.

You are using cloudflared (127.0.0.1:5053) as Upstream DNS server.
Let's eliminate this variable from our troubleshooting.

Please, set Pi-hole upstream DNS to an external public DNS server (1.1.1.1, 8.8.8.8, or any other of your preference).

Can you run these commands from this device?

nslookup pi-hole.net

nslookup pi-hole.net 192.168.1.254

nslookup flurry.com 192.168.1.254

What is the output?

5

For pi-hole.net and
pi-hole.net 192.168.1.254
it returned the same address 3.18.136.52
When I tried flurry it returned

Name: flurry.com
Address: 0.0.0.0
Name: flurry.com
Address: ::
6

Okay now it returns

;; connection timed out; no servers could be reached

7

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