Certain domain names are locally routed only. So if you use internal or local as a tld, you can just assign whatever names you want and your computer won’t go looking out on the internet for them. This means you and I can both have fileserver.local as an address on our respective network without conflicting. It’s the URI equivalent of 192.168.0.0/16.
Comment on ICANN approves use of .internal domain for your network
Wilzax@lemmy.world 5 weeks ago
Why do I care what ICANN says I can do on my own network? It’s my network, I do what I want.
Voroxpete@sh.itjust.works 5 weeks ago
torkildr@lemmy.world 5 weeks ago
Interesting that you should use “.local” as an example, as that one’s extra special, aka Multicast DNS
ygpa@lemmy.world 5 weeks ago
YouCANN do anything you want?
charonn0@startrek.website 5 weeks ago
The value of the DNS is that we all use the same one. You can declare independence, but you’d lose out on that value.
KillingTimeItself@lemmy.dbzer0.com 5 weeks ago
the only losers in this situation are people that are squatting on my rightfully pirated domain names!
friend_of_satan@lemmy.world 5 weeks ago
Try using .com for your internal network and watch the problems arise. Their choice to reserve .internal helps people avoid fqdn collisions.
See also traintocode.com/stop-using-test-dot-com/
Wilzax@lemmy.world 5 weeks ago
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
friend_of_satan@lemmy.world 5 weeks ago
Sure, you can do whatever you want. You could even use non-rfc1918 addresses and nobody can stop you. It’s just not always a great idea for your own network’s functionality and security. You can use an unregistered TLD if you want, but it’s worth knowing that when people and companies did that in the past, and the TLD was later registered, things didn’t turn out well for them. You wouldn’t expect .foo to be a TLD, right? And it wasn’t, until it was.
Wilzax@lemmy.world 5 weeks ago
Ah good point. I guess a future-proofed guarantee that the domain will never be used externally would be easier to use than trying to somehow configure my DNS to never update specific addresses.
DarkMetatron@feddit.org 5 weeks ago
German router and network products company AVM learned the hard way that this is a bad idea. They use fritz.box for their router interface page and it was great until tld .box became publicly available and somebody registered fritz.box.
Having a reserved local/internal only tld is really great to prevent such issues.
aesthelete@lemmy.world 5 weeks ago
I agree that this is a good idea, but I wanted to add that if someone owns a domain already, they can also use that internally without issue.
If you own a domain and use Let’s Encrypt for a star cert, you can have nice, well secured internal applications on your network with trusted certificates.
patrick@lemmy.jackson.dev 5 weeks ago
If you just run a personal private network, then yea pick anything because you can change it fairly easily. Companies should try to stick to things that they know won’t change under them just to avoid issues