Pi-Hole "Temporary Failure in Name Resolution" When Selected as DNS Server

Hello,

Any help would be appreciated. I have looked at any solution for problems that look similar, but can't seem to find a solution/

Expected Behaviour:

Pi-hole running on a raspberry pi 32 bit should be able to function as DHCP & DNS server for home network. Was working for many months and then the DNS capability failed. Currently running:

RETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

Actual Behaviour:

After the Pi-Hole initially failed (Overnight there was a large spike in DNS queries from ~1000 to ~10,000, then network connection was lost) I tried to set it back up as normal. But when I try to set the pi as the DNS server on the router the pi immediately losses DNS capabilities and cannot access the internet. Trying to ping anything returns a "Temporary failure in name resolution". All other devices lose the ability to view webpages as well. Everything is fine if I switch back to the default DNS servers for all other devices, but I have to change the IP address of the pi to gain DNS function again. Or at least I think it's a DNS issue, as there's no issue with the internet until I try to set up the pi as a DNS server. I am currently using the wlan0 connection

ip addr show:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether d8:3a:dd:4d:0d:4f brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether d8:3a:dd:4d:0d:50 brd ff:ff:ff:ff:ff:ff
inet 192.168.2.30/24 brd 192.168.2.255 scope global dynamic noprefixroute wlan0
valid_lft 257148sec preferred_lft 257148sec
inet6 fe80::aa6c:ed1c:2676:319a/64 scope link noprefixroute
valid_lft forever preferred_lft forever

ip route:

default via 192.168.2.1 dev wlan0 proto dhcp metric 600
192.168.2.0/24 dev wlan0 proto kernel scope link src 192.168.2.30 metric 600

route -n:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.2.1 0.0.0.0 UG 600 0 0 wlan0
192.168.2.0 0.0.0.0 255.255.255.0 U 600 0 0 wlan0

/etc/dhcpcd.conf:

interface wlan0
inform 192.168.2.30/24
static routers=192.168.2.1
static domain_name_servers=8.8.8.8
noipv6
interface wlan0
static ip_address=192.168.2.30/24
static routers=192.168.2.1
static domain_name_servers=8.8.8.8 8.8.4.4
interface eth0
static ip_address=192.168.2.31/24
static routers=192.168.2.1
static domain_name_servers=

Debug Token:

https://tricorder.pi-hole.net/VrMzxH6m/

I've also noticed that the time on the pi is off by about 3 seconds, which an issue when pi hole first failed. Not sure if this would be related.

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