NIST URLs for leap-seconds.list in leapseconds.awk
On Jan 10, 2024, at 12:20 PM, PoolMUC via tz <tz@iana.org> wrote:
After recent updates to leapseconds.awk to include IERS as a source for leap-seconds.list, one URL given for the file at NIST still is ftp://ftp.nist.gov/pub/time/leap-seconds.list:
print "# This file is generated automatically from the data in the public-domain" print "# NIST/IERS format leap-seconds.list file, which can be copied from" print "# <https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list>" print "# or, in a variant with different comments, from" print "# <ftp://ftp.nist.gov/pub/time/leap-seconds.list>" print "# or <ftp://ftp.boulder.nist.gov/pub/time/leap-seconds.list>."
However, at least for me, and at this time, the hostname ftp.nist.gov <http://ftp.nist.gov/> does not resolve. ftp.boulder.nist.gov <http://ftp.boulder.nist.gov/> does resolve.
Seeing the same thing here (Washington DC): *** snip snip *** [fredg@elastigirl ~]$ dig @gea.nist.gov ftp.nist.gov ; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.15 <<>> @gea.nist.gov ftp.nist.gov ; (2 servers found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 6750 ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; WARNING: recursion requested but not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1220 ;; QUESTION SECTION: ;ftp.nist.gov. IN A ;; AUTHORITY SECTION: nist.gov. 300 IN SOA gea.nist.gov. netops.nist.gov. 3435747 10800 1080 2419200 300 ;; Query time: 5 msec ;; SERVER: 129.6.92.10#53(129.6.92.10) ;; WHEN: Wed Jan 10 12:31:43 EST 2024 ;; MSG SIZE rcvd: 88 *** snip snip *** Cheers! |---------------------------------------------------------------------| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |---------------------------------------------------------------------| | A room without books is like a body without a soul. | | | | -- Cicero | |---------------------------------------------------------------------|
On 2024-01-10 09:20, PoolMUC via tz wrote:
However, at least for me, and at this time, the hostname ftp.nist.gov does not resolve. ftp.boulder.nist.gov does resolve.
Thanks for reporting that. ftp.nist.gov has been flaky for some time, and I have the feeling that NIST hasn't wanted us to use it. Perhaps their FTP servers were overloaded, perhaps they're trying to discourage the use of FTP due to its security issues (but then why use FTP with Boulder?), and perhaps they just want to get out of the leap second business and let IERS deal with it. Since the boulder URI is more reliable let's mention only it for the NIST URIs. Proposed patch attached.
participants (3)
-
Fred Gleason -
Paul Eggert -
PoolMUC@web.de