Please follow the below template, it will help us to help you!
Expected Behaviour:
Working p-hole.
Actual Behaviour:
FTL service offline, not ad-blocking. New install.
Working p-hole.
FTL service offline, not ad-blocking. New install.
It looks like you have a few problems:
The check below should return 0.0.0.0 for the first two checks, since that domain is on your blocklist. Pi-Hole failed to block it.
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] content.adservingfactory.com is 5.254.100.250 via localhost (127.0.0.1)
[✓] content.adservingfactory.com is 5.254.100.250 via Pi-hole (192.168.200.10)
[✓] doubleclick.com is 216.58.193.206 via a remote, public DNS server (8.8.8.8)
From the above, it appears that pihole-FTL is not running or answering queries. What is the output of this command from the Pi terminal (we're checking for all ths services on ports used by Pi-Hole and add-on DNS resolvers):
sudo netstat -nltup | grep 'Proto\|:53 \|:5053 \|:5353 \|:8953 \|:67 \|:80 \|:471'
Lastly, you have Pi-Hole at IP 10, so you shouldn't be using that IP for DNS1 (Pi-Hole can't resolve its own upstream queries):
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.168.200.10/24
IPV6_ADDRESS=
PIHOLE_DNS_1=192.168.200.10
I appreciate the response. I ended up reinstalling in this order to get it working. Basically, I didn’t follow the guide in the documentation that assumes pi hole is already installed. Redirecting...
Raspbian
Pi-hole
Unbound
*Added 127.0.0.1#5353 as the custom pi-hole DNS
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.