Self-hosting has become increasingly popular as individuals seek greater control over their data and a deeper understanding of technology by running their own services at home. To support this trend, ICANN has reserved the .internal Top Level Domain (TLD) specifically for non-Internet routable domains. This initiative aims to simplify the process for those interested in self-hosting.
Background and Decision
Earlier this year, ICANN solicited public comments on the proposed .internal TLD. With minimal concerns raised—mainly about the TLD’s length—the proposal was forwarded to the ICANN board. Recently, ICANN ratified the .internal TLD, ensuring that domains like neowin.internal cannot be registered on the public Internet.
Comparison with Existing Standards
This new standard is similar to existing practices for specific IP address ranges that are reserved for internal network use. According to RFC 1918, IP addresses within the 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 ranges are designated for internal networks only. The .internal TLD provides a similar level of isolation for domain names, allowing users to host their own DNS and Certificate Authority (CA) within their internal networks without risking conflicts or disruptions.
Practical Considerations
While the .internal TLD offers significant benefits for internal network management, there are some limitations to consider. For instance, services like Let’s Encrypt, which provide free SSL/TLS certificates, cannot be used with .internal domains because these domains do not have a specific owner. Users will need to manage their own CA or purchase a public domain if they require globally recognized certificates.
Additional Resources
For those interested in exploring self-hosting further, there are comprehensive guides available. These resources cover the advantages and disadvantages of self-hosting and provide detailed instructions on setting up environments such as the Proxmox hypervisor, along with installing Windows and Linux virtual machines.