12-23-2023 12:50 PM
I have recently setup Adguard Home on a raspberry pi for whole home ad filtering. But devices assigned via Google Wifi DHCP are not able to resolve internet addresses.
- my google wifi router is 192.168.86.1
– the Pi is statically assigned 192.168.86.10
- Custom DNS on router is set to 192.168.86.10.
-devices where I manually set the DNS to the Pi work fine. Devices assigned the DNS via the router can’t resolve anything.
-I understand that google wifi acts as a relay for DNS requests and each device is assigned 192.168.86.1 as DNS via DHCP will be forwarded to the custom DNS , 192.168.86.10 in this case.
However, nothing is being received by adgaurd from 192.168.86.1.
I’ve restart network, factory reset google, reinstalled adguard home. Same issue.
if I add a secondary custom dns like 8.8.8.8 , the devices connect, but are not using the primary DNS, 192.168.86.10. If I remove the secondary, the devices can’t resolve anything.
Ideally, I’d like to continue using Google wifi as the dhcp server for all devices and not use adguards dhcp server.
Any ideas what it might be and how to troubleshoot?
12-26-2023 05:15 PM
Sorry to hear of your setup woes. I have a pi-hole running on a Raspberry Pi for my DNS. I set it up on Google Next WiFi Pro as my pi-hole as the primary DNS server and the router as the secondary DNS server. That way DNS is served via pi-hole, unless pi-hole cannot respond. Then it goes to the router, which defaults to the ISP's DNS servers. Seems to work reasonably for me. Pi-hole can choose from various DNS servers, including Google's, if you are so inclined. So at least on the WiFi Pro, it works as expected. Hope this helps.
02-26-2024 02:20 PM
Hi Nolimits,
We're checking to see if everything's good. Have you seen soandso's response? Have you tried the steps above? If so, how was it?
Looking forward to your reply.
Best,
Dan