DNS Belgium, operator of .be, has moved its shared registration systems to the cloud, the non-profit said last week.
The registry migrated from a self-hosted system to Amazon Web Services on February 11.
It’s an effort to cut costs, increase efficiency, and free up engineering time currently dedicated to non-core functions such as hardware maintenance, executives said.
“As AWS sees to the hardware, connectivity etc., DNS Belgium can focus on the layers above, such as the software,” general manager Philip Du Bois said in a press release.
Business development manager Lut Goedhuys said that while the system has been moved to the cloud, AWS allows customers to select the data centers where their applications will be stored.
DNS Belgium picked Ireland, she said.
New gTLD registry operators have been given the right to start selling two-letter domains that match country codes.
Potentially thousands of names could start being released next year, resulting in a windfall for registries and possible opportunities for investors.
Some governments, however, appear to be unhappy with the move and how ICANN’s board of directors reached its decision.
The ICANN board yesterday passed a resolution that will unblock all two-letter domains that match country codes appearing on the ISO 3166 list, most of which are also ccTLDs.
While the resolution gives some protection to governments worried about abuse of “their” strings, it’s been watered down to virtually nothing.
In the first draft of the rules, published in July, ICANN said registries “must” offer an “Exclusive Availability Pre-registration Period” — a kind of mini-sunrise period limited to governments and ccTLD operators.
In the version approved by ICANN yesterday, the word “must” has been replaced by “may” and the word “voluntary” has been added.
In other words, registries won’t have to give any special privileges to governments when they start selling two-character names.
They will, however, have to get registrants to agree that they won’t pass themselves off as having affiliations with the relevant government. It looks like registries probably could get away with simply adding a paragraph to their terms of service to satisfy this requirement.
Registries will also have to “take reasonable steps to investigate and respond to any reports from governmental agencies and ccTLD operators of conduct that causes confusion with the corresponding country code in connection with the use of a letter/letter two-character ACSCII domain.”
This too is worded vaguely enough that it could wind up being worthless to governments, many of which are worried about domains matching their ccTLDs being passed off as government-approved.
The Governmental Advisory Committee is split on how worrisome this kind of thing is.
For examples, governments such as Spain and Italy have fought for the right to get to pre-approve the release of “es” and “it” domains, whereas the governments of the US and UK really could not care less.
The most-recent formal GAC advice on the subject, coming out of the July meeting in Helsinki, merely said ICANN should:
urge the relevant Registry or the Registrar to engage with the relevant GAC members when a risk is identified in order to come to an agreement on how to manage it or to have a third-party assessment of the situation if the name is already registered
“It is our belief that that our resolution is consistent with GAC advice,” outgoing ICANN board member Bruce Tonkin said yesterday, noting that nobody can claim exclusive rights over any string, regardless of length.
Before and after the resolution passed, the GAC expressed “serious concern” that the board had not formally responded to the Helsinki communique.
In its Hyderabad communique, issued after yesterday’s vote, the GAC advised the board to:
- Clearly indicate whether the actions taken by the Board as referred to in the resolution adopted on 8 November 2016 are fully consistent with the GAC advice given in the Helsinki Communiqué.
- Always communicate in future the position of the Board regarding GAC advice on any matter in due time before adopting any measure directly related to that advice.
ICANN staff are now tasked with coming up with a way to implement the two-character release.
My sense is that some kind of amendment to Registry Agreements might be required, so we’re probably looking at months before we start seeing two-letter domains being released.
The Indian government is to urge citizens to register .in domain names instead of .com, according to local reports.
The Economic Times reports today that the Ministry of Economy and IT is to launch a “massive advertising campaign aimed at companies, individuals and startups” promoting .in.
Rajiv Bansal, MEIT joint secretary, is reported as saying the campaign will play up to nationalist sentiments
The government wants to grow .in from about 2.1 million domains to 3 million domains by March next year, it said.
Prices could come down to the $2 to $3 range, the paper said.
The campaign is due to start in a month or so, it was reported.
Governments and ccTLD registries would get new rights to own two-letter domains in new gTLDs under a proposed ICANN policy.
These highly-prized domains, many of which are likely worth thousands or tens of thousands of dollars, would be subject to a mini sunrise period, under the proposal.
The so-called Exclusive Availability Pre-registration Period would be limited to those companies or government entities in charge of matching ccTLDs.
The measures are outlined in “Proposed Measures for Letter/Letter Two-Character ASCII Labels to Avoid Confusion with Corresponding Country Codes” (pdf), published by ICANN late last week.
The surprisingly succinct document outlines three things new gTLD registries must do if they want to start selling two-letter domains matching ccTLDs, which are currently restricted.
The key measure is:
Registry Operator must implement a 30-day period in which registration of letter/letter two-character ASCII labels that are country codes, as specified in the ISO 3166-1 alpha-2 standard, will be made exclusively available to the applicable country-code manager or government.
In other words, if you’re a government or company listed as the ccTLD manager here, you get 30 days of exclusive opportunity to buy the LL.example matching your ccTLD.
Until now, governments have been able to block the release of LL new gTLD domains matching their ccTLDs.
The new proposal, introduced in an attempt to settle a long-running debate about the most appropriate way to enable the release of two-character strings, appears to add a “buy it or lose it” component to existing policy.
Under the base New gTLD Registry Agreement, all two-character domains were initially reserved.
Then, in late 2014, ICANN said registries could release all letter-number, number-letter and number-number combinations.
Many registries have already released such names, some selling for thousands at auction. When Rightside released its LN/NL/NN names, some carried price tags as high as $50,000.
Letter-letter domains could also be released following a formal registry request to ICANN, but were subject to a 60-day period during which governments could object.
Almost 1,000 new gTLDs have submitted such requests, and almost all have been “partially approved”.
That means some governments objected to the release of ccTLD-matching domains. Over 16,000 unique domain names have been objected to and therefore blocked over the last year or so.
The new proposal would add an extra process under which these blocked domains could be released, with ccTLD concerns getting first rights.
Interestingly, it appears to bring ccTLD managers into the mix, rather than restricting the names simply to governments.
The Governmental Advisory Committee has been the main driving force behind demands for restrictions on LL domains, but the proposed policy appears to also extend rights to private entities.
Remember, many ccTLDs are operated independently by private companies, without local government oversight.
For example, .uk is managed by Nominet, a non-governmental entity. The UK government has blocked many uk.example domains from being registered. The new policy appears to allow either Nominet or the government to register these names.
The one-page proposal is light on some details. It does not say, for example, what happens when the government and the ccTLD manager both want the name.
In keeping with ICANN’s habit of staying out of pricing, it does not specify price caps either.
It does, however, oblige registries to ban registrants from pretending to be affiliated with the relevant government when they are not.
Governments also get to complain, and registries have to investigate, if the relevant domains are causing “confusion”, though registries do not appear to be under a strict obligation to delete or suspend domains.
The policy is open for public comment until August here.
The UK may have suffered the most serious self-inflicted wound since the deep-fried Mars bar when it voted to leave the European Union last week, but it seems unlikely to have a huge effect on domain name registrants.
Most EU ccTLD registries do not require registrants to be based in the EU, and those that do have shown themselves flexible.
I surveyed the web sites of all 29 EU ccTLD registries, scouring FAQs and policy documents, to see if leaving the EU would cause conflicts for UK registrants.
All but one of these sites have comprehensive English versions available, which made the process very simple indeed.
It turns out the majority of the EU’s member states either have no geographic restrictions whatsoever or restrict registrations to only people and companies within their own nations.
I found five — six if you count .eu itself — that have policies that refer directly to a European Union presence in their rules and regulations.
- .fr (France) is restricted to residents of the EU and Iceland, Liechtenstein, Norway and Switzerland.
- .it (Italy) allows registrations from anyone in the European Economic Area, the Vatican, San Marino or Switzerland.
- .nl (Netherlands) allows regs from anywhere, but registry manager SIDN says may attach “additional conditions to legal and/or natural persons based outside the European Union”.
- .hu (Hungary) requires EU residency for individuals and companies wishing to register directly at the second level. There are no such restrictions at the third level.
- .bg (Bulgaria) requires a local Bulgarian presence for non-EU registrants.
- .eu (European Union) requires presence in the European Union, Norway, Iceland or Liechtenstein.
As you can see, even those with EU presence requirements are pretty flexible when it comes to bolting on additional eligible countries.
So-called Brexit — British exit from the EU — is unlikely to happen for two years or more, if it happens at all.
The thinking right now is that if/when the UK does finally formally leave it is likely to either become a member of the European Economic Area or have otherwise have negotiated a relationship with the EU not unlike Norway’s.
This would presumably make it fairly easy for ccTLD registries to plug the UK into their existing policies.
Any registry with a substantial number of existing UK registrants would of course have financial exposure to a Brexit, a likely incentive to modify their rules accordingly.
So for regular domain owners, Brexit is probably no big deal.
Whether the move would an impact on trademark holders or registrars are rather more complex matters that I have not looked at yet.