3 ms·

There is no "transfer" of anything. Anyone can edit the root.zone file. I use my own curated version. Great for blocking ads, etc. But for many years no one

There is no "transfer" of anything. Anyone can edit the root.zone file. I use my own curated version. Great for blocking ads, etc. But for many years no one did this, except very rarely. And the honors were left to some folks in the US, IANA/ICANN. Do not be fooled by the acronyms and the fabricated processes and formalities on the official websites. IANA was essentially one person. Bless the hearts of those who worked to create the early internet but these "organizations" derive their "authority" from nowhere. The internet is an abstraction, a term to describe different networks that cooperate. The generally static nature of the root.zone file changed recently. It has doubled, maybe tripled in size and is now filled with TLDs such as .loans and .cologne. As well as trademarks such as .google, .microsoft, etc. These can also capture traffic from users who type strings into address bars that are not FQDNs. ICANN charged $85K+ just to bid on these beauties; they made some very easy money. Most of them are worthless. Exit time for ICANN. :) Now that it is filled with garbage, and perhaps anticipating some finger-pointing, it is time to acknowledge that the root.zone belongs to everyone and is managed by all countries of the world, not only the US. The "transfer". More fabricated formalities. The truth is that anyone can exercise control over the root.zone file, and anyone can serve it. Whether you choose to follow them or not is up to you. (Most users just let default DNS settings decide this for them.) Similar to the early IANA, one person can do this job. I maintain and serve my own root.zone. I am the only user but there could just as well be hundreds of users. This could grow to thousands which could grow to millions which could grow to hundreds of millions which could grow to... This is what happened with the DNS. It started out small and grew big. Believe it or not it is still not that big. I could fit all domain names in existence on consumer-sized storage media. Thus concludes an opinion. Mildly informed.

kijeda 10y ago
This doesn't make a whole lot of sense. Sure, anyone can create their own root zone. I can create my own .com zone too and point my resolver to it instead. But what use is it if it doesn't contain useful entries that point to things I want to access? What use is it if all the parties underneath it aren't sending me updates to the zone? Someone has to do that job for it to all work. Do the managers of the hundreds of TLDs around the world contact you to update your version? No, they send them to IANA. The IANA's job is simply to be the authoritative repository of unique identifiers and associated configuration data — TLDs, IP addresses, port numbers, MIME types, etc. You are free to use your own bespoke IP addressing scheme, port numbers and MIME types too, but don't expect to be able interoperate with anyone else.
mindslight 10y ago
Sure, but there's a strong attractor for using the same root zone everyone else is using, by following the generally recognized steward (hence root.hints). Especially with naive protocols like http that lookup a name for every single object retrieval. For instance, I'd love it if this recent TLD vomit could be nipped in the bud by people choosing to run their own root.zone. But as it stands doing so myself would merely inconvenience me. And this herd effect is magnified further because the custom is for ISPs to run recursive resolvers for their customers.

kijeda 10y ago

This doesn't make a whole lot of sense. Sure, anyone can create their own root zone. I can create my own .com zone too and point my resolver to it instead. But what use is it if it doesn't contain useful entries that point to things I want to access? What use is it if all the parties underneath it aren't sending me updates to the zone? Someone has to do that job for it to all work. Do the managers of the hundreds of TLDs around the world contact you to update your version? No, they send them to IANA. The IANA's job is simply to be the authoritative repository of unique identifiers and associated configuration data — TLDs, IP addresses, port numbers, MIME types, etc. You are free to use your own bespoke IP addressing scheme, port numbers and MIME types too, but don't expect to be able interoperate with anyone else.

mindslight 10y ago

Sure, but there's a strong attractor for using the same root zone everyone else is using, by following the generally recognized steward (hence root.hints). Especially with naive protocols like http that lookup a name for every single object retrieval. For instance, I'd love it if this recent TLD vomit could be nipped in the bud by people choosing to run their own root.zone. But as it stands doing so myself would merely inconvenience me. And this herd effect is magnified further because the custom is for ISPs to run recursive resolvers for their customers.