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 (private) addresses?
I still haven’t heard a convincing argument to not use .local and I see no reason to stop.
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.
That I agree with. Microsoft drafted the recommendation to use it for local networks, and Apple ignored it or co-opted it for mDNS.
.local is already used by mDNS/Zeroconf.
You mean mDNS/Zeroconf are using a tld that was already being used.
Tell me you don’t share a net with Macs without using those words.
Macs aren’t the only thing that use mDNS, either. I have a host monitoring solution that I wrote that uses it.
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
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 (private) addresses?
My main issue was it doesn’t play well with Macs.