On Mon, Apr 18, 2016 at 01:16:21PM +0200, Dag-Erling Smørgrav wrote: > I just tested this (ntpdate -d time.nist.gov) from several locations and > noticed an interesting pattern:
It looks like only the time-*.nist.gov servers (with 129.6.15.* addresses) have this problem. The other servers to which time.nist.gov resolves seem ok. Here are offsets and delays from my last measurements (as seen over IPv4 from Czech republic): 198.60.73.8 (?) 0.000 0.168 24.56.178.140 (host-24-56-178-140.beyondbb.com) 0.004 0.159 128.138.141.172 (utcnist2.colorado.edu) -0.004 0.152 132.163.4.101 (time-a.timefreq.bldrdoc.gov) -0.003 0.150 132.163.4.102 (time-b.timefreq.bldrdoc.gov) -0.004 0.154 129.6.15.28 (time-a.nist.gov) 0.029 0.178 129.6.15.29 (time-b.nist.gov) 0.031 0.180 129.6.15.30 (time-c.nist.gov) 0.028 0.179 129.6.15.27 (time-d.nist.gov) 0.027 0.178 -- Miroslav Lichvar _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
