We recently changed the public IP on a 3CX system and we have a issue with the FQDN not updating.
I have seen posts about setting it to DHCP, restarting services, waiting the appropriate amount of time (6 hours in our case), and changing it back to static after the DNS updates.
I have done that multiple times and the DNS was not updating.
There was one post that I just read that this is not working due to the version of 3CX we are on (16.0.8.9), which is showing "Out of Date"
From the GUI Updates page, there is an option to upgrade to Version 18, but I worried that this might now work if our version is out of date.
Is it safe for us to upgrade directly to Version 18 from 16.0.8.9 ?
I have seen posts about setting it to DHCP, restarting services, waiting the appropriate amount of time (6 hours in our case), and changing it back to static after the DNS updates.
I have done that multiple times and the DNS was not updating.
There was one post that I just read that this is not working due to the version of 3CX we are on (16.0.8.9), which is showing "Out of Date"
From the GUI Updates page, there is an option to upgrade to Version 18, but I worried that this might now work if our version is out of date.
Is it safe for us to upgrade directly to Version 18 from 16.0.8.9 ?
