4 ms·
OpenNIC is a poorly managed amateur project, built on shoddy infrastructure that was thrown together in the early 2000s -- it's completely incapable of acting a
by duskwuff 7y ago
OpenNIC is a poorly managed amateur project, built on shoddy infrastructure that was thrown together in the early 2000s -- it's completely incapable of acting as any kind of peer to the ICANN root. In particular:
- Their resolvers are not consistently available. Many of them are hosted on public cloud hosts (which also raises some questions about their security), and outages are not uncommon.
- It's not clear that they support DNSSEC, or that they have any plan to do so.
- The governance of the OpenNIC-specific zones that they offer is even shoddier than the DNS root itself. Most of them have no registry/registrar distinction, no domain transfer process, no WHOIS services, and sketchy to nonexistent abuse policies.
- Since OpenNIC TLDs cannot be resolved on the public Internet, it's impossible to issue a SSL certificate for one.
- mikedilger 7y agoMost of your points are valid. That's why I'm suggesting Mozilla support it. It would be a lot less "shoddy" if someone shepherded it. I think it is the right idea. The last point is only true because they aren't recognized, which recognition would immediately fix, therefore it is moot.
- duskwuff 7y agoMy concern would be that it's enough of a mess that Mozilla would have an easier time building an equivalent project from the ground up than reshaping this one into something reasonable. I could be convinced that a community-based restructuring of DNS could be for the better. But I don't think that OpenNIC is the right project to base that around. The technical aspects of what they've built are not complicated, and much of that would need to be changed anyway to operate at scale; good governance is a lot harder to build.