And I have enabled the dhcp server through the pi-hole admin panel. My understanding is that this means that pi-hole should be resolving DNS for all clients on my network.
Actual Behaviour:
My client (a mac) is still loading ads from domains that are in the blocklists loaded on my pi-hole. For example doubleclick still loads:
Even though my diagnostic file says that doubleclick is blocked:
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] track.leady.cz is 0.0.0.0 via localhost (127.0.0.1)
[✓] track.leady.cz is 0.0.0.0 via Pi-hole (192.168.1.131)
[✓] doubleclick.com is 216.58.194.174 via a remote, public DNS server (8.8.8.8)
I was having issues with the lighttpd service being able to start to I manually removed it and reinstalled it...so I am able to access the web admin UI now.
The second output shows that the expected reply of 0.0.0.0 (flurry.com is a domain that appears on the original blocklists) was not received. The Mac is getting DNS replies from a source other than Pi-Hole.
Are you absolutely certain that these nlsookups are from the Mac terminal only - and not a Mac terminal that is in a ssh session to your Pi? The Pi uses the loopback IP for DNS, but your Mac should not. Here is the output of the command from my Mac using Pi-Hole at xxx.155.
wow...figured it out...did not realize that my work machine had opendns umbrella installed on it. i just disabled it and everything is working great now. thanks for all your help today @jfb