Home
Welcome to the HCL Domino 11.0.1 documentation
Welcome to the HCL Domino® 11.0.1 documentation. Here administrators can find information about planning, installing, configuring, and administering Domino 11.0.1.
Configuring
Use this information to configure your network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters.
Configuring a network
This section presents the planning concepts and setup procedures necessary for a successful HCL Domino® deployment over a network. It provides information on network protocols from a Domino perspective but does not attempt to provide general network information.
Setting up Domino® servers on the network
Before and after installing a Domino® server, perform required tasks.
Server setup tasks specific to TCP/IP
After you run the Domino® Server Setup program, complete these procedures:
Setting up a secondary name server
To ensure that the Notes® Name Service is always available to Notes users, assign a secondary name server in users' Location documents.

Welcome to the HCL Domino 11.0.1 documentation
Welcome to the HCL Domino® 11.0.1 documentation. Here administrators can find information about planning, installing, configuring, and administering Domino 11.0.1.
- Translated documentation
  The HCL Domino 11.0.1 documentation is currently available in the following languages.
- What's new in Domino® 11?
  Learn about all of the new features for administrators in HCL Domino® 11.
- Overview
  Welcome to HCL Domino® Administrator Help.
- Domino trial
  A trial version of HCL Domino® 11.0.1 is available free of charge.
- Installing
  Use this documentation to install the HCL Domino® server and subsequently deploy the HCL Notes®client.
- Planning
  Use this topic as an overview of planning task.
- Configuring
  Use this information to configure your network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters.
  - Configuring a network
    This section presents the planning concepts and setup procedures necessary for a successful HCL Domino® deployment over a network. It provides information on network protocols from a Domino perspective but does not attempt to provide general network information.
    - Domino® and networks
      A variety of client systems can use wireless or wired technology to communicate with Domino® servers over local area networks (LANs), wide area networks (WANs), and metropolitan area networks (MANs). For example, Notes® workstations and Domino servers use the Notes remote procedure call (NRPC) protocol running over the LAN's network protocol to communicate with other Domino servers. Other client systems, such as Web browsers, Internet mail clients, wireless application protocol (WAP) devices, and personal information management (PIM) devices, can also communicate with Domino servers.
    - Network security
      Physical network security is beyond the scope of this documentation, but you must set it up before you set up connection security. Physical network security prevents unauthorized users from breaking through the network and using one of the operating system's native services -- for example, file sharing -- to access the server. Physical network security also comes into play when any data is exposed, as the potential exists for malicious or unauthorized users to eavesdrop both on the network where the Domino® system resides and on the system you are using to set up the server.
    - Setting up Domino® servers on the network
      Before and after installing a Domino® server, perform required tasks.
      - Setting up Notes® named networks
        The Domino® Server Setup program automatically places all servers that are in a Domino domain and that run the same network protocol in the same Notes® named network (NNN). In the Server document, the setup program assigns each NNN a default name in the format portname network.
      - Fine-tuning network port setup on a server
        After you install and set up a Domino® server, review the list of network ports that were enabled by the Server Setup program. Unless you customize network settings during setup, Domino enables ports based on the current operating system configuration. To conserve system resources, disable the ports for protocols that you do not need.
      - Server setup tasks specific to TCP/IP
        After you run the Domino® Server Setup program, complete these procedures:
        Setting up a secondary name server
        To ensure that the Notes® Name Service is always available to Notes users, assign a secondary name server in users' Location documents.
        Changing the TCP/IP connection-time-out interval
        You can increase the number of seconds that HCL Domino® waits before terminating a connection attempt. For example, increasing the time-out interval is often necessary on a server that dials up other Domino servers. The default time-out interval is 5 seconds.
        Enabling support for IPv6 on a Domino® server
        You can enable support for IPv6 on a Domino® server that runs the IMAP, POP3, SMTP, LDAP, or HTTP service.
        Reordering multiple server ports for TCP/IP
        If a Domino® server has multiple Notes® network ports for TCP/IP, the order in which these ports are listed in the NOTES.INI file and the Server document affects how other servers and workstations connect to this server. The Ports setting in the NOTES.INI file determines which port a workstation or server tries first. In the absence of other settings that bind an NRPC, POP3, IMAP, SMTP, or LDAP service to an IP address, all of these services will try to use the port listed first in the NOTES.INI file.
        Binding an NRPC port to an IP address
        By default, all TCP/IP-based services on an HCL Domino® server listen for network connections on all NICs and on all configured IP addresses on the server. If you have enabled more than one Notes® network port for TCP/IP (TCP port for NRPC) on either a single Domino server or a Domino partitioned server, you must associate the NRPC ports and IP addresses by binding each port to an address.
        Binding an Internet service to an IP address
        If the HCL Domino® server has multiple HCL Notes® network ports for TCP/IP (NRPC ports) and the server is also hosting the SMTP, POP3, IMAP, LDAP, Domino IIOP (DIIOP) or Internet Cluster Manager (ICM) service, you must specify the NRPC port that you want the service to use in the NOTES.INI file. If you do not specify an NRPC port for an Internet service, by default the service will use the port listed first in the Ports setting in the NOTES.INI file. You can specify the same NRPC port for multiple Internet services.
        Assigning separate IP addresses to partitions on a system with a single NIC
        If you use a single NIC with multiple IP addresses, you must complete additional configuration instructions, which are based on your operating system, for each server partition. Using separate IP addresses with a single NIC can have a negative impact on the computer's I/O performance.
        Configuring a partitioned server for one IP address and port mapping
        To configure server partitions to share the same IP address and the same NIC, you use port mapping. With port mapping, you assign a unique TCP port number to each server partition and designate one partition to perform port mapping. The port-mapping partition listens on port 1352 and redirects HCL Notes® and HCL Domino® connection requests to the other partitions.
        Changing a TCP or SSL port number
        The following sections describe the TCP ports that HCL Domino® services use and provide guidelines should you ever need to change these ports.
        Confirming that TCP/IP is configured properly
        Before you can use TCP/IP for communication, confirm that the configuration is properly set up.
      - Server setup tasks specific to NetBIOS
        After you run the Domino® Server Setup program, complete these procedures:
  - Configuring users and servers
    Topics in this section describe how to set up users and servers.
  - Editing the NOTES.INI file
    You should rarely, if ever, need to modify a server's or client's NOTES.INI file. The NOTES.INI file contains many settings that Domino® and Notes® rely on to work properly. An accidental or incorrect change may cause Domino or Notes to run unpredictably. Therefore, you should edit the NOTES.INI file only if special circumstances occur or if Support recommends that you do so.
  - Configuring directory services
    This section describes how to plan, set up, and use HCL Domino® directory services.
  - Configuring messaging
    This section provides an overview of messaging and describes how to set up mail routing, how to set up and customize mail servers, and how to track mail.
  - Configuring iNotes®
    HCL iNotes® provides HCL Notes® users with browser-based access to Notes mail and to Notes calendar and scheduling features. Administrators specify mail policy and security policy settings as well as notes.ini file settings to complete the full implementation of HCL iNotes.
  - Configuring Web servers
    This section describes how to set up the HCL Domino® Web server, and the Domino Web Navigator.
  - Setting up a cluster
    Setting up a cluster includes the tasks of creating and verifying that it is working correctly, and then setting up user access, mail, replications, size quotas, directory assistance, roaming, web navigation, and use of a private LAN in the cluster.
- Securing
  This section describes security features, including execution control lists, IDs, and SSL.
- Administering
  This documentation provides information about the administration tools for managing and monitoring servers and databases.
- Tuning
  Use this information to improve HCL Domino® server, Domino Web server, and messaging performance through the use of resource balancing and activity trends, Server.Load commands, advanced database properties, cluster statistics, and the Server Health Monitor.
- Troubleshooting
  This section describes how to find and solve problems with HCL Domino® server and Administrator client.
- Notices

Setting up a secondary name server

To ensure that the Notes® Name Service is always available to Notes® users, assign a secondary name server in users' Location documents.

About this task

You can specify a different secondary name server for any location whose Location type is either Local area network or Custom. The secondary server can use either the TCP/IP, or NetBIOS protocol. The secondary name server is used when:

The user's home server is down.
The user's home server is not running the expected protocol, for example, TCP/IP.
The name of the user's home server cannot be resolved over the expected protocol, for example, TCP/IP.
Note: You can use desktop policy settings to assign secondary name servers to groups of users.

Procedure

In Notes® client, select File > Locations > Manage Locations, and select the location for which you want to designate a secondary name server.
Click Edit .
Click the Advanced > Secondary Servers tab.
To specify a secondary server for one of the offered protocols, for example, TCP/IP, in the Secondary TCP/IP Notes name server field, enter one of the following:
- The common name of the Domino® server -- for example, Notesserver1
- The hierarchical name of the Domino® server -- for example, Notesserver1/Renovations
In the Secondary TCP/IP host name or address field, enter one of the following:
- IP address -- for example, 197.114.33.22.
- The fully qualified domain name -- for example, notesserver1.renovations.com
- The simple host name -- for example, notesserver1
Optional: Specify secondary servers for either NDS or NetBIOS.
Click Save and Close.