Upgrade to 4.0, DNS will not start, reports FTL offline

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

Expected Behaviour:

Upgrade from 4.0

Actual Behaviour:

upgrade run, dns reported as not started.
ran pihole -r, noticed error ftl not installed from github.
modified etc/pihole/install.log to 8.8.8.8, reran pihole -r. still no luck
web page reports: DNS service not running FTL offline

Debug Token:

cnspidduf6

I got the same issue heer.
Running Ubuntu 18.4
Dansmarathon unaniem to open port. On x.x.x.x address already in Use.
Bind is NOT installed

You mean you modified /etc/resolv.conf with nameserver 8.8.8.8 right ?
Can you post full output of the pihole -r output ?
Keep in mind, I believe resolv.conf gets modified back every time you run pihole -r or pihole -up.

Better create you own thread as your issue seems different.
Chances are you have another DNS daemon running on ports 53 TCP/UDP, not pihole-FTL:

pi@noads:~ $ sudo netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471'
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 127.0.0.1:4711          0.0.0.0:*               LISTEN      20855/pihole-FTL
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      8101/lighttpd
tcp        0      0 0.0.0.0:53              0.0.0.0:*               LISTEN      20855/pihole-FTL
tcp6       0      0 ::1:4711                :::*                    LISTEN      20855/pihole-FTL
tcp6       0      0 :::80                   :::*                    LISTEN      8101/lighttpd
tcp6       0      0 :::53                   :::*                    LISTEN      20855/pihole-FTL
udp        0      0 0.0.0.0:53              0.0.0.0:*                           20855/pihole-FTL
udp        0      0 0.0.0.0:67              0.0.0.0:*                           20855/pihole-FTL
udp6       0      0 :::53                   :::*                                20855/pihole-FTL

Thanks for the heads up., but my issue WAS the same.
Autocorrect has been over active!

I got Dns running now! And the adds are blocked! So the primary goal is reached.

I removed the # before dns=5353 in /etc/dnsmasq.conf

But yes there is a catch. The counters in the admin page remain zero.

I will keep searching

Sorry I thought I deleted this topic, but since it's still here.

Yes, that's correct.

Unfortunately, to get this resolved, I wound up reimaging the pi. A new installation of 4.0 is now working.

It does not from what I could see trying pihole -r multiple times.

1 Like
pi@noads:~ $ 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
nameserver 8.8.8.8

pi@noads:~ $ pihole -r

pi@noads:~ $ 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
nameserver 127.0.0.1

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