Home
Planning
Use this topic as an overview of planning task.
Planning the TCP/IP network
The default TCP/IP configuration for an HCL Domino® server is one IP address that is globally bound, meaning that the server listens for connections at the IP addresses of all NICs on the computer. Global binding works as long as the computer does not have more than one IP address offering a service over the same assigned TCP port.
Ensuring DNS resolves in TCP protocols
When you register a new HCL Domino® server, you specify a common name for it. Within a Domino hierarchical name, the common name is the portion before the leftmost slash. For example, in the name App01/East/Renovations, the common name is App01. The common name, not the hierarchical name, is the name that the Domino server is known by in DNS.
Ensuring DNS resolves in NRPC
This practice ensures good DNS resolves in NRPC for companies with multiple DNS domain levels.

Planning
Use this topic as an overview of planning task.
- Roadmap for deploying Domino® servers
  Use this as a tool when planning how to integrate HCL Domino® into your existing environment.
- Planning server-to-server connections
  Servers must connect to each other to exchange data, for example to replicate databases and exchange mail. You can create connections between servers across a local area network (LAN) or wide area network (WAN), by using a pass-through server (a server that acts as an intermediary server between a client and its destination), or over the Internet. Create a Server Connection document whenever you need to establish any new or additional server connections. You can modify this document when necessary.
- Planning directory services
  HCL Domino® provides a range of directory service features.
- Planning a mail routing topology
  HCL Domino® offers you considerable flexibility in configuring your mail system infrastructure, allowing you to use HCL Notes® routing, SMTP routing, or both, for internal and external messages.
- Planning a cluster
  When planning a cluster, it is important to consider the performance and ability of your hardware. The cluster must have enough CPU power, memory, and disk space to handle the cluster traffic and the number of databases and replicas required.
- Planning the TCP/IP network
  The default TCP/IP configuration for an HCL Domino® server is one IP address that is globally bound, meaning that the server listens for connections at the IP addresses of all NICs on the computer. Global binding works as long as the computer does not have more than one IP address offering a service over the same assigned TCP port.
  - Using Domino® on IBM® i with TCP/IP
    The HCL Domino® server on IBM® i uses TCP/IP to communicate with HCL Notes® clients and the Internet. For the Domino server to work properly, TCP/IP must be set up and active on your system.
  - NRPC name-to-address resolution over TCP/IP
    In the TCP/IP protocol, the method most commonly used to resolve server names to network addresses is the Domain Name System (DNS), an Internet directory service developed both to allow local administrators to create and manage the records that resolve server names to IP addresses and to make those records available globally. While the POP3, IMAP, LDAP, and HTTP services use DNS directly, the NRPC service uses a combination of the Notes® Name Service and DNS to resolve server names to network addresses.
  - Ensuring DNS resolves in TCP protocols
    When you register a new HCL Domino® server, you specify a common name for it. Within a Domino hierarchical name, the common name is the portion before the leftmost slash. For example, in the name App01/East/Renovations, the common name is App01. The common name, not the hierarchical name, is the name that the Domino server is known by in DNS.
    - Ensuring DNS resolves on Windows™ systems -- All TCP protocols
      If an HCL Domino® server is a Microsoft™ Windows™ system, often two name services exist on the system -- NetBIOS over IP and DNS.
    - Ensuring DNS resolves in NRPC -- Best practices
      The following procedures provide the best name-resolution practices for anHCL Domino® server using the default NRPC configuration on a TCP/IP network (oneHCL Notes® network port for TCP/IP). These procedures address the following DNS configurations – one DNS domain and multiple DNS domain levels
    - Ensuring DNS resolves in NRPC -- Alternative practices
      These procedures provide alternative name-resolution practices for an HCL Domino® server using the default NRPC configuration on a TCP/IP network (one Notes® network port for TCP/IP).
    - Ensuring DNS resolves in NRPC
      This practice ensures good DNS resolves in NRPC for companies with multiple DNS domain levels.
  - Considerations for changing a server IP address
    Changing the IP address of an HCL Domino® server can cause access issues.
  - IPv6 and Domino®
    You can enable IPv6 support in HCL Domino® for SMTP, POP3, IMAP, LDAP, and HTTP services on IBM® AIX®, IBM i, and Linux™ systems.
  - Advanced Domino® TCP/IP configurations
    Domino® servers and partitioned Domino servers can have multiple NICs (network interface cards), each with its own IP address.
- Messaging overview
  The HCL Domino® mail system has three basic components: Domino mail servers, Domino mail files, and mail clients. The Domino mail server is the backbone of an organization's messaging infrastructure, acting both as an Internet mail server and an HCL Notes® mail server. Domino provides standards-based Internet messaging through its support of the Simple Mail Transfer Protocol (SMTP), Post Office Protocol version 3 (POP3), Internet Message Access Protocol (IMAP), and Multipurpose Internet Mail Extensions (MIME). At the same time, Domino supports Notes mail through the use of Notes routing protocols -- Notes remote procedure calls (NRPC) -- and the Notes rich text message format.
- Planning your Notes® client deployment
  Use the references listed here to plan for, install, upgrade to, and configure the HCL Notes® client.
- Planning security
  An important aspect of planning security for your Domino® environment is understanding the tasks and features involved with securing each type of resource.

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:

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.

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:

Use the server's FQDN as the Domino® server common name.
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.