←back to thread

.INTERNAL is now reserved for private-use applications

(www.icann.org)
563 points joncfoo | 1 comments | 09 Aug 24 16:36 UTC | HN request time: 0.201s | source
Show context
csdreamer7 ◴[09 Aug 24 20:13 UTC] No.41205035[source]▶
Can we get .local or .l added for private-use applications too?
replies(5): >>41205064 #>>41205158 #>>41207055 #>>41208856 #>>41210365 #
duskwuff ◴[09 Aug 24 20:29 UTC] No.41205158[source]▶
.local is already reserved for mDNS.
replies(2): >>41205429 #>>41210351 #
jeroenhd ◴[09 Aug 24 21:10 UTC] No.41205429[source]▶
.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.

replies(4): >>41205459 #>>41205538 #>>41205804 #>>41207138 #
1. abtinf ◴[10 Aug 24 03:42 UTC] No.41207138[source]▶
> but they could.

Presumably, ICANN, like any other committee, is not interested in self-castration. Which is what would happen if they challenged Apple.

ICANN could do anything with enough rule changes. And then everyone will ignore them.