Broken my FQDN by duplicate install

[deepee]

I have stupidly installed 3cx on a fresh server and used the wrong install code, this has installed and changed the FQDN of a working PBX to the newly installed server. I deleted the new server as soon as I realised but the FQDN which is xxxx.3cx.co.uk, now points to the wrong IP address.

Is there any way for me to fix this?

Thanks

 

[Saqqara]

Change the wan settings to dynamic, wait for awhile then change back to static

 

[deepee]

I am not sure what you mean or how this will help? The server has a static IP and the 3cx FQDN is fixed?

 

[Saqqara]

When you make the above change, it will force the system to update the 3cx fqdn.

3cx fqdn is based on this setting.

 

[deepee]

Ah ok. Is this the setting you mean?

Settings - Network - Public IP - External IP Configuration - Dynamic Public IP (IP changes)

 

[StefanW]

yes, make a change on the IP address type, wait for 10m and change it back.
After you must wait a bit more so the DNS change can propagate to all DNS servers...

 

[AWS2P]

Yes, then wait for DNS propagation 6 hours for STD or PRO licenses, 5 minutes for ENT

 

[StefanW]

Yes, then wait for DNS propagation 6 hours for STD or PRO licenses, 5 minutes for ENT

have a look about the TTL in Std and Pro licensees, we made changes to that rule.

 

[AWS2P]

Do you have a link where to find this, searched about Licenses or 3CX TTL with no result, perhaps I'm blind and info is under my nose

 

[Saqqara]

Do you have a link where to find this, searched about Licenses or 3CX TTL with no result, perhaps I'm blind and info is under my nose

Use mxtoolbox dns lookup tool