Hi, I've been searching this discourse for an answer for days, since the last update of Chrome pihole does not "work", or rather Chrome does random shit I've never asked for.
I've disabled async DNS, flushed the cache in Chrome and Windows 10, If I do a "nslookup" on the domains that I want to block everything is as it should.
But somehow Google Chrome still manages to lookup these addresses, what the heck is Google doing with the browser under the hood?
Google Chrome: Version 83.0.4103.116 (Official Build) (64-bit)
Firefox: 77.0.1 (64-bit)
Edge: Version 83.0.478.54 (Official build) (64-bit)
Expected Behaviour:
Google should not be able to resolve addresses that are blocked via pihole.
Actual Behaviour:
Google still manage to resolve the addresses, so it's nothing wrong with pihole per se, but the problem lies withing Google Chrome.
Search within your browser's privacy settings for yet another feature in Chromium browsers that may redirect DNS traffic - look for an option innocently named "Use a web service to help resolve navigation errors" or similar: