FQDN IP Update

[Tyler.Calhoun]

Hello,
we have an Enterprise license and today our 3CX Wan was down.

WAN 2 has taken over directly. I then changed the public IP in the 3CX dashboard.

I pinged the FQDN from 6 different sites. It took 35 minutes to update the IP behind the FQDN.
Enterprise promises 5 minutes after all.

What can I do differently next time?

Thanks

 

[Nathan@Voxtelesys]

Are each of these 6 sites caching DNS locally? If you are using your ISP provided DNS, I would suggest switching to Google's Quad 8 or Cloudflares 1.1.1.1 for both server and sites.

Also, check out https://www.3cx.com/docs/failover/
I have had good luck with selecting License Key > Edit > OK and then restarting 3CX Services to update the DNS record.

 

[Tyler.Calhoun]

Are each of these 6 sites caching DNS locally? If you are using your ISP provided DNS, I would suggest switching to Google's Quad 8 or Cloudflares 1.1.1.1 for both server and sites.

the server uses 8.8.8.8 and 1.1.1.1

I have had good luck with selecting License Key > Edit > OK and then restarting 3CX Services to update the DNS record.

I will test that.
My only problem is that I can't restart the services while all our call centers are working.

We have two WAN connections with a load balancer and failover function.

If the primary WAN has a problem, WAN2 immediately takes over and the 3cx stays online. This changes the IP though. I enter the new IP in the dashboard and had assumed that this is automatically distributed to all DNS resolvers.

Thanks for your help