.local is already used by mDNS/Zeroconf.
Comment on ICANN approves use of .internal domain for your network
dhtseany@lemmy.ml 3 months agoI still haven’t heard a convincing argument to not use .local and I see no reason to stop.
KingThrillgore@lemmy.ml 3 months ago
x00z@lemmy.world 3 months ago
You mean mDNS/Zeroconf are using a tld that was already being used.
corsicanguppy@lemmy.ca 3 months ago
Tell me you don’t share a net with Macs without using those words.
xcjs@programming.dev 3 months ago
Macs aren’t the only thing that use mDNS, either. I have a host monitoring solution that I wrote that uses it.
ChapulinColorado@lemmy.world 3 months ago
Even on windows sometimes depending on the target host, I’ve had to type host.local. (Final dot to do exact match) instead of host.local
This didn’t seem to affect other domains. I’m assuming it was due to special handling of .local
ayyy@sh.itjust.works 3 months ago
mDNS hasn’t been a just-Apple thing for decades. Do you still call it Ren-dess-voos like the Gaston character in Beauty and the Beast?
ShortFuse@lemmy.world 3 months ago
I’ve also used .local but .local could imply a local neighborhood. The word itself is based on “location”. Maybe a campus could be .local but the smaller networks would be .internal
Or, maybe they want to not confuse it with link-local or unique local addresses. Though, maybe all .internal networks should be using local addresses?
billwashere@lemmy.world 2 months ago
My main issue was it doesn’t play well with Macs.
SirEDCaLot@lemmy.today 3 months ago
Mainly conflicts with mDNS. However it’s shitty IMHO that the mDNS spec snarfed a domain already in widespread use, should have used .mDNS or similar.
xcjs@programming.dev 3 months ago
That I agree with. Microsoft drafted the recommendation to use it for local networks, and Apple ignored it or co-opted it for mDNS.