The Internet Corporation for Assigned Names and Numbers (ICANN) recently agreed to reserve the new Top-Level Domain (TLD)— ‘.internal’—for private use.

The domain registration body has been on a hunt to find an IPv4 private address block like 10.0.0.0/8 equivalent for Domain Name System (DNS) for some time, and their search ended with ‘.internal’ TLD. By using a TLD for private use, ICANN aims to clearly separate internal domains from public ones, making it easier to manage private DNS without affecting the public internet.

Here are more details on the ICANN move.

Why Did ICANN Agree to ‘.internal’ Domain Extension for Private Use?

In January 2024, ICANN released a statement announcing that it would be moving ahead with ‘.internal’ TLD taking on the same role as the 192.168.x.x IPv4 block in DNS.

The need for a top-level domain for private use arrived after ICANN and Internet Assigned Numbers Authority (IANA) realized that private network operators may want to use their own domain name for internal use without making them accessible on public DNS.

While many organizations have been using IANA designated special blocks of IP addresses (like 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16) for internal communication, ICANN and IANA realized it’s time to choose an IP address equivalent for DNS.

The ICANN Security and Stability Advisory Committee (SSAC) recommended that ICANN reserve a top-level DNS label specifically for private use, ensuring it does not interfere with domains in the global DNS root zone. ICANN and IANA evaluated many TLDs, and in January, IANA came up with ‘.internal’ as the TLD for private use at the DNS level. A few days ago, ICANN accepted IANA’s proposal of reserving ‘.internal’ TLD for private use.

Here are some issues that ICANN aims to tackle with the proposal of the ‘.internal’ TLD:

Preventing Conflicts

ICANN aims to keep your internal network safe and separate from the public internet by reserving `.internal` for private use, ensuring you don’t run into conflicts or confusion with public websites. Moreover, your internal network stays secure and organized, without overlapping with global domains.

Clarity for Internal Applications

The `.internal` domain works like private IP addresses (like 192.168.0.0) used in home or office networks. Just as those IP addresses are kept private and don’t show up on the public internet, the `.internal` domain is set aside for private use. Thus, making it easier for you to divide applications and resources, leading to less confusion.

Avoiding Ad Hoc TLD Creation

Some companies were reported to be making up their own domain names for internal use, which sometimes caused problems and confusion. By officially ‘.internal’, ICANN aims to offer a standardized domain extension for internal use. This way, everyone can use the same domain name for their private networks.

Support from Major Players

Companies like Google have been using ‘.internal’ for their internal networks for years. This widespread use showed the need for an official and conflict-free domain for private networks. By formalizing ‘.internal’, ICANN plans to make managing internal networks easier and improve the stability and security of the global DNS.

How Will This Decision Impact Website Owners and Users?

Website Owners

For website owners, the ‘.internal’ domain offers a way to manage their internal communications securely and separately from public websites. For example, a corporation might use this domain for internal resources like employee directories or confidential project documents. This ensures that sensitive information remains protected and is accessible only to authorized personnel.

This can impact:

  • Compliance Costs: New regulations may require website owners to invest in compliance measures, such as updating privacy policies or implementing new security features.
  • Traffic and Engagement: Changes in search engine algorithms or social media policies can affect how easily users find and engage with websites. For instance, an algorithm update might prioritize certain types of content over others.

So, once ICANN’s proposal is implemented, website owners will soon be able to use a ‘.internal’ domain name for their internal networks and private communications.

Do consider DNS_PROBE_FINISHED_NXDOMAIN

To avoid encountering a DNS_PROBE_FINISHED_NXDOMAIN error with the new ‘.internal’ domain, website owners should:

  1. Configure Internal DNS: Ensure that your internal DNS servers are correctly set up to handle ‘.internal’ domain
  2. Access Domains Internally: Use the ‘.internal’ domain exclusively within your private network. Attempting to access these domains from outside your network will lead to resolution errors since they are not meant for public use.
  3. Update DNS Settings: After implementing the ‘.internal’ TLD, check and update your DNS settings to ensure that internal domains are properly routed and recognized within your network.
  4. Confirm Domain Setup: Verify that the ‘.internal’ domain has been correctly integrated into your internal DNS system. Ensure all relevant DNS records are in place to avoid resolution issues.

For more information, check out our guide about How to Fix the DNS_PROBE_FINISHED_NXDOMAIN Error.

Internet Users

For internet users, the implementation of the ‘.internal’ TLD means they won’t be able to access business-related information, as it will be reserved for private use only. It’s similar to trying to access a company’s internal portal or intranet from outside the organization; only employees with the right credentials can view this information. This setup helps keep internal communications and data secure and confined to authorized users.

This can impact:

  • Access to Information: Changes in regulations or policies can affect how easily users can access information online. For example, stricter data privacy laws might limit the availability of certain types of data.
  • User Experience: Decisions related to website design standards, accessibility, and performance can enhance or degrade the user experience. Improved standards can lead to faster, more user-friendly websites.

 Conclusion

ICANN’s acceptance of ‘.internal’ TLD for private use influences users by limiting their access to information, security, and content availability. For website owners, on the other hand, these decisions affect compliance costs, changes in traffic and engagement and new technical requirements, such as domain registration. Understanding these potential impacts is crucial for navigating the evolving digital landscape and ensuring a balanced approach that benefits all stakeholders.

Still have questions? Drop in a comment below!