3CX failover - passive server not updating fqdn when becoming active

[Larry-B]

Hi everyone,

I have setup two instanced on AWS, each instance has its own public IP and both can reach one another. When I try to manually test the failover by shutting down the main instance the passive instance does not update the fqdn with its IP address. I have to manually refresh the license in order to get it to sync.
I have used this guide as a reference https://www.3cx.com/docs/failover/.
I am using 3CX FQDN so I did not use any of the failover scripts since from what I see they are meant to be used when you are self hosting the DNS records.
I have also tried to change external IP configuration to the dynamic option hoping the stun queries would force the fqdn refresh.

 

[Larry-B]

Support info generated from Passive server, the Active server instance is not currently running and fqdn is still pointing to Active server, it did not fail over to the Passive.

 

[Alphabetic]

What is your license type?

There is a TTL for DNS to update and enterprise is the shortest time (i think 5 minutes) whereas pro is longer.

 

[Larry-B]

I have Enterprise license. But it looks like that it started working as intended after multiple reboots of the aws instance. I will still need to test it for extended period to make sure its not an exception but the rule.

 

[Larry-B]

After extensive testing the instances are working normally now. Looks like the original issue was not related to 3cx, after few reboots of ec2 instance on aws the passive server started to detect primary instance failing each time.