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

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

10 comments

Don’t we already have .local for that?
- https://community.veeam.com/blogs-and-podcasts-57/why-using-local-as-your-domain-name-extension-is-a-bad-idea-4828
  
  Is 192.168.x.x not reserved for local networks? I’m pretty sure it isn’t used for public addresses. That link specifically says don’t use .local for public dns, use it for local mdns.
What about all the other weird TLDs that aren't being used? Like .walmart

I would have thought that Walmart.walmart would be a valid link but it isn't, so what's the point?!
- Weird TLDs shouldn’t exist to begin with. Just more evidence that ICANN doesn’t know what the hell they’re doing.
  
  Weird TLDs should totally exist! Just because Walmart isn’t capitalizing on it doesn’t mean that I shouldn’t be able to make hello.friends for my use.
That's so long to type -_-. I like using .lan for that purpose
- Having ones own local DNS-server is great for such, just add local IP and whatever address.
  
  I use .lab as well, but I suppose "s.l" would work as a super short and easily typeable local domain.
  
  That's my hosting vlan - .lab.lan
- Yeah, .lan is way better.

You've viewed 10 comments.