Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status Needs Review
Workspace Sametime
Categories Chat
Created by Guest
Created on Feb 2, 2021

Provide some way to implement redundancy for multiple LDAP server on Sametime Community Server without load balancer

One of our customer used the following way to implement redundancy for multiple LDAP server on Sametime Community Server:


This Sametime server has some strange setting in da.nsf and stconfig.nsf which have two LDAP documents to point to two Domino LDAP servers . These two Domino LDAP servers are in the same Domino Cluster and has the same directory data. The customer use these setting to implement redundancy for Domino LDAP.


In current supported version of Sametime Community Server (9.0.x/10.0.x/11.x), the above way to implement redundancy for multiple LDAP server is not supported. Sametime only support this configuration when using a Load balancer.

But some customer think a load balancer need more cost and configuration is complicated, and wish Sametime could provide a simple way to implement redundancy for multiple LDAP server in future release.

For example, for a two LDAP server configuration, Sametime can provide some parameter to switch real connection from LDAP Server A to LDAP Server B if LDAP Server A is down.

  • Attach files
  • Guest
    May 25, 2021

    You can implement Round Robin DNS for this, and set the respray interval to 5 minutes. It won't be a perfect solution, but should get you a single host to use for LDAP. This will not perform any kind of health check to know if a server is up or down. A network load balancer is the best way. The re-spray parameter and other best practices are described here: