It is certainly easy to read any Wiki too much.
But, to appease your Wikiness...
en.wikipedia.org...
en.wikipedia.org...
Review those to understand how the DNS system works, and focus on the TLD. Basically, there is a series of computer systems at the top of the
hierarchy that determine where .coms, .govs, .orgs, etc are regulated. They also determine what IPs in what countries are authoritative over their
country suffix (.uk, .it, .ro, etc). Last I worked with DNS there were 16 TLDs if I recall correctly, housed at various universities and government
locations. I'm sure much has changed since then. But the necessity to have them centrally located on the base US arpa network has not... until now
obviously.
Decentralizing the system brings immediate conflict issues and possible route problems. If you were to try to look up a host in some other country,
normally your DNS request would be bounced around until it got to the TLD that told it to go to .xx country nameserver. If that country is in control
over where that .xx nameserver is, the first TLD you encountered may not know the location. Basically, it's going to be a really big expensive
headache to make sure everything stays synced up and works together properly. And that's not even getting into any ARPA TLD transitions... wow
that's gonna be fun.