It works, but this is workaroundPing to 0.asia.pool.ntp.org and you know the IP-address
/system ntp client set primary-ntp=[:resolve 0.asia.pool.ntp.org]
Because programmers at MikroTik are lazy . This functionality is so simple to implement and was so many times requested that there is no other explanation for this.Also why can't I use 0.asia.pool.ntp.org instead of IPs
The easiest solution is to use the scheduler to update the NTP servers every X minutes. Something like this: http://forum.mikrotik.com/viewtopic.php ... 06#p415437I think this doesn't solve the problem in the long term.
The 0.asia.pool.nts.org link refers to a pool of IP's of NTS servers. This means if the IP of a NTS server goes offline, the domain (0.asia....) will automatically link to the IP address of another NTS server.
The IP of the domain is dynamic.
But I'm not sure...