Set up PiHole on Buster and it is not working
Ads are still getting through on websites and apps. If I run an nslookup, it is showing that my DNS is set to my default gateway first and PiHole second. On the router, the only DNS I have set is for the PiHole. I use an Eero for my router.
[✓] Your debug token is: https://tricorder.pi-hole.net/jkrdkem59k
You can set Pihole as the DNS host in your router, or you can turn on the DHCP function of pihole after turning off the DHCP function in the router.This is just my personal advice, for your reference only, and can't replace the professional answers of Pihole developers.
Yeah I have the DNS set to the PiHole in the router already. Its actually the only DNS that is set in my router.
Or you can try the DHCP mode？
Welcome to the Pi-hole community.
Could you post both the exact nslookup command as well as the resulting output here, preferably by copy and pasting the text?
This is what I am getting on my Mac:
iMac:~ iMac$ cat /etc/resolv.conf
#
# macOS Notice
#
# This file is not consulted for DNS hostname resolution, address
# resolution, or the DNS query routing mechanism used by most
# processes on this system.
#
# To view the DNS configuration used by this system, use:
# scutil --dns
#
# SEE ALSO
# dns-sd(1), scutil(8
#
# This file is automatically generated.
#
nameserver 192.168.7.1
nameserver 192.168.7.194
And on Windows:
C:\Users\Windows>nslookup pi.hole
Server: Unknown
Address: 192.168.7.1
*** Unknown can't find pi.hole: Non-existent domain
You can format your output for readability by using the </> preformatted text menu option.
I've just done that for you 
I am not familiar with macs, but the comment suggests to use another command.
Could you run that as well, please?
Also, from your Windows machine, what DNS servers get listed if you execute:
ipconfig /all
EDIT: Just the line(s) showing the DNS server(s) will do.
iMac:~ iMac$ scutil --dns
DNS configuration
resolver #1
nameserver[0] : 192.168.7.1
nameserver[1] : 192.168.7.194
if_index : 4 (en1)
flags : Request A records
reach : 0x00020002 (Reachable,Directly Reachable Address)
resolver #2
domain : local
options : mdns
timeout : 5
flags : Request A records
reach : 0x00000000 (Not Reachable)
order : 300000
resolver #3
domain : 254.169.in-addr.arpa
options : mdns
timeout : 5
flags : Request A records
reach : 0x00000000 (Not Reachable)
order : 300200
resolver #4
domain : 8.e.f.ip6.arpa
options : mdns
timeout : 5
flags : Request A records
reach : 0x00000000 (Not Reachable)
order : 300400
resolver #5
domain : 9.e.f.ip6.arpa
options : mdns
timeout : 5
flags : Request A records
reach : 0x00000000 (Not Reachable)
order : 300600
resolver #6
domain : a.e.f.ip6.arpa
options : mdns
timeout : 5
flags : Request A records
reach : 0x00000000 (Not Reachable)
order : 300800
resolver #7
domain : b.e.f.ip6.arpa
options : mdns
timeout : 5
flags : Request A records
reach : 0x00000000 (Not Reachable)
order : 301000
DNS configuration (for scoped queries)
resolver #1
nameserver[0] : 192.168.7.1
nameserver[1] : 192.168.7.194
if_index : 4 (en1)
flags : Scoped, Request A records
reach : 0x00020002 (Reachable,Directly Reachable Address)
Ahh. I gotcha! Formatting success! 
Here is the output for that.
Also for Windows it is giving me this:
DNS Servers . . . . . . . . . . . : 192.168.7.1
192.168.7.194
Both results show that your router is still pushing itself as DNS server, in addition to Pi-hole.
Verify that Pi-hole is set as your only DNS server in your router.
Some routers / firmwares are into a bad habit of distributing themselves in addition to any DNS server you configure.
If that seems to be the case for you, you could disable DHCP on your router and enable Pi-hole as DHCP server.
Yeah it shows in my router that the Pi-hole is the only DNS server listed, so Im not sure why its doing that. Heres a screenshot from my Eero app showing.
deHakkelaar is suggesting you double-proof your router is adding itself to the list of DNS servers, just to be sure. If you wish, you could do so by running the commands he provided in his linked post (and possibly by installing some additional software).
Given the fact that we have confirmed the additional DNS on two different devies running two different OSs, I am fairly confident that a manual DHCP discover will confirm your router is misbehaving.
As another option apart from enabling Pi-hole's DHCP, you could try and see if adding PI-hole into every available slot on your Eero would work.
@deHakkelaar's manual DHCP would then come in handy to quickly establish if this changes anything for you.
I am going to give that a whirl tomorrow. I also spoke with Eero so see if it was something on the router side and they confirmed everything is correct and are saying its a RPi issue. So I am not sure.
If in doubt, see above ^
So what I found out, eero enabled HomeKit on the routers 2 days ago. With HomeKit, the default gateway is the primary DNS and currently there is no way around that. So I disabled HomeKit and rebooted the router and now the primary DNS is the Pi-Hole and all is well.
Thank you for the help both @Bucking_Horn and @deHakkelaar!
There should not be a secondary DNS server (other than Pi-hole) configured/pushed by router or else ads etc will still leak through:
Yeah I have the Pi-Hole as the primary and secondary DNS
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.
