> ...grew out to become a worldwide multi-node adblocking DNS network with thousands of concurrent users around the globe This is hard because DNS going down m

> ...grew out to become a worldwide multi-node adblocking DNS network with thousands of concurrent users around the globe This is hard because DNS going down means Internet is down for anyone who isn't savvy to check and change a failing DNS upstream. And when your users are global, it might mean some really angry users if you couldn't fix emergent issues for hours on end. I run a public content-blocking DNS stub resolver. We made the decision (and subsequently paid the price upfront in terms of engineering) to host it on Fly.io (DoT), Deno Deploy (DoH), and Cloudflare Workers (DoH) to specifically avoid sysadmin tasks for what's a free offering, and the code is licensed under MPLv2 in case anyone wants to run their own stub resolver on those platforms. We haven't had much down time, if any at all, in the past one and half years we have been functional. It costs us $1 per 2tps (transactions per second: ~6M requests) for a month. The free-tier of these platforms should cover personal workloads (3 to 5 devices: ~1M requests), just fine. > I will make sure to keep the domain registered and under my control for the next year, to prevent adhole.org from being abused by DNS hijackers/spoofers. I think they could, if they want to, transfer the ownership of the domain to another public content-blocking resolver, after a year has passed. There are two or three such providers that have a very solid business backing them up to support such a migration.