I co-develop a FOSS DNS client and a DNS stub-resolver which builds blocklists based off of the
nextdns/metadata repository. Recently, I happened to notice that there's at least one AGPLv3 blocklist (ZeroDot1's
CoinBlocker list specifically) that the
nextdns/metadata repository links to (and which the NextDNS resolver) and our FOSS stub resolver uses it, but under a different name viz.
A couple questions:
Do SaaS DNS resolvers (like NextDNS and us, RethinkDNS) that use these blocklists (host files) violate AGPLv3 (when the SaaS code itself is not distributed under AGPLv3)?
If I combine/merge an AGPLv3 host file (blocklist) with other host files and distribute the combined/merged host file (blocklist), do I have to make the source code that was used to combine/merge the host files available under AGPLv3, too?
If I retroactively remove traces of any AGPLv3 licensed blocklists from my SaaS, do I stop violating AGPLv3? That is, can I undo violation and keep my code under existing licenses (MPLv2 and Apache v2).