Jeff Mings wrote:
Yes, Brian, the first NTP pool address I listed is from ntp.pool.org,
but it may be farther away /slower depending upon which server in the
pool answers the query.
Al, I always appreciate your suggestions, but I noticed that the
NASA NTP server is really not supposed to be publicly available:
Strangely, the ntp.hawaii.edu server doesn't have a stratum rating, and
I know that a few years ago, it oddly jumped forward to the year 2030:
In terms of ping time and likely long-term reliability, the NIST
server in LA is looking like my best option : nist1-la.ustiming.org
I got the nasa, columbia servers from some freeBSD list in a published
form. I think Mike Lucas lists some reliable ntp servers for regions in
The pool servers are part of the problem since the IP s are from all
over. One of the guys in England tells me and shouldnt be trusted if you
need real accuracy.
On 02/20/2014 12:52 PM, Brian Chee wrote:
Can't answer that, but Alan Whinery is behind it and it's providing
UHM ITS facilities. Have you thought of ntp.pool.org?
On Thu, Feb 20, 2014 at 2:48 PM, Jeff Mings <je...@lava.net> wrote:
That was fast! You are SO on it, Mr. Chee! :D
Since you work with the UH IT dept., I'm not surprised you
UH server. Is this particular server _reliably_ deployed? I.e.,
likely be consistently available 5 years from now? There are a lot of
devices, like phones, that I need to set a good NTP server on that I
not check for several years.
On 02/20/2014 12:44 PM, Brian Chee wrote:
ntp1.hawaii.edu canonical name = ntproundtop.hawaii.edu.
On Thu, Feb 20, 2014 at 2:40 PM, Jeff Mings <je...@lava.net> wrote:
After the new NTP DOS vulnerability, a lot of NTP servers are
I have used the navy's atomic clock at tick.mhpcc.hpc.mil for
some time, but it appears that they may be reducing access to it now.
Many of my clients use RoadRunner locally, which doesn't seem to
a publicly-listed NTP server in this area. I could use the pool from
CentOS, or even the one from Apple, but I want to make sure I use a
or pool of them that won't be overwhelmed/useless like the
servers. So far, using 0.us.pool.ntp.org looks like a solid
long-term reliability, but nist1-la.ustiming.org yields better ping
times, and the NIST has a nice status page at
servers.cgi for checking service.
Any better suggestions?
~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740
+ http://hawaiidakine.com + http://freebsdinfo.org +
+ http://aloha50.net - Supporting - FreeBSD 7.2 - 8.0 - 9* +
< email: n...@hdk5.net >
"All that's really worth doing is what we do for others."- Lewis Carrol
LUAU@lists.freesoftwarehawaii.org mailing list