Follow

docs.pi-hole.net/main/faq/

"This happens when using Chrome-based browsers. Chrome tries to find out if someone is messing up with the DNS (i.e. wildcard DNS servers to catch all domains). Chrome does this by issuing DNS requests to randomly generated domain names with between 7 and 15 characters

"In a normal setup this results in a “No such name” response from your DNS server. If the DNS server you use has a wildcard setup, each of these requests will result in a response (which is normally even the same) so Chrome knows that there is someone messing around with DNS responses."

So, Chrome checks to see if you're doing DNS adblocking. Fuckin' Google.

@drwho to be honest, they only do that because scummy ISPs are even worse and hijack the search traffic.

...which they want for themselves, so back to "fuck'em", I guess.

@zladuric Two hands, two middle fingers. Only choice is which one.

@drwho I don't think pi-hole does return answers for those? The FAQ seems to just be explaining why they show up in its log.

@freakazoid The Pi-Hole doesn't. It should return an NXDOMAIN. Chrome is treating it as "The local DNS can't be trusted, so I'll start using Google's DNSes," which means it's collecting net.activity. Coupled with their breaking the knees of adblocking with Manifest v3, and...

Fuck. Hang on, quick game of Gunshots or Fireworks.,

@freakazoid Fireworks. Somebody let off a handful of M80's all at once.

@drwho That's not what Chrome is doing. It's not detecting adblockers, it's detecting ISPs that redirect typo'd domains to ads.

@easrng I don't think that's the primary use case, but I do think it's an advantageous side effect.

@drwho how would querying (almost-certainly-)nonexistent domains detect an adblocking DNS server?

@easrng Fingerprinting the responses is the first thing that comes to mind.

Depending on whether or not I can resuscitate Cloudbuster, my next home project is setting up a Pi-hole so I'll be able to test this hypothesis.

If I was them I'd go a little bit farther in detecting threats to my revenue stream, but going farther than I need to is kind of my jam.

@drwho There's no difference in behavior between Google's DNS and adblocking DNS for nonexistent names: diffchecker.com/FdtsLGwo
Here's what it looks like when there is hijacking: diffchecker.com/olaupX6a
Here's the Chromium code responsible for the checks: source.chromium.org/chromium/c

on a tangent re: what level3 does with NXDOMAIN responses 

@drwho The IP returns a page (paste.debian.net/plain/1253678) which redirects to searchguide.level3.com/search/ which has whitelabeled yahoo search results and maybe ads.

@easrng Thank you very much. Seems my cow-orker wasn't the only one on a hair trigger yesterday.

Sign in to participate in the conversation
hackers.town

A bunch of technomancers in the fediverse. This arcology is for all who wash up upon it's digital shore.