pihole is up to date:
Pi-hole version is v4.0 (Latest: ERROR)
AdminLTE version is v4.0 (Latest: ERROR)
FTL version is v4.0 (Latest: ERROR)
You are right, dnsmasq was still running, although I disabled it via systemctl. A forgotten script in the background started dnsmasq again without my knowledge. I disabled the script and dnsmasq and did a reboot. Now sudo netstat -nltup | grep 'Proto\|:53 \|:67 \|:80 \|:471' shows the following:
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 631/lighttpd
tcp6 0 0 :::80 :::* LISTEN 631/lighttpd
So no pihole-FTL here... sudo systemctl status pihole-FTL -l shows:
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Tue 2018-10-02 08:44:36 CEST; 30min ago
Docs: man:systemd-sysv-generator(8)
Process: 304 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/pihole-FTL.service
Oct 02 08:44:23 raspi systemd[1]: Starting LSB: pihole-FTL daemon...
Oct 02 08:44:23 raspi pihole-FTL[304]: Not running
Oct 02 08:44:23 raspi pihole-FTL[304]: chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory
Oct 02 08:44:35 raspi su[1106]: Successful su for pihole by root
Oct 02 08:44:35 raspi su[1106]: + ??? root:pihole
Oct 02 08:44:35 raspi su[1106]: pam_unix(su:session): session opened for user pihole by (uid=0)
Oct 02 08:44:36 raspi pihole-FTL[304]: dnsmasq: cannot open or create lease file /var/lib/misc/dnsmasq.leases: Permission denied
Oct 02 08:44:36 raspi systemd[1]: Started LSB: pihole-FTL daemon.
Ohw that last ipv6
nameserveraddress [in/etc/resolv.conf] could be causing thenslookupparse failures.
I think you are right. I commented the last line out in /etc/resolv.conf, now I get the following results:
host -t txt -c ch version.bind 192.168.2.3
;; connection timed out; no servers could be reached
host pi.hole 192.168.2.3
;; connection timed out; no servers could be reached
Thank you very much for your time and your commitment!
EDIT: I was curious about the line
dnsmasq: cannot open or create lease file /var/lib/misc/dnsmasq.leases: Permission denied
from sudo systemctl status pihole-FTL -l so I googled some time around and I found this thread.
In /etc/init.d/pihole-FTL I changed the line
su -s /bin/sh -c "/usr/bin/pihole-FTL" "$FTLUSER"
to
/usr/bin/pihole-FTL
Afterwards I did a
sudo systemctl daemon-reload
sudo systemctl restart pihole-FTL
and it worked!
Now sudo systemctl status pihole-FTL -l shows:
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (running) since Tue 2018-10-02 09:30:16 CEST; 52s ago
Docs: man:systemd-sysv-generator(8)
Process: 5086 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
Process: 5137 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/pihole-FTL.service
└─5225 /usr/bin/pihole-FTL
Oct 02 09:30:04 raspi systemd[1]: Starting LSB: pihole-FTL daemon...
Oct 02 09:30:04 raspi pihole-FTL[5137]: Not running
Oct 02 09:30:04 raspi pihole-FTL[5137]: chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory
Oct 02 09:30:16 raspi pihole-FTL[5137]: FTL started!
Oct 02 09:30:16 raspi systemd[1]: Started LSB: pihole-FTL daemon.
I really don't know why this change solves the problem? Maybe there is a problem with access rights? It feels a bit like a "quick and dirty" solution which could cause new problems after the next update. So maybe someone knows how I can change access rights to its proper settings?
Nevertheless I am very happy to get that far with all your help!