Restarting an old server will update the DNS to the old IP

[ITSmartwork]

Hi,

i just moved from one server to another but what i noticed was that if the old server is just restarted, it will update the ip address to the old server and thus using the old instance.
How is that possible?

thank you

 

[NicholasP_3CX]

Installing 3CX on a different server does not prevent the old server from activating (unless it is on an older update which cannot communicate with the activation server.)

Ultimately, you will need to restart your new server to update the DNS entry and delete the configuration from the old server.

If you do this too many times you will block your license key and will need the intervention of your partner and/or 3CX to unblock it, after justifying why this happened (fraud prevention)

 

[AWS2P]

this is how it works you need only one instance of same PBX running in same time

 

[ITSmartwork]

Both instances are on the same version "Version 20.0 Update 2 (Build 715 Release)" which is the latest available. How do i delete the configuration from the old server? Consider that on the old instance i have only Web Gui Administrator access.

 

[SteveITS]

From the dashboard you can stop all the services (click "Services"). That might help. But then you have to hope it doesn't get restarted. Better to turn it off, or uninstall 3CX if it's Windows.

 

[ITSmartwork]

As written previosly, i have only access on the dashboard.

 

[SteveITS]

But surely someone does? Or else, I guess, just hope the services don't start again.

Block via firewall rule?

 

[ITSmartwork]

What to block? I have no control over that other infrastructure which is hosting the old VM and is still switched on.

The only way is somehow to control it on the portal login.3cx.com
So you could black list some IP...
But of course this feature does not even exist on the portal.

 

[ITSmartwork]

Just thinking: would it work if i put a trial license on the old server?

 

[bitn2]

Just thinking: would it work if i put a trial license on the old server?

When its the same fqdn than no, that wont work. Reach out to the person who has access to this server und stop this vm.

 

[ITSmartwork]

When its the same fqdn than no, that wont work. Reach out to the person who has access to this server und stop this vm.

it cannot be the same fqdn for the same license.

 

[bitn2]

it cannot be the same fqdn for the same license.

It can and it is actually... Thats why your ip is switching to the old server.

 

[ITSmartwork]

correction: i wrote something wrong "it cannot be the same fqdn for the same license."
What i meant is that "it cannot be the same fqdn for different licenses."
Different license has different FQDN so that is why i'm asking if it might work or not..

 

[bitn2]

correction: i wrote something wrong "it cannot be the same fqdn for the same license."
What i meant is that "it cannot be the same fqdn for different licenses."
Different license has different FQDN so that is why i'm asking if it might work or not..

You need to reinstall to get a new fqdn.. So its the same problem like before.

 

[ITSmartwork]

You need to reinstall to get a new fqdn.. So its the same problem like before.

FQDN for a license does not change to my knowledge. It's just changes the IP even if you reinstall but the FQDN remains the same.

 

[bitn2]

FQDN for a license does not change to my knowledge. It's just changes the IP even if you reinstall but the FQDN remains the same.

correct, but you said you want to try a different licence. So you need to reinstall with different licence and fqdn. Problem still persist....

Why it is a problem to ask the person who have access to the server to stop and delete this vm?

 

[ITSmartwork]

correct, but you said you want to try a different licence. So you need to reinstall with different licence and fqdn. Problem still persist....

It should not. Inserting a different license, will change the FQDN on that server and even if they restart, it will not affect my instance(which is another FQDN). At least this is what i think it will work. So i needed a confirmation before proceeding if my assumption is correct...

Why it is a problem to ask the person who have access to the server to stop and delete this vm?

Because it is a big company and we have no support at all and that is the reason why i moved it on-premise, on my server room. I had days without the 3CX and 20 people complaning withour service. It can happen with big companies. I do not want to mention the name because it is a multinational company.

 

[NicholasP_3CX]

Replacing your license key will transfer your FQDN over.

This thread could go on for weeks, but the long and the short of it is, the old machine will need to be scrapped. Find who controls that machine and ditch it.

 

[ITSmartwork]

Replacing your license key will transfer your FQDN over.

so my assumption is correct: Inserting a different license, will change the FQDN on that old server and even if they restart, it will not affect my instance(which is another FQDN

the old machine will need to be scrapped. Find who controls that machine and ditch it.

trying without success

 

[bitn2]

so my assumption is correct: Inserting a different license, will change the FQDN on that old server and even if they restart, it will not affect my instance(which is another FQDN

No, it will switch the fqdn to the new licence. So your fqdn is gone...