Solved Move pbx to a new machine without releasing FQDN

[Alan Yang]

Should I move my pbx to a new machine without releasing FQDN?

I need keep the same FQDN and license, just change the ip address and restore the backup on a new machine.

 

[pact]

Hi @Alan Yang ,

If you are simply wishing to migrate your PBX to another location, perform a backup of the existing system and restore that backup to the new location. Do not release the FQDN unless you are wishing to change keys. (And from what you describe, you are not wishing to change keys).

During the restoration 3CX will confirm which interfaces you want to use and once it re-activates the FQDN will update.

Be aware once the new instance activates and updates the FQDN the old instance will stop receiving traffic from your external extensions.

 

[YiannisH_3CX]

Hello @Alan Yang

If you wish to keep the same FQDN and licence key then there is no need to release the FQDN from the licence. Take your backup and proceed. As mentioned by @pact you should only have 1 instance online as you will face issues with the licence and DNS resolution if both instances are up at the same time

 

[Fabio Furlan de Carvalho]

After reinstalling and restoring the backup in another machine another ip with the same license, how long does it take to update the IP in the name dns xxxx.3cx.de?

 

[YiannisH_3CX]

The update will be done almost immediately however the DNS propagation could take several hours.

 

[Fabio Furlan de Carvalho]

Hello, the problem is that already 24 hours and still has not updated, is there no fault on the side of the server 3cx? the dns name is furlaninfo.3cx.de and the new ip registered yesterday is 5.199.150.170

 

[craigreilly]

https://furlaninfo.3cx.de:5001/ ->
5.189.150.170

is that resolving to old server? (maybe 199 is a typo)

 

[Marari]

Pinging furlaninfo.3cx.de [5.189.150.170] with 32 bytes of data:
Reply from 5.189.150.170: bytes=32 time=155ms TTL=49
Reply from 5.189.150.170: bytes=32 time=154ms TTL=49
Reply from 5.189.150.170: bytes=32 time=154ms TTL=49
Reply from 5.189.150.170: bytes=32 time=155ms TTL=49

Notice the bold...

 

[Fabio Furlan de Carvalho]

sorry I informed the wrong ip the new server has this same ip 5.189.150.170, but when pingo presents the old see:
Disparando furlaninfo.3cx.de [178.238.228.249] com 32 bytes de dados:
Resposta de 178.238.228.249: bytes=32 tempo=243ms TTL=116
Resposta de 178.238.228.249: bytes=32 tempo=242ms TTL=116
Resposta de 178.238.228.249: bytes=32 tempo=233ms TTL=116
Resposta de 178.238.228.249: bytes=32 tempo=231ms TTL=116

I already did a flushdns and it did not work

 

[craigreilly]

Looks like your DNS is not updating. Are you using DNS of ISP?
Try a different DNS - like Google if you can. I almost always use 8.8.8.8 because it's fast... but I'm in the US.

 

[Fabio Furlan de Carvalho]

ok after changing the dns worked, thank you.

 

[Marari]

@Fabio Furlan de Carvalho

Glad that @craigreilly and I could help

 

[YiannisH_3CX]

Glad to see the issue has been resolved.