Solved FQDN does not resolve to my external IP

Status
Not open for further replies.

jakthree

Free User
Joined
Feb 8, 2019
Messages
124
Reaction score
18
Whois live DNS lookup of my FQDN does not return the external IP address of my 3CX PBX. I have waited a couple days to see if time would fix the problem but it has not.
Who do I contact at 3CX to have my FQDN address fixed?
Thank you
 
Do you have a static IP from your ISP? If not, you'll want to tell your 3CX server you have a dynamic IP (Settings > Network).
 
Hello @jakthree

If your public ip changes then navigate to Settings / Network and set the option to Dynamic IP address. Restart the PBX services and wait for the DNS propagation. Once the resolution is correct you can set it back to static. IF you do not have a static IP address however i would recommend leaving the option to Dynamic so that the PBX can auto detect changes.
 
My IP addresses are static ISP provided. I have temporary changed Settings -> Network to Dynamic Public IP.
Which service(s) to restart?
9616

Here is how I got into this problem.
  1. Registered site-1 and got a license key (key-1).
  2. Installed 3CX (on-premise VM windows) at site-1 and completed first time config using key-1.
(site-1's static ISP provided external IP is ...235)
upon completion of site-1 first time setup, FQDN = site-1.xx.xxx.xx = IP ...235 (correct)
  1. Tested site-1 for two weeks until I was ready to setup site-2.
  2. Installed 3CX (on-premise ISO Linux) at site-2 and completed first time config using key-1.
(I now know using key-1 was a mistake because site-2 was setup using site-1's credentials)
(site-2's static ISP provided external IP is ...220)
upon completion of site-2 first time setup, FQDN = site-1.xx.xxx.xx = IP ...220 (this is wrong)
  1. Ooopps. Registered site-2 and got a license key (key-2).
  2. Re-installed 3CX at site-2 and completed first time config using key-2.
(site-2's static ISP provided external IP ...220)
upon completion of site-2 first time setup, FQDN site-2.xx.xxx.xx = IP ...220. (correct)
However the FQDN of site-1.xx.xxx.xx remained IP ...220. (this is wrong)

All my 3CX site-1 mobile clients are broken because the site-1.xx.xxx.xx IP resolves to site-2's IP.
I need FQDN of site-1.xx.xxx.xx to change IP ...235 (correct).

Thank you,
 
Last edited:
My FQDN took about 45 minutes to propagate. I have set Settings - Network - Static IP.
Thank you for your help.
 
My FQDN took about 45 minutes to propagate. I have set Settings - Network - Static IP.
Thank you for your help.
Glad to see the issue has been resolved and thank you for updating the thread with your solution.
 
Status
Not open for further replies.

Forum statistics

Threads
111,856
Messages
589,404
Members
164,693
Latest member
FLCC