Conflicts and Skulduggery
Date: Thursday March 29 2001, @03:48AM
Topic: Country-Code Top Level Domains (ccTLDs)

The Third Rail reports on conflict at the Azerbaijan .az ccTLD and on what it describes as an attempt to hijack the Nauru .nr ccTLD.

Both these stories suggest that a number of ccTLD redelegation conflicts likely will land in IANA's lap in the next few years. The result of which will be that, unless some countervailing force appears (GAC? EU?), ICANN's control over ccTLDs is likely to increase since IANA is now little more than a wholly-owned subsidiary of ICANN. (Not to mention the effects of the new ccTLD-ICANN contracts currently being drafted.)

Meanwhile, consider this excerpt from the Third Rail account of the attempt on .nr:

According to correspondence relayed to the Third Rail, in February 2001 ... [the .nr administrator] received a call from the Nauru Olympic Committee who "ordered" him to "make some adjustments" to the servers that control .NR. The "adjustments" would have relayed DNS requests to the Nauru Olympic Committee's server in Melbourne and given that server effective control over the domain. Mr. Appi was also asked to call Telstra, which operates the secondary nameserver for .NR, to mirror those changes. Finally, he was ordered to install PCAnywhere "to enable minor configuration changes remotely - from time to time. ... The Nauru Olympic Committee was told to "get @#$%^**!!." "
My e-mail to the Nauru Olympic Committee asking for comment has so far gone unanswered. I wouldn't be surprised to hear that there are two sides to this story, and if the other one ever turns up, I will update this item.

This discussion has been archived. No new comments can be posted.
Conflicts and Skulduggery | Log in/Create an Account | Top | 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.

This article comes from ICANNWatch

The URL for this story is: