thehatfox@lemmy.world to Selfhosted@lemmy.worldEnglish · 1 month agoICANN approves use of .internal domain for your networkwww.theregister.comexternal-linkmessage-square45fedilinkarrow-up15arrow-down10cross-posted to: tech@programming.dev
arrow-up15arrow-down1external-linkICANN approves use of .internal domain for your networkwww.theregister.comthehatfox@lemmy.world to Selfhosted@lemmy.worldEnglish · 1 month agomessage-square45fedilinkcross-posted to: tech@programming.dev
minus-squareWilzax@lemmy.worldlinkfedilinkEnglisharrow-up1·1 month agoWhy do I care what ICANN says I can do on my own network? It’s my network, I do what I want.
minus-squarefriend_of_satan@lemmy.worldlinkfedilinkEnglisharrow-up1·1 month agoTry using .com for your internal network and watch the problems arise. Their choice to reserve .internal helps people avoid fqdn collisions. See also https://traintocode.com/stop-using-test-dot-com/
minus-squareWilzax@lemmy.worldlinkfedilinkEnglisharrow-up0arrow-down1·1 month agoWell as long as the TLD isn’t used by anyone it should work internally regardless of what ICANN says, especially if I add it to etc/hosts
Why do I care what ICANN says I can do on my own network? It’s my network, I do what I want.
Try using .com for your internal network and watch the problems arise. Their choice to reserve .internal helps people avoid fqdn collisions.
See also https://traintocode.com/stop-using-test-dot-com/
Well as long as the TLD isn’t used by anyone it should work internally regardless of what ICANN says, especially if I add it to etc/hosts