DNS service not running

[socram]

Please follow the below template, it will help us to help you!

Expected Behaviour:

DNS Service starting

Actual Behaviour:

DNS Service not running

Debug Token:

xz26y0lwz2

Dear team,

my pihole-installation was running perfectly fine until I updated stubby this morning and changed the listen address to 127.0.0.2#53 (as 5353, which is used before is used by the avahi-daemon.
However, changing that back didn't help.
I'm a little confused that the debug output tells me that 127.0.0.2:53 is used by pihole-FTL as it's used by stubby (which is working fine btw with dig @127.0.0.2 pi-hole.net)

If been searching the forum for hours now and checked all the possible answers for my issue but unfortunately nothing helps.

As dnsmasq is used within pihole now, I disabled the service so that shouldn't conflict. However, here's the output of journalctl -xe if that helps:

Feb 16 12:19:41 RasPi dnsmasq[16422]: dnsmasq: bad option at line 44 of /etc/dnsmasq.d/01-pihole.conf
Feb 16 12:19:41 RasPi dnsmasq[16422]: bad option at line 44 of /etc/dnsmasq.d/01-pihole.conf
Feb 16 12:19:41 RasPi dnsmasq[16422]: FAILED to start up
Feb 16 12:19:41 RasPi systemd[1]: dnsmasq.service: Control process exited, code=exited status=1
Feb 16 12:19:41 RasPi systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
-- Subject: Unit dnsmasq.service has failed

I would be very grateful (and maybe others which find this thread) if I could assistance with troubleshooting.

[jfb]

You may have a two part problem here. Something is keeping pihole-FTL from running, and there have been separate reports of problems running Pi-Hole alongside Stubby.

What is the output of this command which will show processes running on ports used by Pi-Hole:

sudo netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471'

[socram]

Thanks for your time and your answer!

While checking the forum I just noticed that somebody else has a similar problem which also occurs with stubby.

pihole-FTL failed to create listening socket for port 53

Hi, as pihole does not provide dns privacy using DNS-over-TLS (DoT), I used older versions of pi-hole together with the dns proxy stubby (DoT). After switching to pihole-FTL, this doesnt seem to work anymore. I checked two different pihole installations, and both complain "failed to create listening socket for port 53 : Address already in use". After stopping and disabling stubby using systemctl, pihole-FTL works again as expected. Is there anything I can do about this? best regards, and than…

Following that thread I delayed the stubby startup by 30 seconds so it starts after pihole-FTL now.
However, that's only a workaround, as it doesn't solve the problem.

If everything is running (pihole-FTL first, stubby afterwards) this is the result of the command:

tcp 0 0 127.0.0.1:4711 0.0.0.0:* LISTEN 2455/pihole-FTL
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 738/nginx: master p
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 2455/pihole-FTL
tcp6 0 0 ::1:4711 :::* LISTEN 2455/pihole-FTL
tcp6 0 0 :::80 :::* LISTEN 738/nginx: master p
tcp6 0 0 :::53 :::* LISTEN 2455/pihole-FTL
udp 0 0 0.0.0.0:53 0.0.0.0:* 2455/pihole-FTL
udp 0 0 127.0.0.2:53 0.0.0.0:* 1397/stubby
udp6 0 0 :::53 :::* 2455/pihole-FTL

If only stubby is running:

tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 738/nginx: master p
tcp 0 0 127.0.0.2:53 0.0.0.0:* LISTEN 23020/stubby
tcp6 0 0 :::80 :::* LISTEN 738/nginx: master p
udp 0 0 127.0.0.2:53 0.0.0.0:* 23020/stubby

If only pihole-FTL is running:

tcp 0 0 127.0.0.1:4711 0.0.0.0:* LISTEN 23252/pihole-FTL
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 738/nginx: master p
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 23252/pihole-FTL
tcp6 0 0 ::1:4711 :::* LISTEN 23252/pihole-FTL
tcp6 0 0 :::80 :::* LISTEN 738/nginx: master p
tcp6 0 0 :::53 :::* LISTEN 23252/pihole-FTL
udp 29248 0 0.0.0.0:53 0.0.0.0:* 23252/pihole-FTL
udp6 0 0 :::53 :::* 23252/pihole-FTL