- Joined
- Oct 19, 2017
- Messages
- 131
- Reaction score
- 23
We have a 3CX enterprise installation and we needed to configure a second machine to have in case of death on production machine.
So, with a full backup, we disconnected the production machine from the internet and we have tried to restore the machine on a different location out of office hours. When that install started it got the FQDN pointed to the IP on this new location. I have configured it as dinamic IP. But that installation attempt didn't work.
We have plugged the production 3CX server again and after 6 hours still the FQDN is not pointing to the correct IP. The DNS TTL of enterprise should be 300s.
Which would be the way to force the FQDN back to correct IP?
So, with a full backup, we disconnected the production machine from the internet and we have tried to restore the machine on a different location out of office hours. When that install started it got the FQDN pointed to the IP on this new location. I have configured it as dinamic IP. But that installation attempt didn't work.
We have plugged the production 3CX server again and after 6 hours still the FQDN is not pointing to the correct IP. The DNS TTL of enterprise should be 300s.
Which would be the way to force the FQDN back to correct IP?