pi@raspberrypi:~ $ sudo systemctl status pihole-FTL.service
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Fri 2018-06-08 10:38:11 EDT; 3min 42s ago
Docs: man:systemd-sysv-generator(8)
Process: 284 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/pihole-FTL.service
Jun 08 10:38:07 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
Jun 08 10:38:08 raspberrypi pihole-FTL[284]: Not running
Jun 08 10:38:08 raspberrypi pihole-FTL[284]: rm: cannot remove '/var/run/pihole/FTL.sock': No such file or directory
Jun 08 10:38:09 raspberrypi su[361]: Successful su for pihole by root
Jun 08 10:38:09 raspberrypi su[361]: + ??? root:pihole
Jun 08 10:38:09 raspberrypi su[361]: pam_unix(su:session): session opened for user pihole by (uid=0)
Jun 08 10:38:11 raspberrypi pihole-FTL[284]: FTL started!
Jun 08 10:38:11 raspberrypi systemd[1]: Started LSB: pihole-FTL daemon.
pi@raspberrypi:~ $
pi@raspberrypi:~ $ sudo systemctl status dnsmasq
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2018-06-08 10:38:11 EDT; 3min 41s ago
Process: 467 ExecStartPost=/etc/init.d/dnsmasq systemd-start-resolvconf (code=exited, status=0/SUCCESS)
Process: 450 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=0/SUCCESS)
Process: 379 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUCCESS)
Main PID: 463 (dnsmasq)
CGroup: /system.slice/dnsmasq.service
└─463 /usr/sbin/dnsmasq -x /run/dnsmasq/dnsmasq.pid -u dnsmasq -r /run/dnsmasq/resolv.conf -7 /etc/dnsmasq.d,.dpkg
Jun 08 10:38:08 raspberrypi systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server...
Jun 08 10:38:11 raspberrypi dnsmasq[379]: dnsmasq: syntax check OK.
Jun 08 10:38:11 raspberrypi systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server.
...skipping...
Both nslookup commands returned the correct reply. That means that the DNS resolution was working, at least locally. (flurry.com is a known blocked domain and it was Pi-holed).
The Lighttpd Daemon on the other hand ... is behaving weirdly
Nslookup on my macbook after reboot but nothing else:
2017-Bens-MacBook-Pro:Downloads Ben$ nslookup flurry.com
;; connection timed out; no servers could be reached
VNC'd to rasberry pi 192.168.1.12
Nslookup on rasberry pi:
pi@raspberrypi:~ $ nslookup flurry.com
Server: 127.0.0.1
Address: 127.0.0.1#53
This does not seem to be related to the Pi-hole instance.
You were able to connect to the raspberry via VNC and the DNS worked when you queried the domain.
what's the response you get from your client when you run
nslookup flurry.com 192.168.1.12
After raspberry reboot, can you access the flurry page on a different device (maybe cell phone/tablet)?
2017-Bens-MacBook-Pro:Downloads Ben$ echo before reboot of raspberry pi
before reboot of raspberry pi
2017-Bens-MacBook-Pro:Downloads Ben$ nslookup flurry.com 192.168.1.12
Server: 192.168.1.12
Address: 192.168.1.12#53
2017-Bens-MacBook-Pro:Downloads Ben$ echo after raspberry pi reboot
after raspberry pi reboot
2017-Bens-MacBook-Pro:Downloads Ben$ nslookup flurry.com 192.168.1.12
;; connection timed out; no servers could be reached
After reboot on my iphone i could not reach yahoo.com.
Then I went to pi-hole admin page on my iphone
Then I was able to access yahoo.com from my iphone.
I dig up this conversation because I had the same issue with a newly installed pi-hole.
I turn off all devices at night, included the pi. So the pi-hole need to restart correctly each day. After one week trying, I finally succeeded! It's a dirty solution but it work, maybe some of you will find something more clean.
For me, pi-hole can't work as a DNS server when restarted because he don't have the right time.
So :
1/ I installed ntp on the Pi.
2/ I forced "nameserver 8.8.8.8" on /etc/resolv.conf
3/ I change the right of this file to 555 to avoid system modification each time.
After each start, the pi need a bit of time to sync with ntp server but after that, all good to go.
1/ I installed ntp on the Pi.
2/ I forced “nameserver 8.8.8.8” on /etc/resolv.conf
3/ I change the right of this file to 555 to avoid system modification each time.
This has got to be the stupidest thing ever. So time goes off and internet doesn't work.
You cannot manually set the time. You cannot edit the file for the name server. You cannot install NTP.
Last time power went out the only solution was to wipe the pi and install it again.
If your Pi-hole host is using Pi-hole as nameserver, you change this in the OS and the host will have access to a DNS server whether Pi-hole is operating or not.