Very few queries on Google Nest

Expected Behaviour:

Hundreds of queries from the various devices on my wlan0 network

Actual Behaviour:

Only receiving about 15 queries, which only seem to be originating from my laptop, which still gets ads, some of which are actually in the adlist provided. I originally had zero queries, and I was able to get a few by switching the bash command from eth0 to wlan0, but it hasn't changed from that value. I think it has something to do with the DNS and DHCP, but from others it seems that Google Nest isn't the easiest to get working on that front

Debug Token:

https://tricorder.pi-hole.net/7n3UnYtI/

Your router is the DHCP server and is correctly offering the Pi-hole OS an address from a typical range of 1 through to 254 (or some subsection of those) on the wireless interface. But the address configured on the interface is a single IP which can only communicate with the router and no other clients. On top of that, Pi-hole is configured to use the ethernet wired interface, which is not connected.

To fix this, first of all try to sort out the IP addressing so that the OS has a static IP on the desired interface. For example if the interface uses DHCP, you can reserve the IP address in the router and the Pi OS will always get that IP. Or you can set it manually so it doesn't use DHCP.

The address should have a subnet mask of /24, also known as 255.255.255.0. It should be a 192.168.86.x address because that is what the router is configured to use and your other clients will be on that range. Once done, try pinging it from another machine and it should be reachable and responding.

Once the network is happy, reconfigure Pi-hole and ensure the correct interface – wifi or ethernet – is selected. You can do that from the terminal with

pihole -r

and select Reconfigure when prompted, then follow the prompts.

Once done, you can test it's working from a client computer, like your laptop, by opening a terminal and typing (using the Pi-hole's IP address)

nslookup flurry.com 192.168.86.x

It should be blocked and give a 0.0.0.0 response and you should see the query when you refresh Pi-hole's Query Log. If so then it's all working and you can start using it.

I have a friend who had Google Nest and I seem to remember that they hard code their own DNS into the firmware so they bypass Pi-hole.

So DHCP and DNS are different? I thought I made the IP static already, and I did end up switching it from Ethernet to wlan0. So now while I am getting queries from the network, when I try to make that IP the only one Google communicates with (along with 8.8.8.8 for a fallback) it only uses the 8.8.8.8

Additionally, disabling the DHCP settings in Google nest and enabling them in pi hole just make it so we don’t have WiFi

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.