Bitte beachte diese Vorlage, damit wir dir bestmöglich helfen können!
Beobachtetes und erwartetes Verhalten
Seit heute Mittag ist der PiHole DNS Server down. Ich weiß leider nicht warum und wie ich das beheben kann. Ich kenne mich leider auch nicht wirklich gut aus und habe das was ich über Google gefunden habe nicht wirklich verstanden / umsetzen können bzw. es war keine wirkliche Hilfe.
Ausgeführt wird PiHole via Docker/Portainer auf einem UGREEN NAS.
Bisher gab es keine Probleme (run time about 3 weeks).
Danke für Eure Hilfe.
Stefan
Debug Token:
2025-06-02 17:22:11.016 CRIT Error in dnsmasq configuration: failed to create listening socket for port 53: Address in use
2025-06-02 17:22:11.016 failed to create listening socket for port 53: Address in use
2025-06-02 17:22:11.016 FAILED to start up
I thought lets have a look at how those Ugreen's look like.
First thing I noticed on their home page was below ad snippet:
Unprecedented Charing power
World's first 500W GaN Desktop charger
Thats not a typo of mine!
I think I'll stay clear from Ugreen for a while
But to get back to the heart of the issue.
That nas is probably running its own stub resolver / DNS proxy / cashing DNS forwarder thats listening on port 53.
Thus conflicting with Pi-hole that also needs port 53 to listen on ... to serve the clients.
Either you find a way to disable that stub resolver without breaking too much, or you need to setup the Docker container with the ipvlan or macvlan networking mode/driver:
EDIT: If you can access a shell on that nas, you could try run below as the root user or as a user that has enough privies.
ss -nltup sport = 53
Or if that one isn't available:
netstat -nltup
Those should list the daemon thats currently listening on port 53.
Eg:
$ sudo ss -nltup sport = 53
Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
udp UNCONN 0 0 0.0.0.0:53 0.0.0.0:* users:(("pihole-FTL",pid=481,fd=20))
udp UNCONN 0 0 [::]:53 [::]:* users:(("pihole-FTL",pid=481,fd=22))
tcp LISTEN 0 32 0.0.0.0:53 0.0.0.0:* users:(("pihole-FTL",pid=481,fd=21))
tcp LISTEN 0 32 [::]:53 [::]:* users:(("pihole-FTL",pid=481,fd=23))
The funny thing is: I figured out what it was.
I installed the Virtual Machine App on my UGREEN NAS and this is the trouble maker.
As soon as I deinstalled the VM App everything is working again.
