←back to thread

.localhost Domains

(inclouds.space)
301 points todsacerdoti | 3 comments | | HN request time: 0.926s | source
Show context
mjevans ◴[] No.43644380[source]
Once again, .local should _never_ have been assigned to any organization. Just like .lan should also be reserved like the private IP blocks.
replies(2): >>43644423 #>>43644451 #
WorldMaker ◴[] No.43644451[source]
.local wasn't assigned to an organization, it was assigned to mDNS: multicast DNS. mDNS is the ask everyone on the local network if they like to be called that name which used to be better known under Apple's brand/trademark Bonjour, but now is a true standard.
replies(1): >>43644604 #
1. mjevans ◴[] No.43644604[source]
Yes, but why couldn't they have assigned .mdns for that instead? Or even better given it it's own .arpa domain? E.G. .mdns(.arpa) rather than the .local TLD? ( https://en.wikipedia.org/wiki/.arpa )
replies(1): >>43645104 #
2. WorldMaker ◴[] No.43645104[source]
Because .local looks nice and is a better name/explainer for what mDNS does than the standard name or the old brand name? Because the old brand was already using .local even if Apple Devices were somewhat a minority at the time?

At this point a lot of TLD changes are going to step on someone's project or home/business/private network. I think .local is a good name for mDNS. I appreciate why you maybe aren't happy with it, but don't share your concern.

replies(1): >>43646546 #
3. mjevans ◴[] No.43646546[source]
Those are both reasons that .local should be static DNS on the _network_ like localhost is a standard name for the loopback address(es).

There's no reason .mdns or .mdns.arpa couldn't have just been added to the default domains search list (the list of suffixes tried for non FQDN searches); which given it ISN'T a nice human obvious word to append wouldn't have conflicted with anyone who'd already had a .local at the time, and anyone else in the future who thinks an obvious phrase like .local would not be in use by some other resolver system.