At time of post..
.mil. is down.
Apparently an Anonymous "Operation Payback".
.mil nameservers are unresponsive.
Well that's the most ludicrous thing I've heard all month.
*grabs popcorn*
All those Domain servers seem to be in the one /16 and my traces show them
all taking the same network path... Well that is pretty poor planning...
Got this from a friend: http://pastebin.com/UkwHbY1V
Greeting Internet.
This is Operation PayBack
We Are Anonymous Centre
PayBack is a bitch
All US MILITARY SERVERS ARE OFFLINE
Operation PayBack - http://armypubs.army.mil
Operation PayBack - http://army.mil
Operation PayBack - www.public.navy.mil
Operation PayBack - http://navy.mil
Operation PayBack - http://usmc.mil
Operation PayBack - http://US.Army.mil
Operation PayBack - http://NKO.navy.mil
Operation PayBack - http://www.uscg.mil
Operation PayBack - http://www.af.mil
Operation PayBack - http://www.marines.mil
Operation PayBack - http://www.militaryonesource.mil
Operation PayBack - http://www.dtic.mil
Operation PayBack - http://www.dfas.mil
Operation PayBack - http://www.dla.mil
Operation PayBack - http://www.move.mil
Operation PayBack - http://www.jcs.mil
Operation PayBack - http://www.stratcom.mil
Operation PayBack - http://www.dc3.mil
Operation PayBack - US ARMY
Operation PayBack - US NAVY
Operation PayBack - US MARINES
Operation PayBack - US AIR FORCE
All US MILITARY SERVERS ARE OFFLINE
@Anon_Centre
#AnonCentre
OpenDNS still has A records for nipr.mil authoritative nameservers.
% dig -t ns nipr.mil @resolver1.opendns.com
; <<>> DiG 9.9.3-P2 <<>> -t ns nipr.mil @resolver1.opendns.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37645
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;nipr.mil. IN NS
;; ANSWER SECTION:
nipr.mil. 20126 IN NS EUR2.nipr.mil.
nipr.mil. 20126 IN NS EUR1.nipr.mil.
nipr.mil. 20126 IN NS PAC2.nipr.mil.
nipr.mil. 20126 IN NS CON1.nipr.mil.
nipr.mil. 20126 IN NS PAC1.nipr.mil.
nipr.mil. 20126 IN NS CON2.nipr.mil.
;; Query time: 58 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Tue May 20 04:09:11 UTC 2014
;; MSG SIZE rcvd: 151
% dig eur2.nipr.mil @resolver1.opendns.com
; <<>> DiG 9.9.3-P2 <<>> eur2.nipr.mil @resolver1.opendns.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44901
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;eur2.nipr.mil. IN A
;; ANSWER SECTION:
eur2.nipr.mil. 20103 IN A 199.252.143.234
;; Query time: 56 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Tue May 20 04:09:34 UTC 2014
;; MSG SIZE rcvd: 58
Hi Clark
It's down when looked upon from our DNS recursors in India as well.
I have seen in past with many domains (not TLDs though) that when they are
down due to non-reachability of authoritative servers for the zone, OpenDNS
and Google DNS still give answers. Likely they have some in-built
resistivity to these issues by serving the stale data when auth is
unreachable.
Looks like it has been corrected now
a message of 107 lines which said:
Looks like it has been corrected now
Not from everywhere. From two different networks in France, I get:
% check-soa -i nipr.mil
CON1.nipr.mil.
199.252.157.234: ERROR: Timeout
CON2.nipr.mil.
199.252.162.234: ERROR: Timeout
EUR1.nipr.mil.
199.252.154.234: ERROR: Timeout
EUR2.nipr.mil.
199.252.143.234: OK: 2014051904 (256 ms)
PAC1.nipr.mil.
199.252.180.234: ERROR: Timeout
PAC2.nipr.mil.
199.252.155.234: ERROR: Timeout
% check-soa -i mil
CON1.NIPR.mil.
199.252.157.234: ERROR: Timeout
CON2.NIPR.mil.
199.252.162.234: ERROR: Timeout
EUR1.NIPR.mil.
199.252.154.234: ERROR: Timeout
EUR2.NIPR.mil.
199.252.143.234: OK: 2014051904 (265 ms)
PAC1.NIPR.mil.
199.252.180.234: ERROR: Timeout
PAC2.NIPR.mil.
199.252.155.234: ERROR: Timeout