PLANNING


Ensuring DNS resolves in NRPC

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:


If your company uses multiple DNS domain levels -- for example, when each country in which a multinational company has offices is a subdomain in DNS -- do the following:

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