I don't know. I'm using it now in the form of pihole, but DoT/DoH with ESNI are coming, and we don't have a good way to ID and block them by their very nature, which is the bad edge of the double-edged sword that they enable.

The good edge is keeping ISPs etc. from messing with your DNS requests, but that sword cuts both ways as it also can lock your own home network out.

I don't understand what is it with DNS-based blocking people that they seem to be some of the most annoying proselytizers. Anyone remembers the "HOSTS file guy" from Slashdot ?

DNS-based blocking is as much a "future-proof" technology as "just don't look at the adverts". DNS-based blocking is old, easily workaroundable by anyone (just use the same domain name for everything, or interchangeable domain names, or just don't rely on system DNS), and significantly less featureful than even the simplest DOM/JS-based blocking (e.g. good luck collapsing ad elements from the view, getting Youtube not to play ads, etc.).

> DNS-based blocking

Google cracks down on VPN based adblockers https://news.ycombinator.com/item?id=32636412

DNS based ad blocking is slightly different than VPN based blocking. VPN is there for people running environments where DoH is not yet supported.

Newer versions of iOS, Android and Windows support it already.

I think a hosted browser might be key to solving this. Something like Mighty (https://mightyapp.com) if it were self-hosted or somehow run by an org you could trust (or be run in some verifiably zero-trust way).

Until DoH becomes standard/required?