Lotus Domino Administrator 8 Help - Ensuring DNS resolves in NRPC -- A practice to use with caution

NETWORK CONFIGURATION

Ensuring DNS resolves in NRPC -- A practice to use with caution
The following practice, if followed precisely, should ensure good DNS resolves in NRPC for companies with multiple DNS domain levels, but might result in extra work if the infrastructure changes. Using this practice has the following disadvantages:

You can never assign more than one IP address in DNS to the IBM® Lotus® 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.

To achieve long-term stability in a large company, see the topic Ensuring DNS resolves in NRPC -- Best practices.

When you have multiple DNS domain levels
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.acme.com, you can also assign the Domino server's common name as app01.germany.acme.com. In this case, the server's Domino hierarchical name might be app01.germany.acme.com/Sales/Acme.

Ensuring DNS resolves in NRPC -- Alternative practices

Ensuring DNS resolves in TCP protocols

Glossary

Feedback on Help or Product Usability?

Help on Help

All Help Contents

Glossary