hi guys,
Just installed a pi-hole on an existing server machine (ubuntu 20.04) which is rather clean. Installation went smooth, however at the end I receive the following error: " [✗] DNS service is NOT running "
In the dashboard this is confirmed, together with an error message for FTL.
Any idea how to fix this, because a forum and google search did not bring me closer to a solution. Please see below output + token
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated)
Active: active (exited) since Wed 2020-11-11 18:02:59 UTC; 1h 53min ago
Docs: man:systemd-sysv-generator(8)
Process: 12223 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
Nov 11 18:02:59 homeserver systemd[1]: Starting LSB: pihole-FTL daemon...
Nov 11 18:02:59 homeserver pihole-FTL[12223]: Not running
Nov 11 18:02:59 homeserver su[12243]: (to pihole) root on none
Nov 11 18:02:59 homeserver su[12243]: pam_unix(su:session): session opened for user pihole by (uid=0)
Nov 11 18:02:59 homeserver su[12243]: pam_unix(su:session): session closed for user pihole
Nov 11 18:02:59 homeserver systemd[1]: Started LSB: pihole-FTL daemon.
and:
xx@homeserver:~$ ls -lah /etc/dnsmasq.d/
total 20K
drwxr-xr-x 2 root root 4.0K Nov 11 12:59 .
drwxr-xr-x 113 root root 12K Nov 11 12:59 ..
-rw-r--r-- 1 root root 1.5K Nov 11 12:59 01-pihole.conf
lrwxrwxrwx 1 root root 28 Feb 14 2019 lxd -> /etc/dnsmasq.d-available/lxd
I've been long wondering what triggers creation of those lxd files, and if they are indeed present at the time of Pi-hole's installation.
Personally, I haven't seen them when I last setup Ubuntu (that was 18).
Maybe you have the time to investigate?
Also, there are other instances where extra dnsmasq configuration interferes with Pi-hole's operation, e.g. PiVPN, raspAP, and some other third-party tools.
I'd probably prefer an addition to the debug log instead.