NTP server not sync and showing status waiting

NTP server not sync and showing status waiting. What is the issue?


> system/ntp/client/export         
# 2024-06-21 14:09:44 by RouterOS 7.15.1
# software id = **ELIDED**
#
# model = CCR1036-8G-2S+
# serial number = **ELIDED**
/system ntp client
set enabled=yes
/system ntp client servers
add address=0.asia.pool.ntp.org
add address=1.asia.pool.ntp.org
add address=2.asia.pool.ntp.org
add address=3.asia.pool.ntp.org
add address=192.46.215.60
add address=129.159.140.221
add address=185.18.207.158

Without the rest of the /export output, we’re going to have to speculate somewhat. Your issue might have to do with “/ip/firewall/filter” rules, for instance.

Short of that, have you tried the several solutions given in this long thread?

thanks!

Observing dns resolving issue on that router and found dns port forwarding rules.

/ip firewall nat
add action=dst-nat chain=dstnat comment=8.8.8.8 dst-port=53 protocol=udp src-address=10.20.0.0/16 to-addresses=8.8.8.8 to-ports=53
add action=dst-nat chain=dstnat dst-port=53 protocol=tcp src-address=10.20.0.0/16 to-addresses=8.8.8.8 to-ports=53

Your NTP configuration relies on DNS working properly due to the use of address pools.

What happens when you say…


/tool/ping 0.asia.pool.ntp.org

By the way, the whole point of NTP pools is that you don’t have to list many addresses. I would pare your local NTP configuration back to a single pool address:


/system ntp client servers
add address=asia.pool.ntp.org

By not restricting it to one of the numbered sub-pools, I’m saying “anything in Asia is fine”. You might want to restrict it to something more local like in.asia.pool.ntp.org since your profile name suggests you might be in India.

There aren’t many good reasons to get clever with this. Let the pool managers do their job; spend your creative time on something more valuable to your organization than micromanaging pool addresses.

I tried adding multiple NTP servers; only asia.pool.ntp.org resolved my synchronization issue.