From version 3.5, Cisco Meeting Server can use other validations Hostname/IP Address If you are deploying or upgrading to version 3.6 (or 3.5). The database cluster nodes might fail to connect to each other. The reason is that each server will try to resolve the server's name (or hostname) of each node in the cluster, which is not available in version prior 3.5.
To solve this issue, You need a DNS Record, fortunately a DNS RR record can be created on CMS to resolve the server identity locally.
Let's take an example, if you have three Nodes running the database cluster with 3.6 version with hostname CMS1 10.1.5.61, CMS2 10.1.5.62 and CMS3 10.1.5.63, CMS1 as the primary or the master node, you need the following DNS RR Records as follow:
On CMS1:
dns add rr "cms2. IN A 10.1.5.62"
dns add rr "cms3. IN A 10.1.5.63"
On CMS2:
dns add rr "cms1. IN A 10.1.5.61"
dns add rr "cms2. IN A 10.1.5.63"
On CMS3:
dns add rr "cms1. IN A 10.1.5.61"
dns add rr "cms3. IN A 10.1.5.62"
