thehatfox@lemmy.world to Selfhosted@lemmy.worldEnglish · 1 month agoICANN approves use of .internal domain for your networkwww.theregister.comexternal-linkmessage-square51fedilinkarrow-up18arrow-down10
arrow-up18arrow-down1external-linkICANN approves use of .internal domain for your networkwww.theregister.comthehatfox@lemmy.world to Selfhosted@lemmy.worldEnglish · 1 month agomessage-square51fedilink
minus-squaredhtseany@lemmy.mllinkfedilinkEnglisharrow-up0·1 month agoI still haven’t heard a convincing argument to not use .local and I see no reason to stop.
minus-squarekingthrillgore@lemmy.mllinkfedilinkEnglisharrow-up1·1 month ago.local is already used by mDNS/Zeroconf.
minus-squareSirEDCaLot@lemmy.todaylinkfedilinkEnglisharrow-up1·1 month agoMainly 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.
minus-squarexcjs@programming.devlinkfedilinkEnglisharrow-up1·1 month agoThat I agree with. Microsoft drafted the recommendation to use it for local networks, and Apple ignored it or co-opted it for mDNS.
minus-squarebillwashere@lemmy.worldlinkfedilinkEnglisharrow-up1·1 month agoMy main issue was it doesn’t play well with Macs.
I still haven’t heard a convincing argument to not use .local and I see no reason to stop.
.local is already used by mDNS/Zeroconf.
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.
My main issue was it doesn’t play well with Macs.