SNTP + NTP Package issues

Hi Guys,

I am looking for ways to use DNS to update time inside my network.

I installed the NTP package and found that I cant use DNS for an update source without running scripts to do that task manually. That is fine, but if someone that isnt that familiar with MT needs to make an adjustment and im not availalble to assist then this becomes a poor solution. Therefore I am investigating alternative options.

I tried the following,

R1 Installed the NTP package, set cloud update from MikroTik and set NTP server to unicast
R1 - /system ntp client set enabled=no
R1 - /ip cloud set update-time=yes
R1 - /system ntp server set enabled=yes broadcast=no multicast=no manycast=no

R2 - Set the SNTP client to check with R1
R2 - /system ntp client set enabled=yes primary-ntp=R1-IP secondary-ntp=R1-IP

I am finding two issues that I don’t understand, they may be related to the same issue.

  1. It takes a good 10-15mins before R2 gets the time from R1. It keeps pumping messages into the logs saying “Ignoring Receiving NTP packet 48bytes”
  2. In Winbox → System → SNTP Client under “last bad packet from” it states the reason as “server-not-synchronised”.

Should this setup work? Can anyone provide insight / answers to my questions 1 and 2?

Thanks guys.

NTP server on R1 needs self NTP client configured and synchronized to external NTP reference servers before it can serve precise time to ckienrs (R2).

Cloud function update-time is by no means adequate and is no substitution. It should be disabled if NTP client is running.

There’s a cloud of public NTP servers, addresses resolvable as .pool.ntp.org where is 2-letter country code.