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:
http://support.ntp.org/bin/view/Servers/PublicTimeServer000270
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:
http://support.ntp.org/bin/view/Servers/PublicTimeServer000453
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
Sincerely,
-Jeff
On 02/20/2014 12:52 PM, Brian Chee wrote:
Can't answer that, but Alan Whinery is behind it and it's providing NTP for
UHM ITS facilities. Have you thought of ntp.pool.org?
/brian chee
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 produced a
UH server. Is this particular server _reliably_ deployed? I.e., will it
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 might
not check for several years.
Thanks Brian,
-Jeff
On 02/20/2014 12:44 PM, Brian Chee wrote:
ntp1.hawaii.edu canonical name = ntproundtop.hawaii.edu.
Name: ntproundtop.hawaii.edu
Address: 128.171.235.62
On Thu, Feb 20, 2014 at 2:40 PM, Jeff Mings <je...@lava.net> wrote:
Hi All!
After the new NTP DOS vulnerability, a lot of NTP servers are
changing
their operation.
I have used the navy's atomic clock at tick.mhpcc.hpc.mil for quite
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
have
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
server
or pool of them that won't be overwhelmed/useless like the Microsoft NTP
servers. So far, using 0.us.pool.ntp.org looks like a solid choice for
long-term reliability, but nist1-la.ustiming.org yields better ping
times, and the NIST has a nice status page at http://tf.nist.gov/tf-cgi/
servers.cgi for checking service.
Any better suggestions?
Thanks,
-Jeff
_______________________________________________
LUAU@lists.freesoftwarehawaii.org mailing list
http://lists.freesoftwarehawaii.org/listinfo.cgi/luau-
freesoftwarehawaii.org
_______________________________________________
LUAU@lists.freesoftwarehawaii.org mailing list
http://lists.freesoftwarehawaii.org/listinfo.cgi/luau-
freesoftwarehawaii.org
_______________________________________________
LUAU@lists.freesoftwarehawaii.org mailing list
http://lists.freesoftwarehawaii.org/listinfo.cgi/luau-freesoftwarehawaii.org
