Live data from Hacker News

.INTERNAL is now reserved for private-use applications

icann.org

11–20 of 290 posts

Re: .INTERNAL is now reserved for private-use applications

#11
post #5

I need a dumbed down version of this.

When setting up local networks people commonly use a top level domain like 'my.lan', 'my.network', 'my.local'. Instead of using one of these non-reserved domains that may one day end up as a TLD, it is recommended to use 'my.internal'.

If the 'private' TLD you're using suddenly becomes real, then you can ship off data, every possibly unencrypted data and connection requests to computers you do not control.

Re: .INTERNAL is now reserved for private-use applications

#12
post #5

I need a dumbed down version of this.

The dumbed down version is that no one will be allowed to register a .internal domain on the internet, ever. So you are free to use it for your internal network in any way you like and it will not come into conflict with registered domains and internet standard.

Re: .INTERNAL is now reserved for private-use applications

#13
post #8

1. Buy .intern TLD 2. Sell to scammers. 3. Profit. (I want to appreciate how hard it probably is for ICANN to figure out proper TLDs.)

Um... no? .intern is not a valid TLD; you can't get any domains with it, nobody has proposed that TLD, and if someone did that issue would be discovered then.

Re: .INTERNAL is now reserved for private-use applications

#14
post #6

Earlier quoted context omitted.

Is it not already? https://en.wikipedia.org/wiki/.local

Not by ICANN? https://www.iana.org/domains/root/db

The ICANN root zone only contains gTLDs and ccTLDs which are delegated. Other TLDs which are explicitly reserved for non-public use, like .localhost, .test, or .invalid, don't appear on that list either.

Re: .INTERNAL is now reserved for private-use applications

#15
post #8

1. Buy .intern TLD 2. Sell to scammers. 3. Profit. (I want to appreciate how hard it probably is for ICANN to figure out proper TLDs.)

Um... no? .intern is not a valid TLD; you can't get any domains with it, nobody has proposed that TLD, and if someone did that issue would be discovered then.

If you've got a couple hundred grant laying about, you could probably set up a shell company and acquire .intern through a several-year ccTLD acquisition process.

I'd like to think people learned from .dev and such. I doubt any scammer will be able to use it.

Re: .INTERNAL is now reserved for private-use applications

#16
post #5

I need a dumbed down version of this.

Remember how tons of developers got surprised when Google got the .dev TLD, because they were using domains they didn't own to develop software? Well, now .internal has been reserved so developers and companies can safely use .internal domains without that happening to them.

Re: .INTERNAL is now reserved for private-use applications

#17

Earlier quoted context omitted.

Um... no? .intern is not a valid TLD; you can't get any domains with it, nobody has proposed that TLD, and if someone did that issue would be discovered then.

If you've got a couple hundred grant laying about, you could probably set up a shell company and acquire .intern through a several-year ccTLD acquisition process. I'd like to think people learned from .dev and such. I doubt any scammer will be able to use it.

Sorry, what happened with .dev?

EDIT: just saw your comment about Google here

https://news.ycombinator.com/item?id=41205394

Re: .INTERNAL is now reserved for private-use applications

#19
post #7

Can we get .local or .l added for private-use applications too?

.local is already reserved for mDNS.

.local is in this weird state where it's _technically_ not reserved, but most PCs in the world already resolve it with special non-DNS software because of the Bonjour/mDNS protocol.

So you end up with the IETF standardising .local, because Apple was already using it, but ICANN never did much with that standardisation.

I doubt ICANN will actually touch .local, but they could. One could imagine a scheme where .local is globally registered to prevent Windows clients (who don't always support mDNS) from resolving .local domains wrong.

Re: .INTERNAL is now reserved for private-use applications

#20

Earlier quoted context omitted.

If you've got a couple hundred grant laying about, you could probably set up a shell company and acquire .intern through a several-year ccTLD acquisition process. I'd like to think people learned from .dev and such. I doubt any scammer will be able to use it.

Sorry, what happened with .dev? EDIT: just saw your comment about Google here https://news.ycombinator.com/item?id=41205394

People were using .dev for internal things and acted surprised when Google decided to use it on the internet.
Post reply on HN