Hey everyone,
I recently replaced my ISP-provided 5G router (with OPNsense behind it) with a UniFi UDR-5G-MAX. This finally allowed me to enable native IPv6 on my network.
Initially, everything worked as expected. However, after my ISP assigned a new dynamic IPv4 address, I noticed that my 3CX FQDN was still pointing to the old IPv4 address.
The issue first became apparent because the 3CX mobile app could no longer connect from outside my network.
For troubleshooting, I tried the following:
As a last test, I disabled IPv6 within the 3CX configuration (using SSH), restarted 3CX once more, and immediately after that the FQDN updated to the correct IPv4 address. External connectivity started working again.
This makes it appear that enabling IPv6 in 3CX somehow prevents the dynamic IPv4 address from being detected or updated for the 3CX FQDN.
I'm currently running 3CX Version 20.0.9.995
Has anyone else experienced this? Is this a known issue or expected behavior?
I recently replaced my ISP-provided 5G router (with OPNsense behind it) with a UniFi UDR-5G-MAX. This finally allowed me to enable native IPv6 on my network.
Initially, everything worked as expected. However, after my ISP assigned a new dynamic IPv4 address, I noticed that my 3CX FQDN was still pointing to the old IPv4 address.
The issue first became apparent because the 3CX mobile app could no longer connect from outside my network.
For troubleshooting, I tried the following:
- Restarted the 3CX server multiple times
- Clicked "Check License" several times to force communication with the 3CX servers
- Ran the built-in Firewall Checker (all tests passed successfully)
- Verified that general connectivity was working
As a last test, I disabled IPv6 within the 3CX configuration (using SSH), restarted 3CX once more, and immediately after that the FQDN updated to the correct IPv4 address. External connectivity started working again.
This makes it appear that enabling IPv6 in 3CX somehow prevents the dynamic IPv4 address from being detected or updated for the 3CX FQDN.
I'm currently running 3CX Version 20.0.9.995
Has anyone else experienced this? Is this a known issue or expected behavior?
