.uk.co Is Toast
Date: Friday February 21 2003, @06:06AM
Topic: Country-Code Top Level Domains (ccTLDs)

Further to our earlier item, a Columbian court has ruled that the registrant of .uk.co had lost its rights to the domain, and hence the 8,000 or so sub-registrants of third level domains are up the creek without a paddle. It's hard to see how this in any way adds to the stability of the internet -- wouldn't we be better off with more gTLDs so no one had to rely on jury-rigged work-arounds?

News coverage:
Europemedia.net (most up to date I've seen)
Web hosting news

This discussion has been archived. No new comments can be posted.
.uk.co Is Toast | Log in/Create an Account | Top | 1 comments | Search Discussion
Click this button to post a comment to this story
The options below will change how the comments display
Check box to change your default comment view
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
That's to be expected...
by dtobias (dan@tobias.name) on Friday February 21 2003, @10:57AM (#11212)
User #2967 Info | http://domains.dan.info/
Whenever you register a domain in a country code, you're ultimately putting your address under the control of the country in question, even if somebody has "repurposed" the TLD for marketing reasons and claims it means something else. .co is the country code of Colombia, .tv is the country code of Tuvalu, and .tm is the country code of Turkmenistan, and even if somebody claims that they "really" stand for companies, television, and trademarks respectively, they still are ultimately under the control of the countries they really stand for, which can arbitrarily change the rules at any time and leave you no recourse, especially if you're a non-citizen of that country.

Also, if you register a third-level domain (other than in TLDs that expressly offer registrations by the registry or authorized registrars at that level, such as .name and .museum), you're at the mercy of the 2nd-level registrant your domain is beneath, as well as the TLD registry which can yank the 2nd-level registration (killing all subdomains beneath it), possibly in connection with disputes to which you're not even a party. No ICANN agreement controls, regulates, or provides recourse for actions regarding 3rd-level subdomains; you're on your own if they go bad on you.
[ Reply to This | Parent ]

This article comes from ICANNWatch

The URL for this story is: