MikroTik Team, please introduce that feature at next releases - to be possibility to input cannonical names of NTP servers - not changed to IP addresse. I would like to put into "Primary NTP Server" and "Secondary NTP Server" name like: time.windows.com - not to be translated to IP addresse.

A good suggestion!

If you disable the ntp package and reboot, you’ll find System > SNTP, which does what you want as an NTP client.

However, if you want to use the NTP server, you need the ntp package. In this case, you can schedule a script to resolve a new IP address, as discussed here:

https://blog.ligos.net/2018-01-29/NTP-P ... rotik.html

MikroTik TEAM - could We expect that feature at next releases of RouterOS?

What feature? Some arrow to point you to the right menu?

What feature? Some arrow to point you to the right menu?

This behaviour changes once you install the ntp package, which provides the ntp server functionality. The possibility to configure reference servers as fqdns then disappears.

What feature? Some arrow to point you to the right menu?

As mentioned in an earlier post the SNTP client is fine, however upon installing the NTP package to provide a local NTP server the replacement NTP client still only accepts IP addresses, not names.

SNTP client only queries servers for correct time, updates router's time and exits/sleeps until next time. And due to that, SNTP client can resolve FQDN every time it makes connection. NTP server, OTOH, is kind of stateful. Which means that it follows server's performance and thus has to send subsequent queries to same server(s).

BTW, behaviour of NTP servers (e.g. under linux) is the same: it resolves FQDNs of servers at start (can use multiple servers if they are used in pool manner), but then sticks to same servers until it restarts.

Indeed it would be nice if we could configure NTP servers by entering FQDN (so that IP addresses update after a few years of operation without need to manually update IP addresses), but it would not affect the way NTP server works. But due to the way NTP server works probably MT devels considered this feature of low importance/priority.

He didn't mention if he needs the NTP package, I stand by my reply until then :P