Hi! I posted this in another topic but figured I'd post it here, too. After one of the latest updates, that started to happen to me too. Interestingly, that thing happens only after a power outage, where the Raspberry Pi didn't get shut down properly – every time. With previous versions, that did n…

Here it is 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-g…

Those outputs look fine. What about: nslookup flurry.com sudo systemctl status lighttpd.service

[image] RamSet: sudo systemctl status lighttpd.service See below. I did two nslookups back to back. pi@raspberrypi:~ $ nslookup flurry.com Server: 127.0.0.1 Address: 127.0.0.1#53 Name: flurry.com Address: 192.168.1.12 pi@raspberrypi:~ $ nslookup flurry.com Server: 127.0.0.1 Address:…

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 [image] stephens79526: Jun 08 13:19:59 raspberrypi sudo…

Thanks for your help. Let me know, or anyone else, what I should do. Thanks

Ramset, Any suggestions on this issue? Thanks for your help.

What about the same nslookup command on a client, after the raspberry came back online? Form the above test you did locally, Pi-hole was working as expected (after power failure). Is your raspberry hardwired into the router or ar you using the WiFi connection ?

It's a hardwired connection. Here is the output of ifconfig. Should wlan0 be down? eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.12 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::f56a:6de9:acb6:1811 prefixlen 64 scopeid 0x20 ether b8:27:eb:8f:e6:f2 txq…

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 flur…

Here are the results from my macbook pro 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 Name: flurry.com Address: 192.168…

Pi-hole Userspace

Pi-hole stops working after power outage or restart

Help

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled