←back to thread

563 points joncfoo | 1 comments | | HN request time: 0.202s | source
Show context
csdreamer7 ◴[] No.41205035[source]
Can we get .local or .l added for private-use applications too?
replies(5): >>41205064 #>>41205158 #>>41207055 #>>41208856 #>>41210365 #
duskwuff ◴[] No.41205158[source]
.local is already reserved for mDNS.
replies(2): >>41205429 #>>41210351 #
jeroenhd ◴[] 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 #
arjvik ◴[] No.41205459[source]
Modern windows supports mDNS these days!
replies(1): >>41206329 #
jeroenhd ◴[] 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 #
dboreham ◴[] No.41206566[source]
mDNS is a broadcast protocol so always "blocked at the firewall ".
replies(2): >>41206985 #>>41210598 #
1. ◴[] No.41210598[source]