Hi all,
i searched and couldn't find anything similar ,
Dynamic IP might help with this use case but now with FQDN , i dont knwo whether it will work or how to make it work.
affects self-hosted only i believe
problem is in 3CX we can give one static IP as shown in below screenshot and that IP will be used by 3cx managed FQDN for the clients/users to connect to 3cx server.
issue is when that IP address need to be changed for any reason (internet provider went down, to put backup provider ).
currently manually only another IP address can be updated and DNS propagation takes time,
so we could have an option to enter 2 static IP addresses then automatic failover could happen in above situation.
like 3cx in there FQDN DNS have another A record like backup , so 3cx clients could check for that if the primary is not connecting to the 3cx server.
kindly let me know your thoughts or anything I'm missing to achieve this requirement with existing features ?
i searched and couldn't find anything similar ,
Dynamic IP might help with this use case but now with FQDN , i dont knwo whether it will work or how to make it work.
affects self-hosted only i believe
problem is in 3CX we can give one static IP as shown in below screenshot and that IP will be used by 3cx managed FQDN for the clients/users to connect to 3cx server.
issue is when that IP address need to be changed for any reason (internet provider went down, to put backup provider ).
currently manually only another IP address can be updated and DNS propagation takes time,
so we could have an option to enter 2 static IP addresses then automatic failover could happen in above situation.
like 3cx in there FQDN DNS have another A record like backup , so 3cx clients could check for that if the primary is not connecting to the 3cx server.
kindly let me know your thoughts or anything I'm missing to achieve this requirement with existing features ?
