When several CommuniGate Pro Servers use a Shared Directory to keep all their Domain Integration Records, these Servers can be used to serve the same Domain (or the same Domains). Such a Domain is called a Distributed Domain, and each Server hosts a subset of that Domain Accounts. The Distributed Domain should not be a Main Domain of any CommuniGate Pro Server:
In this example:
When an Account is created, renamed, removed, or updated on one of the sv*.corp.dom Servers, the Directory Unit on the Shared Directory Server is updated. As a result, the Shared Directory contains records for all Accounts created on all sv*.corp.dom Servers.
When any Server creates an Account and places a record into the Shared Directory, it stores the Server Main Domain name as the record hostServer attribute.
The Shared Directory can be used to route Distributed Domain mail to the proper location (Server). Open the General page in the WebAdmin Settings realm, then open Cluster settings page, and enable the Directory-Based Clustering. The address routing mechanism is modified:
This Distributed Domain configuration is useful for multi-location and international organizations and corporations where all employee Accounts should be in the same Domain, but each organizational unit is served with its own Server. The DNS MX records for the such a Distributed Domain should point to any or to all Servers hosting that Domain. When a Server receives mail for a Distributed Domain, it either delivers the mail locally (if the addressed Account is hosted on that Server), or relays mail to Server specified in the hostServer attribute of the Account Directory record.
Note: the names and IP addresses for "distributed" systems should be entered into the "Static Members" table on the Clusters WebAdmin page.
Usually, one of the Servers (the "main l