On 2019-07-08 05:16, Tony Finch wrote:
The main problem that I can see is 3 out of the 7 navy.mil DNS servers say that usno.navy.mil does not exist, so it's a matter of luck whether you'll be able to contact it or not.
Chris's suggestion of populating /etc/hosts or your local LDAP server is a useful workaround: 199.211.133.5 charon.usno.navy.mil charon.nofs.navy.mil 192.68.148.66 charon.nofs.navy.mil # Naval Oceanographic Portal DNS server 192.68.148.80 toshi.nofs.navy.mil # IERS rapid earth orientation data 199.211.133.23 maia.usno.navy.mil # IERS rapid earth orientation data 199.211.133.239 tycho.usno.navy.mil # IERS rapid earth orientation data 199.211.133.93 aa.usno.navy.mil # astronomical data 199.211.133.90 www.usno.navy.mil # Naval Oceanographic Portal 204.34.198.40 tick.usnogps.navy.mil # NTP, USNO AMC, Schriever AFB, Co Springs, CO, US 204.34.198.41 tock.usnogps.navy.mil # NTP, USNO AMC, Schriever AFB, Co Springs, CO, US 192.5.41.40 tick.usno.navy.mil # NTP, USNO PMC, Washington, DC, US 192.5.41.41 tock.usno.navy.mil # NTP, USNO PMC, Washington, DC, US 192.5.41.209 ntp2.usno.navy.mil # NTP, USNO PMC, Washington, DC, US 140.31.199.22 time.mhpcc.hpc.mil # NTP, AFRL, HPCC, Maui, HI, US 204.123.2.72 usno.hpl.hp.com # NTP, HP Labs, Palo Alto, CA, US -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised.