+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: FAQs etc (/forumdisplay.php?fid=38)
+--- Forum: Suggestions for Documentations (/forumdisplay.php?fid=64)
+--- Thread: local_time.ntp_server1 requires *fully qualified* domain name (/showthread.php?tid=42962)
local_time.ntp_server1 requires *fully qualified* domain name - Z - 07-15-2019 07:29 PM
The documentation for local_time.ntp_server1 says only that "IP address or domain name" are permitted values.
My suggestion for the documentation is to add some explanatory text to let the reader know that "domain name" actually means fully qualified domain name, and that an unqualified hostname won't work.
The web management GUI merely says "Illegal address!" if the administrator tries to configure an unqualified hostname.
(Or, another option might be to update the firmware to accept unqualified hostnames, which many organisations use internally.)
(07-15-2019 07:29 PM)Z Wrote: The documentation for local_time.ntp_server1 says only that "IP address or domain name" are permitted values.
My suggestion for the documentation is to add some explanatory text to let the reader know that "domain name" actually means fully qualified domain name, and that an unqualified hostname won't work.
The web management GUI merely says "Illegal address!" if the administrator tries to configure an unqualified hostname.
(Or, another option might be to update the firmware to accept unqualified hostnames, which many organisations use internally.)
Interestingly, unqualified hostnames are accepted in the auto-provisioning .cfg file, and NTP updates are successful. It appears to be only the web GUI which rejects unqualified hostnames.