I dont have access to the syslog where it is broken now that I'm on a different working version, but can goto a broken version to get them again if this helps. While it was broken, tried several NTP servers (google, Nist, apple)... After all those failed, started going back versions to find a working one.
Originally found this issue reported on redit while looking for a fix:
Joined: 18 Mar 2014 Posts: 6391 Location: Netherlands
Posted: Mon Jun 08, 2020 14:09 Post subject:
That poster mentions and R6400v1, I have one running usually upgrading when a new build arrives and have never had any problem.
But like I said, ntp works best if you use the built-in time server (so leave it blank).
So it can be something in your specific setup, I have seen some reports, if the router is setup as a bridge and local DNS and Gateway were not setup correctly and the WAN was not disabled that the router did not get the right time.
Going to latest version, still fails with any user specified server. As you mentioned, it works leaving it blank. Leaving it blank is a work around, but something is actually broken if you cannot specify an NTP server. Will leave on this version for now if you would like additional debug info.
===Using build 43334 with NTP server: time.google.com (same result with other user specified servers)
Dec 31 19:01:03 apu-3200 daemon.err ntpclient: Failed resolving address to hostname time.google.com: Try again
Dec 31 19:01:03 apu-3200 daemon.err ntpclient: Failed resolving server time.google.com: Network is down
Dec 31 19:01:03 apu-3200 daemon.err process_monitor: cyclic NTP Update failed (servers time.google.com)
Dec 31 19:01:03 apu-3200 daemon.err process_monitor: Last update failed, we need to re-update after 30 seconds
===Using build 43334 with NTP server: <blank>
Dec 31 19:06:35 apu-3200 daemon.notice ntpclient: Network up, resolved address to hostname 184.108.40.206
Dec 31 19:06:35 apu-3200 daemon.debug ntpclient: Connecting to 220.127.116.11 [18.104.22.168] ...
Jun 8 10:39:22 apu-3200 daemon.info ntpclient: Time set from 22.214.171.124 [126.96.36.199].
Seems this may be more specific to 3200ACM, as others have reported the issue with that model specifically. What additional information would you like to see to dig further?
With no server specified, I'm still seeing these occasionally. Shortly thereafter it starts working. There are other machines behind this router which also use the same NTP servers and those are working without issue.
Jun 8 12:39:31 apu-3200 daemon.err ntpclient: Failed resolving address to hostname 2.pool.ntp.org: Try again
Jun 8 12:39:31 apu-3200 daemon.err ntpclient: Failed resolving server 2.pool.ntp.org: Network is down
Jun 8 12:39:31 apu-3200 daemon.notice ntpclient: Network up, resolved address to hostname 188.8.131.52
Jun 8 12:39:31 apu-3200 daemon.debug ntpclient: Connecting to 184.108.40.206 [220.127.116.11] ...
Jun 8 12:39:30 apu-3200 daemon.info ntpclient: Time set from 18.104.22.168 [22.214.171.124].
Jun 8 12:39:30 apu-3200 daemon.info process_monitor: cyclic NTP Update success (servers 2.pool.ntp.org 126.96.36.199 188.8.131.52)
Joined: 08 May 2018 Posts: 7258 Location: Texas, USA
Posted: Mon Jun 08, 2020 17:40 Post subject:
The builds you are initially referring to might be during dnsmasq updates that may have resulted in DNS resolution issues - and DNS resolution issues aren't necessarily that something is "broken", per se. I've had those messages before, but NTP wasn't "broken". The situation I am referring to on my R9000 is the time is completely wrong, like it half-ass syncs to an 18:00 time, no matter what time of day or night it is.
Joined: 24 Feb 2013 Posts: 1516 Location: Belgrade
Posted: Tue Jun 09, 2020 6:22 Post subject:
Failed resolving address to hostname
as you can see by yourself, your problem is not NTP but DNS...
I strongly suggest you to use IP adress of NTP servers instead of hostname... problem can occur if your DNS server needs correct time because of lets say certificates, and it is not up and running and your ntp client tries first to resolves hostname... but your NS is not up...
Thank you for the investigation, recommendations, and clarification. Enabled dnsmasq and am able to specify a time server accordingly without any issues.
Admittedly only come here when experiencing a problem, curious if there is a sticky for recommended best practices for setup/config in one place? found this one, but asking if there is a more comprehensive set...