I'm still getting a 404. I am using a Windstream backbone, is this maybe path/server specific. Here is a dig. dig tf.nist.gov ; <<>> DiG 9.9.5-3-Ubuntu <<>> tf.nist.gov ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46860 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 2, ADDITIONAL: 2 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;tf.nist.gov. IN A ;; ANSWER SECTION: tf.nist.gov. 1784 IN CNAME tf.boulder.nist.gov. tf.boulder.nist.gov. 86384 IN CNAME ftp.boulder.nist.gov. ftp.boulder.nist.gov. 86384 IN A 132.163.4.45 ;; AUTHORITY SECTION: boulder.nist.gov. 1485 IN NS dns-y.boulder.nist.gov. boulder.nist.gov. 1485 IN NS gdnsea.nist.gov. ;; ADDITIONAL SECTION: dns-y.boulder.nist.gov. 1485 IN AAAA 2610:20:6b01:4::10 ;; Query time: 6 msec ;; SERVER: 68.70.255.9#53(68.70.255.9) ;; WHEN: Wed Oct 29 13:25:15 EDT 2014 ;; MSG SIZE rcvd: 168 On Wed, Oct 29, 2014 at 1:25 PM, Brian Christopher Raaen < mailing-lists@brianraaen.com> wrote:
I'm still getting a 404. I am using a Windstream backbone, is this maybe path/server specific. Here is a dig.
dig tf.nist.gov
; <<>> DiG 9.9.5-3-Ubuntu <<>> tf.nist.gov ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46860 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 2, ADDITIONAL: 2
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;tf.nist.gov. IN A
;; ANSWER SECTION: tf.nist.gov. 1784 IN CNAME tf.boulder.nist.gov. tf.boulder.nist.gov. 86384 IN CNAME ftp.boulder.nist.gov. ftp.boulder.nist.gov. 86384 IN A 132.163.4.45
;; AUTHORITY SECTION: boulder.nist.gov. 1485 IN NS dns-y.boulder.nist.gov. boulder.nist.gov. 1485 IN NS gdnsea.nist.gov.
;; ADDITIONAL SECTION: dns-y.boulder.nist.gov. 1485 IN AAAA 2610:20:6b01:4::10
;; Query time: 6 msec ;; SERVER: 68.70.255.9#53(68.70.255.9) ;; WHEN: Wed Oct 29 13:25:15 EDT 2014 ;; MSG SIZE rcvd: 168
On Wed, Oct 29, 2014 at 1:22 PM, Chris Patsalou < chrispatsalou@googlemail.com> wrote:
Appears up from here (London, UK)
*NameIP AddressLocationStatusnist1-pa.ustiming.org <http://nist1-pa.ustiming.org>206.246.122.250Hatfield, PAAll services availabletime-a.nist.gov <http://time-a.nist.gov>129.6.15.28NIST, Gaithersburg, MarylandAll services busy, not recommendedtime-b.nist.gov <http://time-b.nist.gov>129.6.15.29NIST, Gaithersburg, MarylandAll services busy, not recommendedtime-c.nist.gov <http://time-c.nist.gov>129.6.15.30NIST, Gaithersburg, MarylandAll services availabletime-d.nist.gov <http://time-d.nist.gov>2610:20:6F15:15::27NIST, Gaithersburg, MarylandAll services via IPV6nist1-macon.macon.ga.us <http://nist1-macon.macon.ga.us>98.175.203.200Macon, GeorgiaAll services availablewolfnisttime.com <http://wolfnisttime.com>207.223.123.18Birmingham, AlabamaAll services availablenist.time.nosc.us <http://nist.time.nosc.us>96.226.242.9Carrollton, TexasAll services availablenist.expertsmi.com <http://nist.expertsmi.com>50.245.103.198Monroe, Michigantemporary failurenist.netservicesgroup.com <http://nist.netservicesgroup.com>64.113.32.5Southfield, MichiganAll services availablenisttime.carsoncity.k12.mi.us <http://nisttime.carsoncity.k12.mi.us>66.219.116.140Carson City, MichiganAll services availablenist1-lnk.binary.net <http://nist1-lnk.binary.net>216.229.0.179Lincoln, NebraskaAll services availablewwv.nist.gov <http://wwv.nist.gov>24.56.178.140WWV, Fort Collins, ColoradoAll services availabletime-a.timefreq.bldrdoc.gov <http://time-a.timefreq.bldrdoc.gov>132.163.4.101NIST, Boulder, Coloradontp ok; time, daytime busytime-b.timefreq.bldrdoc.gov <http://time-b.timefreq.bldrdoc.gov>132.163.4.102NIST, Boulder, ColoradoAll services busytime-c.timefreq.bldrdoc.gov <http://time-c.timefreq.bldrdoc.gov>132.163.4.103NIST, Boulder, Coloradontp ok; time, daytime busytime.nist.gov <http://time.nist.gov>global address for all serversMultiple locationsAll services availableutcnist.colorado.edu <http://utcnist.colorado.edu>128.138.140.44University of Colorado, BoulderAll services availableutcnist2.colorado.edu <http://utcnist2.colorado.edu>128.138.141.172University of Colorado, BoulderAll services availablentp-nist.ldsbc.edu <http://ntp-nist.ldsbc.edu>198.60.73.8LDSBC, Salt Lake City, UtahAll services availablenist1-lv.ustiming.org <http://nist1-lv.ustiming.org>64.250.229.100Las Vegas, NevadaAll services availabletime-nw.nist.gov <http://time-nw.nist.gov>131.107.13.100Microsoft, Redmond, WashingtonAll services very busynist-time-server.eoni.com <http://nist-time-server.eoni.com>216.228.192.69La Grande, OregonAll services availableHope this helps?*
On 29 October 2014 17:14, Brian Christopher Raaen < mailing-lists@brianraaen.com> wrote:
The list of NIST NTP servers is down for me, is anyone else seeing this? I'm getting a 404 error http://tf.nist.gov/tf-cgi/servers.cgi
-- Brian Christopher Raaen Network Architect Zcorum
-- Brian Christopher Raaen Network Architect Zcorum
-- Brian Christopher Raaen Network Architect Zcorum
Seems to be working over IPv4, not over IPv6. $ curl -6 http://tf.nist.gov/tf-cgi/servers.cgi 2>/dev/null | head -5 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> $ curl -4 http://tf.nist.gov/tf-cgi/servers.cgi 2>/dev/null | head -5 <html> <head> <title>NIST Internet Time Service</title> <meta http-equiv="content-type" content="text/html;charset=iso-8859-1"> <script language="JavaScript" id="_fed_an_js_tag" src="/js/federated-analytics.all.min.js?agency=NIST&subagency=tf&pua= UA-42404149-6&yt=true"></script>
Am 29.10.2014 um 18:26 schrieb Brian Christopher Raaen <mailing-lists@brianraaen.com>:
I'm still getting a 404. I am using a Windstream backbone, is this maybe path/server specific. Here is a dig.
dig tf.nist.gov
-- Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
That is interesting as the computer I am using is on dual-stack, and I am probably using IPv6 to reach it. On Wed, Oct 29, 2014 at 1:56 PM, Stefan Bethke <stb@lassitu.de> wrote:
Seems to be working over IPv4, not over IPv6.
$ curl -6 http://tf.nist.gov/tf-cgi/servers.cgi 2>/dev/null | head -5 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> $ curl -4 http://tf.nist.gov/tf-cgi/servers.cgi 2>/dev/null | head -5 <html> <head> <title>NIST Internet Time Service</title> <meta http-equiv="content-type" content="text/html;charset=iso-8859-1"> <script language="JavaScript" id="_fed_an_js_tag" src="/js/federated-analytics.all.min.js?agency=NIST&subagency=tf&pua= UA-42404149-6&yt=true"></script>
Am 29.10.2014 um 18:26 schrieb Brian Christopher Raaen < mailing-lists@brianraaen.com>:
I'm still getting a 404. I am using a Windstream backbone, is this maybe path/server specific. Here is a dig.
dig tf.nist.gov
-- Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
-- Brian Christopher Raaen Network Architect Zcorum
Also getting a 404 over IPv6. You can verify what transport we're using in Firefox using the SixorNot plugin. hth, Doug
On Wed, Oct 29, 2014 at 11:19 AM, Brian Christopher Raaen <mailing-lists@brianraaen.com> wrote:
That is interesting as the computer I am using is on dual-stack, and I am probably using IPv6 to reach it.
"happy eyeballs"
On Wed, Oct 29, 2014 at 1:56 PM, Stefan Bethke <stb@lassitu.de> wrote:
Seems to be working over IPv4, not over IPv6.
$ curl -6 http://tf.nist.gov/tf-cgi/servers.cgi 2>/dev/null | head -5 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> $ curl -4 http://tf.nist.gov/tf-cgi/servers.cgi 2>/dev/null | head -5 <html> <head> <title>NIST Internet Time Service</title> <meta http-equiv="content-type" content="text/html;charset=iso-8859-1"> <script language="JavaScript" id="_fed_an_js_tag" src="/js/federated-analytics.all.min.js?agency=NIST&subagency=tf&pua= UA-42404149-6&yt=true"></script>
Am 29.10.2014 um 18:26 schrieb Brian Christopher Raaen < mailing-lists@brianraaen.com>:
I'm still getting a 404. I am using a Windstream backbone, is this maybe path/server specific. Here is a dig.
dig tf.nist.gov
-- Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
-- Brian Christopher Raaen Network Architect Zcorum
Happy Eyeballs has nothing to do with it. This is a server misconfiguration plain and simple. Doug On 10/29/14 11:30 AM, Christopher Morrow wrote:
On Wed, Oct 29, 2014 at 11:19 AM, Brian Christopher Raaen <mailing-lists@brianraaen.com> wrote:
That is interesting as the computer I am using is on dual-stack, and I am probably using IPv6 to reach it.
"happy eyeballs"
On Wed, Oct 29, 2014 at 1:56 PM, Stefan Bethke <stb@lassitu.de> wrote:
Seems to be working over IPv4, not over IPv6.
$ curl -6 http://tf.nist.gov/tf-cgi/servers.cgi 2>/dev/null | head -5 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> $ curl -4 http://tf.nist.gov/tf-cgi/servers.cgi 2>/dev/null | head -5 <html> <head> <title>NIST Internet Time Service</title> <meta http-equiv="content-type" content="text/html;charset=iso-8859-1"> <script language="JavaScript" id="_fed_an_js_tag" src="/js/federated-analytics.all.min.js?agency=NIST&subagency=tf&pua= UA-42404149-6&yt=true"></script>
Am 29.10.2014 um 18:26 schrieb Brian Christopher Raaen < mailing-lists@brianraaen.com>:
I'm still getting a 404. I am using a Windstream backbone, is this maybe path/server specific. Here is a dig.
dig tf.nist.gov
-- Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
-- Brian Christopher Raaen Network Architect Zcorum
On Wed, Oct 29, 2014 at 11:36 AM, Doug Barton <dougb@dougbarton.us> wrote:
Happy Eyeballs has nothing to do with it. This is a server misconfiguration plain and simple.
I meant that it seems that v4 is broken, but v6 is not. so sure, it's a server thing, but he's seeing different results maybe as a side effect of eyeballs.
Doug
On 10/29/14 11:30 AM, Christopher Morrow wrote:
On Wed, Oct 29, 2014 at 11:19 AM, Brian Christopher Raaen <mailing-lists@brianraaen.com> wrote:
That is interesting as the computer I am using is on dual-stack, and I am probably using IPv6 to reach it.
"happy eyeballs"
On Wed, Oct 29, 2014 at 1:56 PM, Stefan Bethke <stb@lassitu.de> wrote:
Seems to be working over IPv4, not over IPv6.
$ curl -6 http://tf.nist.gov/tf-cgi/servers.cgi 2>/dev/null | head -5 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> $ curl -4 http://tf.nist.gov/tf-cgi/servers.cgi 2>/dev/null | head -5 <html> <head> <title>NIST Internet Time Service</title> <meta http-equiv="content-type" content="text/html;charset=iso-8859-1"> <script language="JavaScript" id="_fed_an_js_tag" src="/js/federated-analytics.all.min.js?agency=NIST&subagency=tf&pua= UA-42404149-6&yt=true"></script>
Am 29.10.2014 um 18:26 schrieb Brian Christopher Raaen <
mailing-lists@brianraaen.com>:
I'm still getting a 404. I am using a Windstream backbone, is this maybe path/server specific. Here is a dig.
dig tf.nist.gov
-- Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
-- Brian Christopher Raaen Network Architect Zcorum
I disabled IPv6 on my machine and was able to pull it up, reenable IPv6 and I start getting 404's. On Wed, Oct 29, 2014 at 3:36 PM, Christopher Morrow <morrowc.lists@gmail.com
wrote:
On Wed, Oct 29, 2014 at 11:36 AM, Doug Barton <dougb@dougbarton.us> wrote:
Happy Eyeballs has nothing to do with it. This is a server misconfiguration plain and simple.
I meant that it seems that v4 is broken, but v6 is not. so sure, it's a server thing, but he's seeing different results maybe as a side effect of eyeballs.
Doug
On 10/29/14 11:30 AM, Christopher Morrow wrote:
On Wed, Oct 29, 2014 at 11:19 AM, Brian Christopher Raaen <mailing-lists@brianraaen.com> wrote:
That is interesting as the computer I am using is on dual-stack, and I
am
probably using IPv6 to reach it.
"happy eyeballs"
On Wed, Oct 29, 2014 at 1:56 PM, Stefan Bethke <stb@lassitu.de> wrote:
Seems to be working over IPv4, not over IPv6.
$ curl -6 http://tf.nist.gov/tf-cgi/servers.cgi 2>/dev/null | head -5 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> $ curl -4 http://tf.nist.gov/tf-cgi/servers.cgi 2>/dev/null | head -5 <html> <head> <title>NIST Internet Time Service</title> <meta http-equiv="content-type" content="text/html;charset=iso-8859-1"> <script language="JavaScript" id="_fed_an_js_tag" src="/js/federated-analytics.all.min.js?agency=NIST&subagency=tf&pua= UA-42404149-6&yt=true"></script>
Am 29.10.2014 um 18:26 schrieb Brian Christopher Raaen <
mailing-lists@brianraaen.com>:
I'm still getting a 404. I am using a Windstream backbone, is this maybe path/server specific. Here is a dig.
dig tf.nist.gov
-- Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
-- Brian Christopher Raaen Network Architect Zcorum
-- Brian Christopher Raaen Network Architect Zcorum
On 10/29/14 12:36 PM, Christopher Morrow wrote:
On Wed, Oct 29, 2014 at 11:36 AM, Doug Barton <dougb@dougbarton.us> wrote:
Happy Eyeballs has nothing to do with it. This is a server misconfiguration plain and simple.
I meant that it seems that v4 is broken, but v6 is not.
Other way around.
Still acting up for me this morning. On Wed, Oct 29, 2014 at 4:05 PM, Doug Barton <dougb@dougbarton.us> wrote:
On 10/29/14 12:36 PM, Christopher Morrow wrote:
On Wed, Oct 29, 2014 at 11:36 AM, Doug Barton <dougb@dougbarton.us> wrote:
Happy Eyeballs has nothing to do with it. This is a server misconfiguration plain and simple.
I meant that it seems that v4 is broken, but v6 is not.
Other way around.
-- Brian Christopher Raaen Network Architect Zcorum
It is now working over IPv6 On Thu, Oct 30, 2014 at 10:09 AM, Brian Christopher Raaen < mailing-lists@brianraaen.com> wrote:
Still acting up for me this morning.
On Wed, Oct 29, 2014 at 4:05 PM, Doug Barton <dougb@dougbarton.us> wrote:
On 10/29/14 12:36 PM, Christopher Morrow wrote:
On Wed, Oct 29, 2014 at 11:36 AM, Doug Barton <dougb@dougbarton.us> wrote:
Happy Eyeballs has nothing to do with it. This is a server misconfiguration plain and simple.
I meant that it seems that v4 is broken, but v6 is not.
Other way around.
-- Brian Christopher Raaen Network Architect Zcorum
-- Brian Christopher Raaen Network Architect Zcorum
Either is alcatel-lucent.com for the past 2 days I noticed. Ipv6 version of their site broken. On Oct 30, 2014 1:18 PM, "Brian Christopher Raaen" < mailing-lists@brianraaen.com> wrote:
It is now working over IPv6
On Thu, Oct 30, 2014 at 10:09 AM, Brian Christopher Raaen < mailing-lists@brianraaen.com> wrote:
Still acting up for me this morning.
On Wed, Oct 29, 2014 at 4:05 PM, Doug Barton <dougb@dougbarton.us> wrote:
On 10/29/14 12:36 PM, Christopher Morrow wrote:
On Wed, Oct 29, 2014 at 11:36 AM, Doug Barton <dougb@dougbarton.us> wrote:
Happy Eyeballs has nothing to do with it. This is a server misconfiguration plain and simple.
I meant that it seems that v4 is broken, but v6 is not.
Other way around.
-- Brian Christopher Raaen Network Architect Zcorum
-- Brian Christopher Raaen Network Architect Zcorum
IPv6 is production. Report the problem. In message <CA+M5dWaR8GvpQZ6EC_wWv5nmz0v0_zmEipUQ15q5bvpR=Ytw=A@mail.gmail.com> , Javier J writes:
Either is alcatel-lucent.com for the past 2 days I noticed. Ipv6 version of their site broken. On Oct 30, 2014 1:18 PM, "Brian Christopher Raaen" < mailing-lists@brianraaen.com> wrote:
It is now working over IPv6
On Thu, Oct 30, 2014 at 10:09 AM, Brian Christopher Raaen < mailing-lists@brianraaen.com> wrote:
Still acting up for me this morning.
On Wed, Oct 29, 2014 at 4:05 PM, Doug Barton <dougb@dougbarton.us> wrote:
On 10/29/14 12:36 PM, Christopher Morrow wrote:
On Wed, Oct 29, 2014 at 11:36 AM, Doug Barton <dougb@dougbarton.us> wrote:
Happy Eyeballs has nothing to do with it. This is a server misconfiguration plain and simple.
I meant that it seems that v4 is broken, but v6 is not.
Other way around.
-- Brian Christopher Raaen Network Architect Zcorum
-- Brian Christopher Raaen Network Architect Zcorum
-- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org
On 10/30/2014 06:27 PM, Mark Andrews wrote:
IPv6 is production. Report the problem.
Sorry for reporting it here, but there seems to be more than one problem (the link resulting from clicking on "nist time". I get the nist front page fine on v6, then click on the time link and get a 404 looking for a strange url: "hxxp://time.gov/HTML5" (which could be fine but does look a little strange.) -- Pete
In message <5452D146.4080307@altadena.net>, Pete Carah writes:
On 10/30/2014 06:27 PM, Mark Andrews wrote:
IPv6 is production. Report the problem.
Sorry for reporting it here, but there seems to be more than one problem (the link resulting from clicking on "nist time".
What does reporting a 404 to nanog do? The network to them is UP. Since the front page is up and actually has a address for reporting web problems I would expect that you would report the problem there (I've cc'd the address). If the front page wasn't up you should do a whois lookup and use those contact details except this a .gov domain where whois is a farce. So you also need to contact your federal representative and complain about that. Nist can put contact details on their web page: Public Inquiries Unit NIST, 100 Bureau Drive, Stop 1070, Gaithersburg, MD 20899-1070 Email: inquiries@nist.gov Phone: (301) 975-NIST (6478) or Federal Relay Service (800) 877-8339 (TTY) But the whois give this farcical response: % DOTGOV WHOIS Server ready Domain Name: NIST.GOV Status: ACTIVE
Last update of whois database: 2014-10-31T00:16:27Z <<< Please be advised that this whois server only contains information pertaining to the .GOV domain. For information for other domains please use the whois server at RS.INTERNIC.NET.
I get the nist front page fine on v6, then click on the time link and get a 404 looking for a strange url: "hxxp://time.gov/HTML5" (which could be fine but does look a little strange.)
-- Pete
-- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org
participants (7)
-
Brian Christopher Raaen -
Christopher Morrow -
Doug Barton -
Javier J -
Mark Andrews -
Pete Carah -
Stefan Bethke