SoylentNews is people
SoylentNews
https://www.theregister.com/2024/01/29/icann_internal_tld/
The Internet Corporation for Assigned Names and Numbers (ICANN) has proposed creating a new top-level domain (TLD) and never allowing it to be delegated in the global domain name system (DNS) root.
The proposed TLD is .INTERNAL and, as the name implies, it's intended for internal use only. The idea is that .INTERNAL could take on the same role as the 192.168.x.x IPv4 bloc – available for internal use but never plumbed into DNS or other infrastructure that would enable it to be accessed from the open internet.
ICANN's Security and Stability Advisory Committee (SSAC) advised the development of such a TLD in 2020. It noted at the time that "many enterprises and device vendors make ad hoc use of TLDs that are not present in the root zone when they intend the name for private use only. This usage is uncoordinated and can cause harm to Internet users" – in part by forcing DNS servers to handle, and reject, queries for domains only used internally.
[...] ICANN's board still has to sign off the creation of .INTERNAL. But if you want to get ahead of the pack, there's nothing stopping you. Indeed, some outfits already use ad hoc TLDs. Open source Wi-Fi firmware project WRT has used .LAN, and networking vendor D-Link has employed .dlink.
There's nothing stopping you doing likewise.
But as ICANN's proposal for the idea noted: "Operators who choose to use private namespaces of the kind proposed in this document should understand the potential for that decision to have corresponding costs, and that those costs might well be avoided by choosing instead to use a sub-domain of their own publicly registered domain name."
(Score: 3, Interesting) by boltronics on Friday February 02 2024, @03:49AM
My understanding is that .home.arpa is perfectly safe to use for internal domains, so that's what I use at home for hosts on my main LAN.
https://en.wikipedia.org/wiki/.arpa#Residential_networking [wikipedia.org]
The length of the domain doesn't matter at all here, as I have home.arpa to my host search path in /etc/resolv.conf (which is populated by the DHCP server).
However, as the link states, it's meant for residential networks. It's likely fine as a default for many device vendors though, where home users are the target customers. An enterprise setup would be a different story… so there it makes more sense to just replace records like nas0.accounting.mycompany.com and httpd0.development.mycompany.com with nas0.accounting.mycompany.internal and httpd0.development.mycompany.internal or whatever, but it's hard to imagine this ever being a practical default.
When it comes to internal domains for public facing hosts that I manage on my home network (on a separate DMZ VLAN), that's where I currently use a private subdomain of my publicly registered domain name, but I guess it would be easy enough to switch if this proposal becomes a standard.
It's GNU/Linux dammit!