Not sure if this is the right thread but I am having an issue with using the Google search bar. It doesn't give me suggestions when I type something in. I'm sure this is related to my block lists and maybe I'm blocking location tracking via PiHole. Any help on the issue would be very appreciated. Thank you!!
ok...
On the client involved: set manual dns to google. 8.8.8.8
clear dns cache, browser cache or reboot
Re-test. Search bar working? => yes pihole is blocking.
Revert the dns changes to dchp on the client.
Get ip address of the client.
Search the log in pihole for the blocked domain based on the client ip.
I'm currently using open dns as primary and secondary dns on the PiHole. So what your saying is change that to use Google dns and the search bar should work as normal?
It's looking like it still isn't working. I changed my DNS servers to Google DNS and I still get nothing for suggestions. As seen here.
I am getting csi.gstatic.com blocked. But I'm not sure if this is a Google domain or not. ssl.gstatic.com is show as forwarded. Maybe I should whitelist that domain?
Edit: just found that gstatic is a Google domain so I added it to the whitelist. Not sure if it will work or not.
Edit: still doesn't work
No, that is not what I tried to explain.
To my understanding:
On the pihole: you use opendns as upstream?
First pihole checks the local blacklists for block, if domain not found it will use upstream dns to do a lookup.
On the client: you have set dhcp to automatic?
On your dhcp server: server configured to set pihole as dns server?
for the test: client : set fixed google dns 8.8.8.8 on the client? Clear cache Yes?
Still blocked? yes: Error might be on the client.
Try a diffrent device without changing anyting. Blocked? Yes:
Either someting is blocked on pihole blacklists or opendns is blocking something.
Check if encrypted.google.com is blacklisted.
This does not sound like a Pi-hole problem when it persists although you completely changed the DNS server to something like Google.
Yeah your probably right. I'll start by reflashing the firmware on my phone later on and see if that fixes anything
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.