- Joined
- Feb 28, 2024
- Messages
- 10
- Reaction score
- 0
Dear 3CX and Everyone,
Good Afternoon.
We are currently setting up a 3CX High Availability (HA) solution (Version 20 Enterprise, On-Premises with Debian OS). Our environment includes an active server at the DC site and a passive server at the DR site, each with its own LAN IP address and public IP address.
Our objective is to configure the 3CX FQDN DNS resolution so that it automatically updates to point to the public IP address of the active server, rather than the standby server. In other words, we want the 3CX FQDN to always resolve to the active server’s public IP, ensuring seamless service continuity. As our current issue we found the 3CX FQDN automatically resolve to public ip standby server not active server.
Could you kindly provide guidance or recommendations on how we can change 3CX FQDN to active server ?
Best regards,
Tongmeng
Good Afternoon.
We are currently setting up a 3CX High Availability (HA) solution (Version 20 Enterprise, On-Premises with Debian OS). Our environment includes an active server at the DC site and a passive server at the DR site, each with its own LAN IP address and public IP address.
Our objective is to configure the 3CX FQDN DNS resolution so that it automatically updates to point to the public IP address of the active server, rather than the standby server. In other words, we want the 3CX FQDN to always resolve to the active server’s public IP, ensuring seamless service continuity. As our current issue we found the 3CX FQDN automatically resolve to public ip standby server not active server.
Could you kindly provide guidance or recommendations on how we can change 3CX FQDN to active server ?
Best regards,
Tongmeng

