Latest news of the domain name industry

Recent Posts

AusRegistry chalks up third Arabic domain win

AusRegistry International has announced it has been picked to provide the back-end registry for عمان., the Arabic-script internationalized domain name for Oman.

It’s the company’s third IDN ccTLD contract in the region, following on from Qatar’s forthcoming قطر. and the United Arab Emirates’ already-live امارات.

The company’s press release suggests to me that it’s a software/support deal, rather than a full-blown hosted back-end registry solution.

AusRegistry said it will “provide Domain Name Registry Software and supporting services for the establishment of a new Domain Name Registry System”.

It has previously announced back-end deals for ASCII ccTLDs including .qa and .ae, and manages Australia’s .au, which recently passed the two million domains milestone.

The deal with Oman, which AusRegistry said was competitively bid, also encompasses .om, the nation’s regular ccTLD.

While ICANN approved Oman’s chosen string under its IDN ccTLD Fast Track program back in October, it has not yet been delegated to the DNS root zone.

With the approval of Ukraine’s Cyrillic ccTLD last week, 25 territories have had their choice of local-script ccTLD given the nod under the program.

ICANN accused of Twitter faux pas over Arabic domains

The registry behind one of the new Arabic-script ccTLDs has sharply criticised ICANN for the way it introduced internationalized domain names to the root this week.

Adrian Kinderis, CEO of AusRegistry, accused ICANN, specifically those responsible for the IANA function, of “embarrassing incompetency” and cultural insensitivity.

Kinderis’ beef is that IANA added the three new Arabic IDNs to the root without giving their local managers so much as a headsup.

AusRegistry is the back-end provider for امارات. the United Arab Emirates’ new IDN ccTLD, as well as its ASCII original.

“I was alarmed to discover that the relevant ccTLD Managers were only notified many hours after the fact, long after the same IANA staff member had broadcast the news on a personal Twitter account,” he blogged.

While Kinderis was diplomatic enough not to name names, he’s talking about IANA registry manager Kim Davies, who broke the web-changing news on Wednesday with a tweet.

“This was an inappropriate manner in which to announce an event of this importance,” Kinderis wrote. “It displays a disturbing lack of understanding and a complete disregard of the cultural and political significance of this event within the Arabic world.”

He goes on to point out that the announcement was made during Saudi Arabia’s weekend, leaving ccTLD managers scrambling to get their marketing in place on their day off.

I could keep quoting. It’s a fairly extraordinary attack on aspects of ICANN’s culture. Go have a read.

The internet is polyglot as full IDNs go live

Click this: http://وزارة-الأتصالات.مصر/

It’s the Egyptian Ministry of Communications and Information Technology, owner of one of the world’s first fully non-ASCII internet domain names.

If you hover over the link, you might see the Punycode translation appear in your browser’s bottom bar, even though the href itself is in Arabic script.

Thanks to ICANN, from today the Latin script no longer has a stranglehold on the domain name system.

I’m afraid I won’t be able to tell you what the three newly created internationalized domain name ccTLDs are, because none of the software on my machine wants to let me use them in a sentence without switching my cursor to right-to-left editing mid-way through the word or changing the characters entirely, and after ten minutes of beating my head against the keyboard I gave up.

Anyway, the new domains represent Egypt, Saudi Arabia and the United Arab Emirates.

They were all recently approved by ICANN as part of its “fast-track” IDN ccTLD process, which promises to give countries the equivalent of their ASCII ccTLD in their native script.

After 25 years, the English language no longer has exclusive rights on the DNS. Not what I’d call a “fast” track, but we got there eventually.

ICANN has more here.