Please follow the below template, it will help us to help you!
Expected Behaviour:
Ad blocking, flurry.com returning with actual IP addresses
Actual Behaviour:
After reinstalling Raspian and Pihole onto my Raspi, and resetting my router settings, the ads are still there. Some of the charts on the dashboard show something is working, but not only are the ads still showing up, nothing under the Blacklist is... well, blacking. After trying a bajillion different solutions, I think I found something actually replicable. Given that it's a URL, it's even harder to find
Not entirely sure what flurry.com is, but I found a few threads advising to run a few commands. When I run nslookup furry.com on my Pi, I just get Address 0.0.0.0, when I run on my Mac, I get the following:
Given that my clue is but a URL, it is even harder to find. So given everything I have tried, whatever is behind flurry.com seems to be the only thing. Running ifconfig doesn't seem to return anything interesting with either:
Your debug log shows that Pi-Hole is working properly. The 0.0.0.0 (or NULL) return is expected for a blocked domain, and flurry.com is a blocked domain.
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] opqyo.voluumtrk.com is 0.0.0.0 via localhost (127.0.0.1)
[✓] opqyo.voluumtrk.com is 0.0.0.0 via Pi-hole (192.168.50.251)
[✓] doubleclick.com is 172.217.2.174 via a remote, public DNS server (8.8.8.8)
The debug log shows that in the 24 hours prior to today at 08:06 am, the following activity was recorded by Pi-Hole:
[2019-01-22 08:06:15.414] Imported 1373 queries from the long-term database
[2019-01-22 08:06:15.414] -> Total DNS queries: 1373
[2019-01-22 08:06:15.414] -> Cached DNS queries: 55
[2019-01-22 08:06:15.415] -> Forwarded DNS queries: 1045
[2019-01-22 08:06:15.415] -> Exactly blocked DNS queries: 273
[2019-01-22 08:06:15.415] -> Unknown DNS queries: 0
[2019-01-22 08:06:15.415] -> Unique domains: 404
[2019-01-22 08:06:15.415] -> Unique clients: 3
[2019-01-22 08:06:15.415] -> Known forward destinations: 2
Since the domain lookup from the Pi correctly returned the NULL IP and the lookup from the Mac did not, the Mac does not appear to be using Pi-Hole for DNS. If you run this command from the Mac terminal, it will show you the true order of the nameservers the Mac is using:
This is telling you that the Mac is not properly configured to use Pi-Hole. it is using Google for DNS and bypassing Pi-Hole. What do you see on this network DNS panel on your Mac? It is likely the same numbers. If so, then edit the settings and put the Pi-Hole IP there, and nothing else. Then apply the changes.
Oh bugger! I had some issues with my DNS a week or so ago, so I guess that is where I changed that. When I deleted the Google DNS servers, it 'defaulted' to 192.168.50.251, do I need a second one?
