Page 1 of 1
why doesn't NTP client accept named domains?
Posted: Sat Jan 18, 2014 10:13 am
by hendry
I don't understand why WebFig calls this SNTP IIUC.
Also why can't I use 0.asia.pool.ntp.org instead of IPs? Or am I missing something?
Re: why doesn't NTP client accept named domains?
Posted: Tue Jan 21, 2014 6:41 pm
by plisken
I have a suspicion that your router board is not connected to your ISP while you ran the configuration.
The router cannot perform DNS translations in itself
Re: why doesn't NTP client accept named domains?
Posted: Wed Jan 22, 2014 5:22 am
by hendry
My router has DNS. It seems that it won't accept a domain name as an argument. Bit crap.
Re: why doesn't NTP client accept named domains?
Posted: Wed Jan 22, 2014 7:20 pm
by plisken
Ping to 0.asia.pool.ntp.org and you know the IP-address
Re: why doesn't NTP client accept named domains?
Posted: Wed Jan 22, 2014 8:54 pm
by honzam
Ping to 0.asia.pool.ntp.org and you know the IP-address
It works, but this is workaround
Re: why doesn't NTP client accept named domains?
Posted: Thu Jan 23, 2014 8:04 pm
by Sob
Don't lose hope. They only recently added this "advanced feature" to VPN clients, including OpenVPN they hate very much. For NTP, which AFAIK they don't hate, so that should be an advantage, it should eventually happen too.
Re: why doesn't NTP client accept named domains?
Posted: Fri Jan 24, 2014 12:11 am
by skot
Use the [:resolve] function to set NTP... like this:
/system ntp client set primary-ntp=[:resolve 0.asia.pool.ntp.org]
Re: why doesn't NTP client accept named domains?
Posted: Sun Jun 01, 2014 6:35 pm
by mgreant
I 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...
Re: why doesn't NTP client accept named domains?
Posted: Mon Jun 02, 2014 7:51 pm
by payday
Also why can't I use 0.asia.pool.ntp.org instead of IPs
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: most RouterBoards don't have clocks build in, so SNTP client could be enabled by default with
0.pool.ntp.org and
1.pool.ntp.org set as default servers. So simple and practical.
Re: why doesn't NTP client accept named domains?
Posted: Tue Jun 03, 2014 9:00 pm
by skot
I 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...
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#p415437
Re: why doesn't NTP client accept named domains?
Posted: Mon Jun 16, 2014 11:20 pm
by payday
I just found that SNTP Client in Winbox accepts domain names and resolves them to IP addresses. I think it wasn't possible in v 6.8 (when I last tried that
).