Latest news of the domain name industry

Recent Posts

It’s official, .internal is blocked forever

Kevin Murphy, August 1, 2024, Domain Policy

ICANN has formally confirmed that the gTLD .internal will never be delegated.

Its board of directors resolved earlier this week that it “reserves .INTERNAL from delegation in the DNS root zone permanently to provide for its use in private-use applications.”

It went on to recommend “that efforts be undertaken to raise awareness of its reservation for this purpose through the organization’s technical outreach.”

The idea is to give organizations a gTLD that they can use behind their firewalls that they can be sure will never become a public-DNS gTLD in future, which would carry the risk of name collisions and data leakage.

The string “internal” was picked in January over .private and put out for public comment to murmurs of approval.

The move means nobody will be able to apply for .internal in future new gTLD application rounds.

Amazon and Google among .internal TLD ban backers

Kevin Murphy, March 20, 2024, Domain Tech

Google and Amazon have publicly backed ICANN’s plan to reserve the top-level domain .internal for private behind-the-firewall uses.

ICANN picked the string “internal” as the one that it will promise to never delegate to the DNS root, allowing network administrators and software developers to confidently use it with a lower risk of data leakage should the TLD come under a registry’s control in future.

The public comment period over its choice is coming to a close tomorrow, with a generally supportive vibe coming from the 30-odd comments submitted so far.

Notably, tech giants Amazon and Google have both filed comments backing .internal, with both companies saying that they already use the TLD extensively for internal purposes (Google in its Cloud services) and that to allow it to be delegated in future would cause big problems.

Some commenters niggled that .internal is too long, and that something like .local or .lan, both already reserved, might be better. Others wondered why strings such as .corp or .home, which are already effectively banned due to the high risk of name collisions, were not chosen instead.

ICANN picks the domain it will never, ever release

Kevin Murphy, January 24, 2024, Domain Policy

ICANN has picked the TLD string that it will recommend for safe use behind corporate firewalls on the basis that it will never, ever be delegated.

The string is .internal, and the choice is now open for public comment.

It’s being called a “private use” TLD. Organizations would be able to use it behind their firewalls safe in the knowledge that it will never appear in the public DNS, mitigating the risk of public/private name collisions and data leakage.

.internal beat fellow short-lister .private to ICANN’s selection because it was felt that .private might lure people into a false sense of security.

While it’s unlikely that anyone was planning to apply for .internal as a commercial or brand gTLD in future, it’s important to note that when it makes it to the ICANN reserved list all confusingly similar strings will also be banned, under the current draft of the Applicant Guidebook.

So reserving .internal also potentially bans .internat, which Google tells me is the French word for a boarding school, or .internai, which is a possible brand for an AI for interns (yes, I’m grasping here, but you get my point).

The public comment period is open now and ends March 21.