Solved FQDN binding with wrong IP

[ajay8100]

Hello,
I am having some issues with FQDN binding with wrong IP address.
I am creating a new instance in cloud (OVH/Amazon LightSail) but the build is failing every time.
After few minutes the FQDN is registering with my WAN IP instead of the WAN IP of the cloud instance that I am creating and the instance creation process continues to run for hours.
I tried multiple times and every time the FQDN registers with my WAN IP

Thanks...

 

[cobaltit]

If you didn't turn off your old instance that will happen. Also the DNS updates can take up to 6 hours (for standard keys) to update. So make sure your old instance is offline, and stop reinstalling or you will get the LE limit on cert generation.

 

[NikosT_3CX]

@ajay8100 can you PM me with your license key to check it ?

 

[NikosT_3CX]

@ajay8100 I have found the key and as I can see we already have a ticket open in the Cloud Team about this.
Your FQDN is bound with a Public ip address because we can see requests coming from this site to our Activation Server from a PBX. You mentioned that this is the ip address of your office, but I would recommend to check if you have forgotten a VM turned on with a PBX installed and having this key installed on.