PBX not reachable via FQDN after migration to new EC2 instance

Status
Not open for further replies.

theDUCprobe

Bronze Partner
Advanced Certified
Joined
Jun 7, 2022
Messages
4
Reaction score
1
Hi,

We cannot reach our pbx via it's fqdn after a migration was done from nano ec2 instance to a micro ec2 instance. Migration was done by backup old pbx and restoring it on new instance.
PBX version is 18.0 (Build 939)

Also, when users try to scan their QR code the get the below message displayed on their mobile device:
1698319825384.png
 
Hello

DNS will not have populated yet.

I would try forcing a license refresh from your MGMT console to give it an elbow.
 
Thanks kieferschild.

Migration was completed at 16:57pm (Irish Standard Time) yesterday, I should expect dns to have updated. Also license key information was refreshed but sadly that did not work.

On the old system, the public ipv4 was set as static. Could it be that the fqdn will remain attached to the ip on the old ec2 instance unless changed some how?

Thanks again
 
Is the old instance still up?
'
If you ping FQDN are you getting new IP address and if so, is it coming back with IPv4 or 6? You might need to disabled v6.
 
Hmm, just checked, nslookup is returning old public ip for the fqdn.
 
So check what DNS servers youre using on the devices trying to connect up and change them if need be.

Also check you've not got static DNS entries anywhere.
 
  • Like
Reactions: jed
Hmm, just checked, nslookup is returning old public ip for the fqdn.

Just a dump Question, but to eliminate this. Do you have DNS on your inside that answer with the old IP? (Could also be a hostfile for some old testing perhaps?) In other words, can you access the server from another network with the right IP?
 
We made a bit progress, I did change the IP to dynamic on the mgmt console and restarted the 3cx services, ran another nslookup query for the fqdn and that now returns the new public ip. However, I still can't reach the pbx using the fqdn, might need some time to updated the name servers.

@jed No we don't, I believe the fqdn is hosted on 3cx name servers.
 
  • Like
Reactions: jed
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet