FQDN not resolving

[network19]

Hi all

One of our companies FQDN has stopped resolving. No changes have been made and i have tried the move to dynamic IP and restart services then move back to Static IP and restart services. Its really odd but it is hampering rollout of windows clients as they cannot connect out of the office. Any ideas gratefully received

 

[Saqqara]

Please give us info the the system as per https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

I am guessing you are running ver 16.

 

[network19]

• 3CX Version, Pro perpetual 16.0.16
• Server OS, Windows Server 2012 R2
• Is the 3CX Server Hosted and where? On Prem
• IP Phone Make/Model/Firmware version, Windows App
• Provisioning Method: Tunnel / Local
• Trunk Provider or VoIP Gateway Make/Model, Telapliant
• Has the Firewall Checker passed: Yes
• Are custom Phone Templates being used: No

 

[bitn2]

You need to Upgrade Windows Server to at least 2016 and 3cx to V18.

 

[network19]

Still think there is an issue with FQDN as this did work till a few weeks ago and now does not resolve at all

 

[bitn2]

Still think there is an issue with FQDN as this did work till a few weeks ago and now does not resolve at all

Yes, the Problem is the outdatet version of the server and 3cx.

 

[JohnS_3CX]

At this point, Server 2012 might not even be able to reach the 3CX activation server and your PBX will no longer be able to refresh the FQDN.

Get a backup, and redeploy on a supported OS and PBX version.