Hi guys,
pihole-FTL status check shows:
ebian@beaglebone:~$ sudo service pihole-FTL status -l
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Sun 2018-11-25 23:01:31 UTC; 5s ago
Docs: man:systemd-sysv-generator(8)
Process: 3178 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
Process: 3184 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
Nov 25 23:01:30 beaglebone systemd[1]: Starting LSB: pihole-FTL daemon...
Nov 25 23:01:30 beaglebone pihole-FTL[3184]: Not running
Nov 25 23:01:30 beaglebone pihole-FTL[3184]: chown: cannot access '/etc/pihole/dhcp.lea
Nov 25 23:01:30 beaglebone su[3207]: Successful su for pihole by root
Nov 25 23:01:30 beaglebone su[3207]: + ??? root:pihole
Nov 25 23:01:30 beaglebone su[3207]: pam_unix(su:session): session opened for user piho
Nov 25 23:01:31 beaglebone pihole-FTL[3184]: FTL started!
Nov 25 23:01:31 beaglebone systemd[1]: Started LSB: pihole-FTL daemon.
pihols status check shows:
debian@beaglebone:~$ pihole status
[✓] DNS service is running
[✓] Pi-hole blocking is Enabled
DNS lookup check shows:
ebian@beaglebone:~$ host pi.hole localhost
Using domain server:
Name: localhost
Address: ::1#53
Aliases:
pi.hole has address
pi.hole has IPv6 address <probably correct IP, IPv6 is weird to me>
I'll go point my router back to the pihole, brb...