←back to thread

.INTERNAL is now reserved for private-use applications

(www.icann.org)
563 points joncfoo | 5 comments | 09 Aug 24 16:36 UTC | HN request time: 0.022s | 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. arjvik ◴[09 Aug 24 21:16 UTC] No.41205459[source]▶
Modern windows supports mDNS these days!
replies(1): >>41206329 #
2. jeroenhd ◴[09 Aug 24 23:45 UTC] No.41206329[source]▶
It does! I generally assume mDNS to just be available on every device these days. But I've also seen managed environments where mDNS has been turned off or blocked at the firewall.
replies(1): >>41206566 #
3. dboreham ◴[10 Aug 24 00:49 UTC] No.41206566[source]▶
mDNS is a broadcast protocol so always "blocked at the firewall ".
replies(2): >>41206985 #>>41210598 #
4. oasisbob ◴[10 Aug 24 02:57 UTC] No.41206985{3}[source]▶
Multicast too. If you've never needed to manipulate ACLs for multicast traffic, you're not really living.
5. ◴[10 Aug 24 16:34 UTC] No.41210598{3}[source]▶