Please follow the below template, it will help us to help you!
If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.
Expected Behaviour:
PI-Hole run as before the update.
Actual Behaviour:
PI-Hole shows error "DNS server failure".
sudo ss -tulpn sport = 53
Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
udp UNCONN 180480 0 0.0.0.0:53 0.0.0.0:* users:(("pihole-FTL",pid=4905,fd=20))
udp UNCONN 0 0 10.0.3.1:53 0.0.0.0:* users:(("dnsmasq",pid=823,fd=6))
tcp LISTEN 0 32 10.0.3.1:53 0.0.0.0:* users:(("dnsmasq",pid=823,fd=7))
But dnsmasq is not running:
sudo systemctl status dnsmasq
Unit dnsmasq.service could not be found.
Debug Token:
No upload possible:
[?] Would you like to upload the log? [y/N] y
* Using curl for transmission.
* curl failed, contact Pi-hole support for assistance.
* Error message: curl: (6) Could not resolve host: tricorder.pi-hole.net
and restart the pihole-FTL service. After that PI-Hole is working including DNS server.
I rebooted my raspi and still PI-Hole is working. But then I made another update:
udo pihole -up
[✓] Supported OS detected
[✓] Update local cache of available packages
[✓] Building dependency package pihole-meta.deb
[✓] Installing Pi-hole dependency package
[i] Checking for updates...
[i] Pi-hole Core: update available
[i] Web Interface: up to date
[i] FTL: up to date
[i] Pi-hole core files out of date, updating local repo.
[✓] Check for existing repository in /etc/.pihole
[i] Update repo in /etc/.pihole...HEAD ist jetzt bei 9de976cb Pi-hole Core 6.0.1 (#5912)
[✓] Update repo in /etc/.pihole
...
[i] Testing if systemd-resolved is enabled
[i] Systemd-resolved is not enabled
[i] Restarting services...
[✓] Enabling pihole-FTL service to start on reboot...
[✓] Restarting pihole-FTL service...
[✓] Deleting existing list cache
[✗] DNS resolution is currently unavailable
[i] Waiting until DNS resolution is available..................
And again I got the DNS server failure in PI-Hole.
cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "resolvectl status" to see details about the actual nameservers.
nameserver 127.0.0.3
search fritz.box
I have on this raspi for longer time "DNSCrypt-proxy" installed, which listen on Port 127.0.0.3:10053. I guess, the content of /etc/resolv.conf is from this installation.
The update of pihole to v6 seemed to changed the configuration of DNSCrypt-proxy.
For now I added more nameserver (second pihole-instance with v5 and main router) and run
sudo pihole -up
again. But actual are no updates, so I cannot test, if the update works. I have to wait for the next update.
I have never done anything with DNSCrypt-proxy so I have no idea how it works, but I would expect to have some kind of port mentioned too next to the additional localhost IP ?!
If you use 127.0.0.3 only for DNSCrypt-proxy then you could use just port 53 or one of the DoH/DoT related ports I think ??
Today is a update for pihole-ftl and it runs without errors. So, the DNS-configuration is working.
I have 3 nameserver in my /etc/resolv.conf.
Next week I update the other pihole-instance and hopefully it will work.
this is the fix that i did
1- SSH to Raspberry pi and update DNS IP setting to my Routers Gateway, so i can get internet, nano /etc/dhcpcd.conf
2- reboot Raspberry pi -->sudo reboot
3-now i have internet, ran this command -->sudo PIHOLE_SKIP_OS_CHECK=true pihole -r
4-once Window opens, choose first option R for repair
5-pi hole is back up, -->update DNS IP to raspberry pi using this command nano /etc/dhcpcd.conf
