FQDN and IP name stuck to an old instance

[callahero]

Hi all, I have a AWS Lightsail instance of 3cx that ran fine for a couple years. I had some issues one day that prompted me to want to relocate the instance to Ohio from the more issue prone DC area. I created a new AWS Lightsail instance and used the 3cx Express to install and set up my duplicate installation in the new instance. Once this was done, i notified my SIP provider to add the new static IP to my system and after a backup restore, i was up and running. A few weeks go by and i started to see calls not coming through. Now it seems that if i ping my FQDN it resolves to the old instance IP address, not the new one that the 3CX Express created. I can get into both installations, one with the FQDN and the new one in the Ohio server farm with the IP. I would like my FQDN corrected and i am willing to delete the old AWS instance. Any suggestions are appreciated. Thanks in advance!

 

[innotip]

Hi,

Please first delete (or at least shut down) the old instance, THEN switch new instance network to "dynamic IP", wait a minute, then check that it took ip into account, then get back to static IP. Should make the trick !

 

[callahero]

Thanks Innotip! That did the trick, i saw that you had recommended this to someone else and i tried it but did not stop the old instance first. now that i did, all worked as expected. Thank you!