NTP Servers, tick and tock

[RiDDLeRThC]

Figured this will fit in well here.

Anyone else having an issue hitting these servers? Were they taken down for some reason?

tick.usno.navy.mil
tock.usno.navy.mil

 

[RocketTech]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\chris>ping tick.usno.navy.mil

Pinging tick.usno.navy.mil [67.215.65.132] with 32 bytes of data:
Reply from 67.215.65.132: bytes=32 time=50ms TTL=53
Reply from 67.215.65.132: bytes=32 time=53ms TTL=53
Reply from 67.215.65.132: bytes=32 time=48ms TTL=53
Reply from 67.215.65.132: bytes=32 time=48ms TTL=53

Ping statistics for 67.215.65.132:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 53ms, Average = 49ms

C:\Users\chris>ping tock.usno.navy.mil

Pinging tock.usno.navy.mil [67.215.65.132] with 32 bytes of data:
Reply from 67.215.65.132: bytes=32 time=45ms TTL=53
Reply from 67.215.65.132: bytes=32 time=46ms TTL=53
Reply from 67.215.65.132: bytes=32 time=45ms TTL=53
Reply from 67.215.65.132: bytes=32 time=46ms TTL=53

Ping statistics for 67.215.65.132:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 46ms, Average = 45ms

C:\Users\chris>

 

[p3n]

Ping doesn't use the NTP protocol Chris.

works here.

 

[Red Squirrel]

Yep seems it may be down (the ntp service)

root@falcon:~# ntpdate time.nist.gov
21 Aug 18:05:41 ntpdate[18715]: adjust time server 207.200.81.113 offset 0.004714 sec
root@falcon:~# ntpdate tick.usno.navy.mil
21 Aug 18:05:54 ntpdate[18716]: no server suitable for synchronization found
root@falcon:~# ntpdate  tock.usno.navy.mil 
21 Aug 18:06:10 ntpdate[18717]: no server suitable for synchronization found
root@falcon:~#

 

[RiDDLeRThC]

Chris - those are the wrong IPs. reverse lookup points to opendns for the IP you resolved.

 

[RiDDLeRThC]

They seem to be having some kind of DNS issues.

I cannot resolve with google's dns servers and even using http://mxtoolbox.com/SuperTool.aspx they sometimes resolve and then sometimes dont.

 

[RocketTech]

There you go. If you are deperate for ntp service, try pool.ntp.org- I typically use pool0.ntp.org, never failed me.

 

[klank]

Or you could use....

4.2.2.2
4.2.2.3
4.2.2.4
4.2.2.5
4.2.2.6
4.2.2.7

 

[hawk82]

0.us.pool.ntp.org and 1.us.pool.ntp.org
I don't believe I've ever seen a failure using those servers. Works like a charm.
Consider donating ntp servers to cause if you can.

 

[RiDDLeRThC]

I've always used tick and tock but maybe its time for a change.

even the 4.2.2.x servers weren't resolving it earlier for me.

 

[D-EJ915]

US NTP pool or bust.

 

[RocketTech]

I looked into it once a while ago, so correct me if I'm wrong, but 0.pool.ntp.org will assign a pool of available low-latency servers.pool.us.ntp.org (or pool.locale.ntp.org) will supply servers of the specifed reported locale, regardless of distance, latency, or whatnot.

 

[Red Squirrel]

I've always used tick and tock but maybe its time for a change.

even the 4.2.2.x servers weren't resolving it earlier for me.

Pun intended?

 

[-Dragon-]

it's locale.pool.ntp.org for local pools, I use 0-3.us.pool.ntp.org for mine

http://support.ntp.org/bin/view/Servers/NTPPoolServers