ICANN Wants to Create .Internal Top-level Domain for Private Use

[TheLostSwede]

The nonprofit organisation that is in charge of coordinating and managing the namespaces and numerical spaces on the internet—ICANN or Internet Corporation for Assigned Names and Number—has proposed a rather big change on how consumers and businesses could be accessing networked devices on their private networks in the future. ICANN has put forward a new top-level domain for private use, much like the 192.168.x.x IP address range is allocated to private networks (alongside two other ranges), we might end up with a similar top-level domain. The proposed domain will be .internal, although we already have .localhost and .local today, but neither is really usable in a private network.

As such .internal has been suggested—in favour of.private due to concerns about it sounding like something privacy related—as a means for less computer savvy users to connect to devices on a private network. We've already seen solutions from several router manufacturers that use various domain names or subdomains to enable easier connectivity to routers. However, the goal here is to avoid clashes with top-level domains on the internet and.internal is said to resolve this problem. That said, it's not clear how this will be implemented as yet, but the ICANN is set to release more details in the near future. Even though it might not be the perfect solution, it should hopefully allow people to remember what they called their devices when they need to access them, rather than trying to remember the correct IP address.



View at TechPowerUp Main Site | Source

 

[lexluthermiester]

As such .internal has been suggested—in favour of.private due to concerns about it sounding like something privacy related

Internal networks are always private. Can't see the problem..

 

[bonehead123]

Internal networks are always private. Can't see the problem.

Ah yes, the ole "solution looking for a problem" thingy

oh my....what have they done now.........

 

[Solaris17]

Internal networks are always private. Can't see the problem..

It’s about DNS it’s a real issue. If .private is popular and being petitioned as a legit TLD then having it as your internal TLD will make your requests search your internal DNS system or worse (and in most cases) you will search outside your network and never get the resources you are trying to reach internally.

split horizon DNS is a bad and frowned upon practice so we try to minimize it as much as possible.

.local and .localhost have there own issues because they mean different things to different OSs and can be handled differently depending on platform.

to get around this most places use there TLD and rely on AD or heavily modified DNS servers to redirect users internal user requests to systems. This becomes a problem when you need to make modifications internally to DNS or want to test addresses from “the outside”.

this is a good thing for IT because it will alleviate internal DNS complexity and it will get around the .local and .localhost oddities introduced by various OSs.

without DNS then internal resources are relegated to ip address’ .

 

[Eskimonster]

If i can host my plex server kek

 

[JAB Creations]

All I care about here is if I don't have to keep screwing with Chrome every time I need to make a new version install (I test all versions of all modern browsers) without having to set chrome://flags/#allow-insecure-localhost. I know the localhost TLS certificate is self-signed! I'm quite sick of it and if this fixes it than great! Not using .private TLD is a good move too as there are plenty of legitimate public-access websites oriented around security.

 

[kondamin]

Looks to much like a regular tld

 

[lexluthermiester]

It’s about DNS it’s a real issue.

Fair enough. That is not my area of expertise. I'll defer to the experts.

 

[Solaris17]

Fair enough. That is not my area of expertise. I'll defer to the experts.

I mean just fyi you’re also not wrong. To anyone outside of homelabs or corp this means nothing. I would expect it to eventually make it (read years) as the default TLD on consumer routers instead of like .local but there is 0 home user impact for sure.

 

[remixedcat]

It’s about DNS it’s a real issue. If .private is popular and being petitioned as a legit TLD then having it as your internal TLD will make your requests search your internal DNS system or worse (and in most cases) you will search outside your network and never get the resources you are trying to reach internally.

split horizon DNS is a bad and frowned upon practice so we try to minimize it as much as possible.

.local and .localhost have there own issues because they mean different things to different OSs and can be handled differently depending on platform.

to get around this most places use there TLD and rely on AD or heavily modified DNS servers to redirect users internal user requests to systems. This becomes a problem when you need to make modifications internally to DNS or want to test addresses from “the outside”.

this is a good thing for IT because it will alleviate internal DNS complexity and it will get around the .local and .localhost oddities introduced by various OSs.

without DNS then internal resources are relegated to ip address’ .

A brand of wireless routers I've tested before would have some wierd hostname stuff like this and it would cause stuff like vmware to have wierd dns hostnames that were hard to fix I'll dig up the screenshots of how it made vmware esxi/vsphere when I find em... would also be creating another hop in traceroutes for some reason too.

I wonder if this .internal would create that as well..

 

[DaemonForce]

It's another vague issue that doesn't appear to be a problem until everything starts imploding because some clown wanted to make .ZIP or .MP3 domains a reality.

We have enough problems just getting extremely aggressive bots to stfu now we are encouraging a new era phishing nightmare? Yeah no, bottle it.

 

[remixedcat]

It's another vague issue that doesn't appear to be a problem until everything starts imploding because some clown wanted to make .ZIP or .MP3 domains a reality.

We have enough problems just getting extremely aggressive bots to stfu now we are encouraging a new era phishing nightmare? Yeah no, bottle it.

yep the whole .zip domain suffix was a bad