[dns-operations] [Ext] Is anyone able to resolve names in .mil?

Thu Aug 29 23:35:27 UTC 2019

Besides that you have a typo in your last dig, 
Seems like RRSIG are close to expire, but answering on my side:

this is what I can see:

$ dig con1.nipr.mil @199.252.154.234  +dnssec +multi +norec

; <<>> DiG 9.14.5 <<>> con1.nipr.mil @199.252.154.234 +dnssec +multi +norec
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 621
;; flags: qr aa; QUERY: 1, ANSWER: 2, AUTHORITY: 7, ADDITIONAL: 11

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 4096
;; QUESTION SECTION:
;con1.nipr.mil.		IN A

;; ANSWER SECTION:
CON1.NIPR.MIL.		21600 IN A 199.252.157.234
CON1.NIPR.MIL.		21600 IN RRSIG A 8 3 21600 (
				20190905161727 20190829161727 53946 nipr.mil.
				Le6pRam3B0r5DaZieT/fZGvVfCJ4hMPzzLXEQaXEEIth
				IwArlDYc2aV3uYkdnw0BfpnZu7moCCsOoIdo/k3WpR+g
				xOL24WqkGycStQroZN3f1c8lmRTFI+lGekLe7NYDpyod
				79ILDnbWbwRndhv6l6LTZwmwpzN4F069bVIEpUk= )

;; AUTHORITY SECTION:
NIPR.MIL.		21600 IN NS PAC2.NIPR.MIL.
NIPR.MIL.		21600 IN NS EUR1.NIPR.MIL.
NIPR.MIL.		21600 IN NS CON1.NIPR.MIL.
NIPR.MIL.		21600 IN NS CON2.NIPR.MIL.
NIPR.MIL.		21600 IN NS EUR2.NIPR.MIL.
NIPR.MIL.		21600 IN NS PAC1.NIPR.MIL.
NIPR.MIL.		21600 IN RRSIG NS 8 2 21600 (
				20190905161727 20190829161727 53946 nipr.mil.
				ww+BX5eNLFUHN2U7zt01WLKt38KwyFhe7atFUkTBQBhD
				17YGcPnR+rSUh8g+O8PxWtoiuN2Xeg/IsBoe68OvO1QT
				BB7nXtOIAS3CuXlW5hqggpSyiZF20IDENNdlgksSWB4Q
				+gedN84txif31htUx9XESy8/Fya55RFNOEcUJMM= )

;; ADDITIONAL SECTION:
EUR1.NIPR.MIL.		21600 IN A 199.252.154.234
EUR2.NIPR.MIL.		21600 IN A 199.252.143.234
PAC1.NIPR.MIL.		21600 IN A 199.252.180.234
PAC2.NIPR.MIL.		21600 IN A 199.252.155.234
CON2.NIPR.MIL.		21600 IN A 199.252.162.234
EUR1.NIPR.MIL.		21600 IN RRSIG A 8 3 21600 (
				20190905161727 20190829161727 53946 nipr.mil.
				miixWQv6SyVt8v3x08/NN3AvGMEVWt+cXlmWBZgxGUVD
				1raUABT/2UNcpUnXZijmIhy+17S7gueMjmMHjWf7J6I/
				FswCXBt/c1+10VI18AbLGveVv1ovh20tLCxjEs6DCkaK
				UeLDGqHrwHaGq0wjgne867kz3qhWmCupy4hjvYU= )
EUR2.NIPR.MIL.		21600 IN RRSIG A 8 3 21600 (
				20190905161727 20190829161727 53946 nipr.mil.
				kA/tYvftiUxlVB5siRZlfP+tLkbuYzsm6g7qcNjgKdi1
				lZzJAJffIcVhTuxsRCd9y9UsOqWd62BoqYONU3gR1Qh6
				FM5Rd7tO1SxNygAAruTXika0miL1k3W0CbWP3acMIGSy
				fnbfpff7HDP/1WDmFLx4r5Qoc9Wu1G73LY6oQ7A= )
PAC1.NIPR.MIL.		21600 IN RRSIG A 8 3 21600 (
				20190905161727 20190829161727 53946 nipr.mil.
				Qfh4ihUCJNNhmh1uj5JSSNBScXaqxXnOyXaLyUl3ggvI
				hLZsQ7QJIZO19yys+p6b1kXJXNey5FQ32vVEXVXrnDDZ
				bh/tCFxQhl8nDZhERKpWc6nZ7V28pXXoixE0K6V0cu5o
				fty/HJO0Bfd2N56lCxk2GhjoIzoFnzGADO8RcP8= )
PAC2.NIPR.MIL.		21600 IN RRSIG A 8 3 21600 (
				20190905161727 20190829161727 53946 nipr.mil.
				w+pFSZ4Rs1EsVyQwy4bHPnqR/HVdPanp4SpKJcqPITVS
				6YM6IuCCc2n2iwbECO8x1Tu65XJ5VsraWgny2JqUZzON
				3onxec0pGPK8wpjRCBypAhwkPHV0RdrDHufRwuiSOLBg
				cO2o1xoO4nEI23ndkukrgdoldCWFYsDa7LB7i0s= )
CON2.NIPR.MIL.		21600 IN RRSIG A 8 3 21600 (
				20190905161727 20190829161727 53946 nipr.mil.
				lPG09xj0SZb/BIp1/nFp8ZJPSOwVPd3JbCE942viI6lT
				SzfYoB571ocSEVOhGUIEochdmtjtw+eZT+YUaIk0rR9m
				drI0XDxWXSqvMlm6UbEO9XGIQvLyqf4aZuVvIO4M5BNl
				B4zFFOEEUZMx5AZ70CHAGlzOwZp8JNZZ0VQlmJs= )

;; Query time: 39 msec
;; SERVER: 199.252.154.234#53(199.252.154.234)
;; WHEN: Thu Aug 29 19:33:29 EDT 2019
;; MSG SIZE  rcvd: 1436

-- 
Mauricio Vergara Ereche
Lead DNS Engineer
ICANN

On 2019-08-29, 19:22, "dns-operations on behalf of Warren Kumari" <dns-operations-bounces at dns-oarc.net on behalf of warren at kumari.net> wrote:

    Heyya.

    Is anyone able to resolve names in .mil? It seems to have fallen off
    the Internets from everywhere I can see...

    $dig ns mil @a.root-servers.net

    ; <<>> DiG 9.10.6 <<>> ns mil @a.root-servers.net
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52668
    ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 6, ADDITIONAL: 7
    ;; WARNING: recursion requested but not available

    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 1232
    ;; QUESTION SECTION:
    ;mil. IN NS

    ;; AUTHORITY SECTION:
    mil. 172800 IN NS con1.nipr.mil.
    mil. 172800 IN NS con2.nipr.mil.
    mil. 172800 IN NS eur1.nipr.mil.
    mil. 172800 IN NS eur2.nipr.mil.
    mil. 172800 IN NS pac1.nipr.mil.
    mil. 172800 IN NS pac2.nipr.mil.

    ;; ADDITIONAL SECTION:
    con1.nipr.mil. 172800 IN A 199.252.157.234
    con2.nipr.mil. 172800 IN A 199.252.162.234
    eur1.nipr.mil. 172800 IN A 199.252.154.234
    eur2.nipr.mil. 172800 IN A 199.252.143.234
    pac1.nipr.mil. 172800 IN A 199.252.180.234
    pac2.nipr.mil. 172800 IN A 199.252.155.234

    ;; Query time: 47 msec
    ;; SERVER: 2001:503:ba3e::2:30#53(2001:503:ba3e::2:30)
    ;; WHEN: Thu Aug 29 19:06:34 EDT 2019
    ;; MSG SIZE  rcvd: 247

    $  dig con1.nirp.mil @199.252.154.234

    ; <<>> DiG 9.10.6 <<>> con1.nirp.mil @199.252.154.234
    ;; global options: +cmd
    ;; connection timed out; no servers could be reached

    W

    -- 
    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
    _______________________________________________
    dns-operations mailing list
    dns-operations at lists.dns-oarc.net
    https://lists.dns-oarc.net/mailman/listinfo/dns-operations