Sysadmin @lemmy.world thehatfox @lemmy.world 11 mo. ago

ICANN proposes creating .INTERNAL domain

www.theregister.com ICANN proposes creating .INTERNAL domain

The plan is to keep the world at bay by never recording it in the DNS root – like many already do with a subdomain for an intranet

Selfhosted @lemmy.world Eager Eagle @lemmy.world 11 mo. ago

www.theregister.com /2024/01/29/icann_internal_tld/

Technology @lemmy.zip BrikoX @lemmy.zip 11 mo. ago

ICANN proposes creating .INTERNAL domain to do the same job as 192.168.x.x

www.theregister.com /2024/01/29/icann_internal_tld/

32 comments

.local already exists. More idiocy from ICANN.
- .local exists for a very specific reason and it’s not meant to be used by regular DNS… people use it for alternate things, but it’s reserved for mDNS
  
  if .internal were to be added, we could start using that instead of overloading!
- .local is a bad choice especially if you have any MAC hosts on the network.
  
  There is an RFC about that, but I'm too sleepy to goook it up
Please no

It would be nice to figure out a way to get local SSL certs for .lan and .local domains though.
- I just use a subdomain of my main domain and use dns validation of let's encrypt.
  
  That requires outside authentication though. I think it would be cool to incorporate some SSL into dhcp
- Time for your own CA
- What's wrong with it?
  
  Internal is 8 letters while lan is three
- You can do this, I already use .internal and you can male your own root ca and make your own certificates with that
If only they had done this with .local ages ago. Still, it's a nice change, but I doubt my company will adopt.
- We broke .local, pls give another chance, we promise we'll be responsible with .internal tho
  
  For real. Once Google and others started killing DNS lookups in mobile devices, think about how many legacy networks had to get rebuilt.
  
  Maybe we could all just make up our minds.
- Just out of curiosity, does your company use a different TLD or something more arbitrary/just an IP?
Abolish ICANN.
- Explain what's wrong with this. I'm out of the loop, seems like a good idea to me at first glance.
  
  It's the SPOF for most of the internet, it's function should be democratic and distributed.
  
  Registering TLDs costs absurd amounts of money last I checked.
Porn sites would like this.
I have clients that use internal, but they do it as a subdomain; so internal.contoso.com

Any internal only domains that I set up are probably going to go the same way. I've used domain.local previously, and the DNS headache I get from that is immeasurable.

With so many things going "to the cloud" or whatever, the internal.domain.tld convention tends to make more sense to me.

What's everyone else doing?

You've viewed 32 comments.