4 ms·

I'm sure anyone here who has set up a PiHole ad-blocking DNS server at home has run into these random domain requests and wondered what was going on. At first I

I'm sure anyone here who has set up a PiHole ad-blocking DNS server at home has run into these random domain requests and wondered what was going on. At first I thought one of my devices had a virus on it or something until I did a few searches and discovered it was Chrome being ludicrous. (Next topic: Getting Chrome to actually use the DNS provider that you specify and nothing else...)

gzer0 6y ago
Would these have occurred on a sever that has unbound as its upstream?
- jlgaddis 6y ago
  Why wouldn't they? Chrome doesn't care what DNS server software is in use (even if it could figure that out), it cares whether it's behaving properly or not.
merlinscholz 6y ago
I recently just blocked port 53 in my firewall completely, for that exact reason. I use an internal DNS server the forwards to an DOH upstream server. No more rogue devices trying to use their own dns, at least until they all switch to DOH too
- samoa42 6y ago
  > No more rogue devices trying to use their own dns, at least until they all switch to DOH too nice that you already debunked your thesis
- nikeee 6y ago
  I also blocked port 53 in my firewall (except for the Pihole; no DoH there). After that, I noticed that some applications have some DNS servers hard-coded. 8.8.8.8 being pretty prominent. My solution was to assign the Pihole the IP address 8.8.8.8 as well. Then I added a static route in at the router to route 8.8.8.8 to the Pihole. Now every request to dns.google will also be handled by pihole instead of getting timeouts.