That doesn't mean it's not decentralized. If the .kz operator has a heavy hand, it affects people in their legal jurisdiction but not anyone else, and that's true of everything else as well. A system which doesn't allow enforcement of legal requirements will be blocked, and this isn't a technical problem with a technical solution no matter what the blockchain salespeople say.
They don't change the fact of the centralized structure.
The center used to be Jon Postel, now it's ICANN.
It's a hierarchy of delegated authority (aka "bailiwick"... aka "domain") emanating from the center.
> no one entity owns the entire data set
Because of the delegated authority.
But the authority is all delegated from a center.
It means there's a central point where names can be removed.
The central point owns as much of the data set as they choose to own.
Less inaccurately, ICANN has social consensus to be trusted with the root delegations. If they abuse that position, that consensus would very quickly disappear because they don’t own any of it.
I only explain that DNS delegation is structured with a central `.` zone.
The central node is all-powerful. It can remove any name by removing the top level delegation for that name.
Yes, but authority can be delegated recursively, thus disempowering the top of the tree (ICANN) over the leaf nodes (the rest of us). The root server could technically lie and say thepiratebay.org.'s A record is 127.0.0.1, but recursive resolution (from right to left) prevents that so that only a direct parent could lie.
So because you can get names from pretty much everyone and only a direct parent has authority over you, power is very balanced overall.
That's silly. There's a single organization in charge of everything, with total enforcement power.
> The root server could technically lie and say thepiratebay.org.'s A record is 127.0.0.1
They don't have to "lie."
The people who own `.` can simply issue public orders to the people who own `org.`. They can set policies, demand payment, demand the removal of hosts, and so on.
Since `.` has the power to remove the `org.` delegation, the owners of `org.` are forced to comply.
Maybe i've missed a few episodes in the DNS wars saga. Do you have a few links on this topic? I wasn't aware that ICANN felt powerful enough to threaten to take entire TLDs off the root zone.
> I wasn't aware that ICANN felt powerful enough to threaten to take entire TLDs off the root zone.
What do you think happens if you don't pay ICANN the fee for a gTLD?
Of course, they're not going to remove `org.` -- and `org.` isn't going to defy their rules.
I somewhat agree with that argument, i'd be much happier with a public-key delegation process like in the GNU Name System. But to be fair, given the technical constraints of the time, i would argue DNS is as close as you can get to an anarchist protocol: it appears centralized on the outside, but when you dig into the technical details it was explicitly designed to decentralize powers from the hands of the hosts file maintainers.
> Of course, they're not going to remove `org.` -- and `org.` isn't going to defy their rules.
Do you have examples of .org being ordered by ICANN to take certain actions? Or .org domains being seized? wikileaks.org and thepiratebay.org, which arguably a lot of people have tried to take down over the years are still around and well.
_Powers_ aren't decentralized at all. Only administration and hosting is decentralized. Every single power has to be delegated from above, and continuously renewed. That is what makes it possible to cut people off for non-payment.
> Do you have examples of .org being ordered by ICANN to take certain actions?
ICANN's "Registrar Compliance Program" has helpfully published this powerpoint-style summary of their compliance requirements:
https://www.icann.org/en/system/files/files/registrar-compli...
However, I would say that the most important example is simply that ICANN charges an annual fee for each and every domain!
The power to make the rules is the power to demand the rents.