Solved 3CX Registering Wong IP Address

[mhemmes]

So I started with my free 3CX v15 account for my home office on a staging VM, using one of my static IP addresses. Once I saw the system worked well with my Polycom phone, I migrated over to a permanent workstation on a different static IP. Everything went without a hitch and worked as expected. When the v16 was officially released, I upgraded the system, again no problems. That is until after a couple of days, I noticed I couldn’t access the web portal or use my iOS app any longer from outside my LAN. During troubleshooting, I performed a lookup on my {host}.{state}.3cx.us domain and saw that it was using my old staging IP address. I go into the Windows Services app, restart all 3CX services and the correct public static IP gets registered. After a day or so, it’s back to the wrong IP again. Does anyone have any ideas what might be going on here? The 3CX IP setting are all correct. Thanks in advance!

 

[nub]

nslookup hostname

sometimes on some internal networks i will change the host name to resolve to an internal ip with hosts file or routing and the etc.etc.3cx.etc would resolve to the private ip not the public ip.

 

[mhemmes]

nslookup hostname

sometimes on some internal networks i will change the host name to resolve to an internal ip with hosts file or routing and the etc.etc.3cx.etc would resolve to the private ip not the public ip.

The problem is the public DNS record from the 3CX name server is being updated to my old public IP, nothing wrong on the internal LAN side. I’d love to be able to login to my 3CX account and see the node making the update.

 

[BrenttG]

1. Check the IP settings in the 3CX management console to make sure the proper IP is indicated there, this does not change automatically, you must manually change it! Do not use Dynamic Public IP as a bandaid to auto detect it, in your scenario it would likely deduce the wrong IP...

2. Depending on your firewall, you may need to configure it such that outbound traffic from the 3CX server goes out using a source IP of the static ip you are using for its inbound.

Put your chosen Static IP for the 3CX server into the box i have highlighted in yellow, and make sure it is indeed set to "Static Public IP", Then give it a few hours for DNS to update, and see if your all fixed up.

 

[BrenttG]

I Editted the above with some added info.

 

[YiannisH_3CX]

Please make sure that the old installation is not online and interfering with the DNS resolution. Then in the new system navigate to Settings / Network and switch the PBX to Dynamic IP address. Restart all services for the change to take effect immediately and wait for the DNS propagation. Once the FQDN points to the correct IP you can switch it back to static.

 

[mhemmes]

Please make sure that the old installation is not online and interfering with the DNS resolution. Then in the new system navigate to Settings / Network and switch the PBX to Dynamic IP address. Restart all services for the change to take effect immediately and wait for the DNS propagation. Once the FQDN points to the correct IP you can switch it back to static.

Sorry for the late response...busy work week. So this is the solution here. In my haste, I only uninstalled the 3CX application that I was demoing and forgot to actually uninstall the original server instance in my VM. So every time I was starting my VM (most days), it would register the other public IP with the 3cx.us name servers. Thank you for your help, I really love this system, I've moved two of my companies from RingCentral and Windstream, and I'm saving literally thousands and have a much more feature rich and efficient interface. Thank you guys, truly.

 

[JohnS_3CX]

Hi @mhemmes you're welcome. I'm glad it was resolved and that you are enjoying the system