Solved FQDN - Not working

[carpediem302]

To do some more testing on the 3CX system. I uninstalled 3CX from our server at one location. Installed it and restored the backup at a different location (Different IP) I can connect to it from the outside with the IP address but not the FQDN. Firewall checks out, and the proper ports are opened. Does it take some time for the propagation to work? I did get an email saying 3CX detected an IP address change. The restore also creates the same FQDN as well. Any help would be appreciated.

 

[Saqqara]

std or pro can take 6 hrs for the fqdn to update

enterprise is 5 or 10 mins (can not remember the exact time)

if you added any dns entries for the fqdn, make sure you have updated these records (spilt dns)

 

[AWS2P]

If you use google dns 8.8.8.8 , even with STD or Pro license, I've never got to wait 6 hours for FQDN to point on new public IP. Most of the time few minutes.
from a CMD windows on a Windows pc, do a ipconfig /flushdns then a nslookup of FQDN should resolve.

 

[cobaltit]

But you can't control DNS on every device so it's good to know what to expect. There are ways to force a cache flush on many of the larger DNS providers though.

 

[carpediem302]

It ended up resolving itself on its own. Had to flush DNS