Warren is on the right track. More specifically, there are seven authoritative name servers for navy.mil. Three of them respond properly for usno.navy.mil:
$ dig @ns.jtfgno.mil. usno.navy.mil soa +short psyche.usno.navy.mil. hostmaster.usno.navy.mil. 201709123 3600 1800 2147483647 3600 $ dig @uforiftr02.csd.disa.mil. usno.navy.mil soa +short psyche.usno.navy.mil. hostmaster.usno.navy.mil. 201709123 3600 1800 2147483647 3600 $ dig @updciftr02.csd.disa.mil. usno.navy.mil soa +short psyche.usno.navy.mil. hostmaster.usno.navy.mil. 201709123 3600 1800 2147483647 3600 Four of the authoritative name servers for navy.mil respond with NXDOMAIN for usno.navy.mil: $ dig @ns.cybercom.mil. usno.navy.mil soa $ dig @UFORIFTR01.CSD.DISA.MIL. usno.navy.mil soa $ dig @NS1.CSD.DISA.MIL. usno.navy.mil soa $ dig @UPDCIFTR01.CSD.DISA.MIL. usno.navy.mil soa The DNS administrators of navy.mil need to fix four of their seven authoritative name servers to respond properly for usno.navy.mil… Matt From: Outages <[email protected]> on behalf of Warren Kumari via Outages <[email protected]> Reply-To: Warren Kumari <[email protected]> Date: Friday, December 21, 2018 at 10:00 AM To: Jared Mauch <[email protected]> Cc: "[email protected]" <[email protected]> Subject: [EXTERNAL] Re: [outages] usno.navy.mil disappeared? Actually, that is what I was going to say... and then I poked again and saw: $ dig ns usno.navy.mil<http://usno.navy.mil> @ns.cybercom.mil<http://ns.cybercom.mil>. ; <<>> DiG 9.11.1-P3 <<>> ns usno.navy.mil<http://usno.navy.mil> @ns.cybercom.mil<http://ns.cybercom.mil>. ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 13693 ;; flags: qr aa; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;usno.navy.mil<http://usno.navy.mil>. IN NS ;; Query time: 52 msec ;; SERVER: 131.77.60.235#53(131.77.60.235) ;; WHEN: Fri Dec 21 09:56:49 EST 2018 ;; MSG SIZE rcvd: 42 navy.mil<http://navy.mil> seems to be returning NXDOMAIN for usno.navy.mil<http://usno.navy.mil> (or, I haven't had sufficient coffee..) W On Fri, Dec 21, 2018 at 9:56 AM Jared Mauch via Outages <[email protected]<mailto:[email protected]>> wrote: Looks like either a DNSSEC problem or their servers are down/unreachable. http://dnsviz.net/d/usno.navy.mil/dnssec/ - Jared > On Dec 21, 2018, at 9:48 AM, Steven Surdock via Outages > <[email protected]<mailto:[email protected]>> wrote: > > Anyone know what is going on with The US Naval Observatory? > Usno.navy.mil<http://Usno.navy.mil> appears to be completely unresolvable. > Affecting access to tick and tock time servers. > > $ nslookup -type=NS usno.navy.mil<http://usno.navy.mil> 8.8.8.8 > *** google-public-dns-a.google.com<http://google-public-dns-a.google.com> > can't find usno.navy.mil<http://usno.navy.mil>: Server failed > Server: google-public-dns-a.google.com<http://google-public-dns-a.google.com> > Address: 8.8.8.8 > > -Steve S. > > _______________________________________________ > Outages mailing list > [email protected]<mailto:[email protected]> > https://puck.nether.net/mailman/listinfo/outages _______________________________________________ Outages mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/outages -- I don't think the execution is relevant when it was obviously a bad idea in the first place. This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants. ---maf
_______________________________________________ Outages mailing list [email protected] https://puck.nether.net/mailman/listinfo/outages
