Migration and FQDN

[lubomir.bielik]

Hi guys!

We recently moved our 3CX in a way the we just cloned the virtual drive of VM and moved it. This changed the public IP, which I changed in management console, but we are unable to access 3CX with FQDN. Is there a way how to assign FQDN to new IP?

 

[jonpennell]

Unless you are on the Enterprise license, the TTL for the IP address on the FQDN is 6 hours - so it'll be at least this long until the changed IP/FQDN is updated. If it's been longer than this, maybe a router on-site is caching the FQDN...?

 

[eddv123]

In future I would just select dynamic IP address in your 3CX instance, despite the fact that it comes up in red it works fine and it is fully supported.

Although you have virtulized the instance where is it located ? if you can or have local access why not simply access it on http://local-ip-address.3cx.co.uk:5000 (dependent of region) if you can get access but want to stick to static IP in order to get you public ip to change in 3CX's dns servers you need to navigate to Settings > network and switch to use 'Dynamic Public IP (IP changes)'

Then restart services using the services.mmc. Then wait 20 minutes and go back and switch back to ' Static Public IP (IP Address does not change)' and again restart services. It will take up to an hour to change on our systems DNS and then up to 6 or more hours to propagate around the internet.

 

[YiannisH_3CX]

As mentioned you need to switch the PBX to Dynamic Public IP and restart the PBX services. This will enable the PBX to detect the new public IP and update the DNS entry.
Once the FQDN points to the correct IP you can switch it back to Static