Author: Didier Kryn Date: To: dng Subject: Re: [DNG] hijacking resolv.conf - possible fix?
Le 30/03/2025 à 14:18, Steve Litt a écrit : >> Good to know, but, for the moment I don't consider yet it
>> deserves
>> the burden to install and maintain my own DNS
> All unbound does is pass your dns queries up the chain. It's not
> authoritative. It's very, very simple, and solves the kinds of problems
> discussed in this thread.
So what is it that you want to achieve? I bet the ISP's DNS is just
refering to the very same root DNS as unbound is. So you guys what do
you suspect your ISP's DNS is doing?
The only thing which makes sense to me is the possibility to block
or divert the javascript requests to the AD servers and to cloudfront.
But I'm not sure it would work to barely block all that shit. The AD
industry is not that stupid. Already they know when you switch to
another window and wait untill the scope in on the proper window to
deliver their ADs; they know when you turn the sound off, so that you
need to lower it to a inaudible level instead.
A better approach is to be implemented inside the web browser: let
the AD machinery believe you watch it all but actually divert all the
junk. The Duckduckgo browser on Android does this kind of thing, though
it still displays a blank space in the place of ADs; so it's possible. I
don't expect Firefox to implement this because they seem tied to Google,
but maybe others like Palemoon.