Hi Everyone,
When i originally created a 3cx account i did a managed instance inside of 3cx's Google compute cloud and assigned it to the domain name companypbx.3cx.us. As i was demoing the software i decided that i wanted it in my amazon account so i re-deployed the instance.
Now i have an instance of 3cx inside of my AWS account that i created with PBXExpress, the FQDN of which is companypbx.3cx.us (same domain as above) this is the FQDN that is bound to the SSL cert and the install of 3cx.
This appears to have caused DNS issues on 3cx's end as periodically the domain companypbx.3cx.us will re-bind to the old google compute instance and break all inbound/outbound calls.
Is there a way to have 3cx delete that old instance? or rebind 3cx to my own sub-domain? I already have a bunch of users and configs setup in this instance so i would prefer to not nuke it and start completely over.
When this has happened in the past i have gone into my customer portal on the 3cx website and told it to release the old server, and then after a day or so it would re-bind to the new server, but i need to get this fixed permanently as we are starting to deploy the PBX instance in production.
I am not sure who to contact to fix this issue as it's clearly a DNS problem on 3cx's end but they don't offer support unless you pay.
Any help would be awesome. Thanks.
When i originally created a 3cx account i did a managed instance inside of 3cx's Google compute cloud and assigned it to the domain name companypbx.3cx.us. As i was demoing the software i decided that i wanted it in my amazon account so i re-deployed the instance.
Now i have an instance of 3cx inside of my AWS account that i created with PBXExpress, the FQDN of which is companypbx.3cx.us (same domain as above) this is the FQDN that is bound to the SSL cert and the install of 3cx.
This appears to have caused DNS issues on 3cx's end as periodically the domain companypbx.3cx.us will re-bind to the old google compute instance and break all inbound/outbound calls.
Is there a way to have 3cx delete that old instance? or rebind 3cx to my own sub-domain? I already have a bunch of users and configs setup in this instance so i would prefer to not nuke it and start completely over.
When this has happened in the past i have gone into my customer portal on the 3cx website and told it to release the old server, and then after a day or so it would re-bind to the new server, but i need to get this fixed permanently as we are starting to deploy the PBX instance in production.
I am not sure who to contact to fix this issue as it's clearly a DNS problem on 3cx's end but they don't offer support unless you pay.
Any help would be awesome. Thanks.
