Quad 1/8/9 isn't optimal alternative (too much centralization if everyone uses those by default) but running your own is easy.
edit: Thinking of it, anyone knows if it's possible to use that for OS-wide DNS resolves, not just for the browser?
I remember hearing someone complain on HN of their site getting blocked because it shared an IP with an illegal soccer livestream. I can’t imagine they’re doing this to IP blocks owned by CDNs like Fastly, CloudFlare, or CloudFront though. Or are they? Does this regularly break most of the internet for UK customers?
In the case that a blocked site resolved to a Cloudflare IP, it would likely be kicked off of Cloudflare, or geo-blocked for UK users (by Cloudflare).
https://www.ispreview.co.uk/index.php/2025/07/cloudflare-blo...
It looks like this is possible with Chrome-based browsers using a command line flag (--host-resolver-rules) or in Firefox settings. Is there a better way?
So why ControlD? Because I don't want to run my own piHole, basically. They maintain ad block lists that you can edit as you see fit to add things or relax things that may cause issues(which you can't do easily with public ad blocking dns servers).
Why ControlD then and not NextDNS? First, because their support was awesome when I had an issue. AFAICT it was the founder actually emailing me back and forth, and it ended up being my ISP's fault, but I only knew that based on research provided to me by support. Secondly, I got a good deal on a 5-year subscription at one point.
Happy to answer any questions, not affiliated but a fan of the service.
Trying to downgrade or strip extensions from any TLS 1.3 connection will simply break the connection.