The DNS method seems to avoid this, at least I haven’t seen it yet. I saw it a ton with browser based adblockers.
That is a bummer. Can you indicate which services these are out of curiosity?
Mine does not. I do think that the DHCP switch is cleaner because it’s trivial to turn it off and switch back to the router DHCP which has the old DNS settings. You also said “Network without both DHCP and DNS servers is really fun to debug” but if you have the router fallback, it’s easy?
Yeah, don’t buy a cheap SD card! I recommend the Samsung Evo or Pro per these excellent benchmarks. A quality 32GB is only like $10, so why skimp?
Only truly massive websites serve ads from their own domain, or inline, though. We’ll see how this changes over time if DNS based blocking becomes more popular…
Why would this matter? the DNS requests are the thing being dealt with not the HTTP/HTTPS content.
You still need client side blocking for mobile devices that are actually used .. y’know while mobile .. and that’s a LOT of devices. I don’t think client side is going away any time soon on smartphones.
I don’t find this level of sophistication to be necessary, the vast majority of ads are served from distinct DNS domain names. Also, the performance impact of these client side rules is kinda serious, on the order of 25-33%. Try running Speedometer 2.0 with client side ad blocking on and off. You’ll see what I mean.
Also having to configure each device as its own special snowflake with its own special client adblocker is kind of a pain. Very clean to do it at the DNS level for all devices globally.
That said as per above, client ad blockers will still be needed for mobile devices without a doubt. They aren’t going away or anything.