I feel for the team behind it; running a DNS service can't be cheap, especially when you're trying to stay green. Maybe a community‑funded model could keep it alive? Just a thought.
Probably something like the NTP pool [1] model could work but I can also see people abusing that by adding nodes that rewrite zones or specific records to MitM people. I only mention this model because it scales very well and people can contribute resources they can afford but they can also withdraw from the pool without harming the community [2] in regards to funding resources at least. Some type of automation would have to continuously validate each pool member and use a unique assigned NSID or id.server that maps to an operator account.
Each person just runs a node with a specific Unbound [3] configuration and pulls filter lists from community approved repositories. I mention Unbound as it is one of the most flexible and powerful recursive DNS options and many here are already using it. Bootstrapping could come from a static updated file in a repository that gets refreshed via cron.
Bender|4 months ago
Each person just runs a node with a specific Unbound [3] configuration and pulls filter lists from community approved repositories. I mention Unbound as it is one of the most flexible and powerful recursive DNS options and many here are already using it. Bootstrapping could come from a static updated file in a repository that gets refreshed via cron.
[1] - https://www.ntppool.org/en/
[2] - https://community.ntppool.org/c/server-operators/6
[3] - https://nlnetlabs.nl/projects/unbound/about/