This practice ensures good DNS resolves in NRPC for companies with multiple DNS domain levels.

About this task

Using this practice, as seen in the related links, has the following disadvantages:

• You can never assign more than one IP address in DNS to the HCL Domino® server.
• If the FQDN changes, the Domino server name will not match the FQDN, thus invalidating the DNS resolve. You will then need to create a new server and migrate users to it.
• If you use network address translation (NAT), the server's FQDN must be identical in both instances of DNS (internal and external shadow DNS).
• You cannot use other network protocols, as many of them use flat network name services, and those that use hierarchical name systems will not function unless the name hierarchy is exactly the same.
• Diagnosing connectivity issues can be much harder.

1. Use the server's FQDN as the Domino server common name.

2. Create an A record (or, for IPv6, AAAA record) in DNS.

For example, if you register a server with DNS as app01.germany.renovations.com, you can also assign the Domino server's common name as app01.germany.renovations.com. In this case, the server's Domino hierarchical name might be app01.germany.renovations.com/Sales/Renovations.

Parent topic: Ensuring DNS resolves in TCP protocols

Related concepts
Ensuring DNS resolves in TCP protocols

Related tasks
Ensuring DNS resolves on Windows systems -- All TCP protocols
Ensuring DNS resolves in NRPC -- Best practices
Ensuring DNS resolves in NRPC -- Alternative practices