- Joined
- Feb 20, 2017
- Messages
- 7
- Reaction score
- 0
Got a bit of a strange one. We have just taken over someone's 3CX administration and found that their customer.3cx.com DNS entry was pointed to the public IP of where their SBC was. Did the procedure to change this (set to dynamic, restart services, set to fixed, restart service) only to find a few days later it is back pointing to the SBC's public IP.
The configuration is that the 3CX instance is on Google cloud on Server 2016 and all their phones are connected via an on-site SBC. Any suggestion of why the DNS entry keeps changing back to the SBC?
The configuration is that the 3CX instance is on Google cloud on Server 2016 and all their phones are connected via an on-site SBC. Any suggestion of why the DNS entry keeps changing back to the SBC?