3 ms·
If Verisign is running the nameservers for .com and .net, it will cause DNS problems across the board. We'd have to rely on DNS caches until new .net and .com n
by falcolas 10y ago
If Verisign is running the nameservers for .com and .net, it will cause DNS problems across the board. We'd have to rely on DNS caches until new .net and .com nameservers come up. This would impact not only new domain registrations, but DR grade migrations, and DNSSEC.
If coordinated with an attack against the root nameservers so we couldn't change the .com and .net nameservers, DNS would become a real disaster. If combined with some BGP trickery, you could even see domain names being poisoned.
We should be able to be worked around the damage eventually; but so much of the internet relies on so few root servers/hosts/routers.
- reitoei 10y agoWould there a use case for decentralizing DNS into blockchain, or for creating an alternative?
- cwkoss 10y agoThis is one of the goals of Namecoin, but I'm not sure how successful they've been so far.
- deleted 10y ago[deleted]
- duaneb 10y agoFor some reasons to use DNS (e.g. service discovery) the latency associated with a blockchain would be prohibitive. Generally, I think it's an excellent application.
- falcolas 10y agoI think the problem with the blockchain is that it is relatively immutable, while the internet is anything but. Also, the cost for making a Namecoin change is inexpensive now, but if it were to take over full operations for even one TLD, that would not remain the case.