"DNS server failure" after v6 update

Expected Behaviour:

No "DNS server failure"
Hardware: Raspberry Pi 3 Model A Plus Rev 1.0
I am running pihole v6 on a Raspberry Pi over a wireless network, just updated OS prior to running pihole -up

$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Actual Behaviour:

After updating from pihole v5 to v6 by running pihole -up, the dashboard shows "DNS server failure" in red in the top corner, similar to what is shown in this topic:

However unlike the previous topic, I only run pihole on the Raspberry Pi, I have never installed a VM on it.
Running pihole -d does not show anything on port 53

$sudo ss -tulpn sport = 53
Netid  State  Recv-Q  Send-Q   Local Address:Port   Peer Address:Port  Process

I have tried rebooting and sudo pihole repair, but the problem persists and it doesn't seem to be servicing any DNS requests.

nslookup google.com 192.168.0.241
;; connection timed out; no servers could be reached

It is the 2nd pihole on my network (used as a backup), I have yet to update the other primary pihole v5 running in Docker on my NAS, that is still working fine:

nslookup google.com 192.168.0.240
Server:		192.168.0.240
Address:	192.168.0.240#53

google.com	canonical name = forcesafesearch.google.com.
Name:	forcesafesearch.google.com
Address: 216.239.38.120
Name:	forcesafesearch.google.com
Address: 2001:4860:4802:32::78

Debug Token:

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

I have worked out what the problem was and fixed it after I found the pihole.log file under the tools menu.

dnsmasq was not starting because of bad dhcp-host data imported from my v5 settings.

After I corrected the problems in /etc/pihole/pihole.toml it started working properly.

There were 2 problems lines in the dhcp-hosts:

  1. dhcp-host=11:22:33:44:55:66,192.168.0.12,TV--Samsung-The-Frame--32

The log file showed it was complaining that the host name TV--Samsung-The-Frame--32 was invalid. I am not sure what was wrong with it, it didn't cause a problem with my v5 set up, perhaps it is too long?

  1. dhcp-host=AA-BB-CC-DD-EE-FF,192.168.0.29,repeaterfront

The log file showed an error on this line, the obvious problem was the use of '-' as a separator in the MAC address rather than ':'. This was also directly copied over from my v5 setup.

Fixing these 2 problems got it working.

Funny that the v5 set up never complained about these problems...

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