Please follow the below template, it will help us to help you!
Expected Behaviour:
[Running as usual]
Actual Behaviour:
[Not forwarding DNS requests from clients on the LAN
I don't know what happened. As far as I remember there was nothing special, no change on the RPI, no change in the network.
Picture shows requests before and after. Before different clients, after just localhost.
O btw, no IP#'s as I edited /etc/hosts]
That's swift! I'll do so.
I'll dive into the RPI logs as well.
Is this helpfull?
Feb 17 11:38:14 RPI3 systemd[1]: Stopping LSB: pihole-FTL daemon...
Feb 17 11:38:14 RPI3 systemd[1]: session-c1.scope: Succeeded.
Feb 17 11:38:14 RPI3 pihole-FTL[19350]: Stopped
Feb 17 11:38:14 RPI3 systemd[1]: pihole-FTL.service: Succeeded.
Feb 17 11:38:14 RPI3 systemd[1]: Stopped LSB: pihole-FTL daemon.
Feb 17 11:38:14 RPI3 systemd[1]: Starting LSB: pihole-FTL daemon...
Feb 17 11:38:14 RPI3 pihole-FTL[19380]: Not running
Feb 17 11:38:15 RPI3 systemd[1]: Started Session c8 of user pihole.
Feb 17 11:38:15 RPI3 pihole-FTL[19380]: FTL started!
Feb 17 11:38:15 RPI3 systemd[1]: Started LSB: pihole-FTL daemon.
Feb 17 11:39:00 RPI3 systemd[1]: Starting Clean php session files...
Feb 17 11:39:00 RPI3 systemd[1]: phpsessionclean.service: Succeeded.
Feb 17 11:39:00 RPI3 systemd[1]: Started Clean php session files.
Feb 17 11:39:02 RPI3 CRON[19589]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [$
Feb 17 11:40:01 RPI3 CRON[19686]: (root) CMD ( PATH="$PATH:/usr/local/bin/" pihole upd$
Feb 17 11:40:34 RPI3 SBFspotUploadDaemon[631]: Unable to write to logfile [/ho
And there's a warning too: DataTables warning: table id=all-queries - Requested unknown parameter '3' for row 94, column 3. For more information about this error, please see http://datatables.net/tn/4
What I encounter is that it is necessary to manually set PIHOLE_INTERFACE=wg0
in /etc/pihole/setupVars.conf
I had forgotten that it fails there every now and then, with install as well as when changing settings in the admin interface.
OK, as mentioned before a did another run.
Again PiHole DNS server stopped.
` sudo service pihole-FTL status
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated)
Active: active (exited) since Thu 2020-02-20 17:27:36 CET; 8h ago
Docs: man:systemd-sysv-generator(8)
Process: 15395 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/S
feb 20 17:27:25 RPI3 systemd[1]: Starting LSB: pihole-FTL daemon...
feb 20 17:27:25 RPI3 pihole-FTL[15395]: Not running
`
After that: sudo service pihole-FTL stop, sudo service pihole-FTL start, sudo service pihole-FTL status giving the same output.
Running DNSbench from Windows gives me this picture:
It should be like this:
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated)
Active: active (exited) since Fri 2020-02-21 01:54:58 CET; 6s ago
Docs: man:systemd-sysv-generator(8)
Process: 10802 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
feb 21 01:54:47 RPI3 systemd[1]: Starting LSB: pihole-FTL daemon...
feb 21 01:54:47 RPI3 pihole-FTL[10802]: Not running
feb 21 01:54:57 RPI3 su[10872]: (to pihole) root on none
feb 21 01:54:57 RPI3 su[10872]: pam_unix(su:session): session opened for user pihole by (uid=0)
feb 21 01:54:58 RPI3 pihole-FTL[10802]: FTL started!
feb 21 01:54:58 RPI3 su[10872]: pam_unix(su:session): session closed for user pihole
feb 21 01:54:58 RPI3 systemd[1]: Started LSB: pihole-FTL daemon.