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

[Viktor Dukhovni]

On Thu, Aug 29, 2019 at 07:12:27PM -0400, Warren Kumari wrote:

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

I have a local copy of the root zone, but even querying a.root-servers
directly, I still see valid glue for .MIL:

    mil. IN NS con1.nipr.mil.
    mil. IN NS con2.nipr.mil.
    mil. IN NS eur1.nipr.mil.
    mil. IN NS eur2.nipr.mil.
    mil. IN NS pac1.nipr.mil.
    mil. IN NS pac2.nipr.mil.
    con1.nipr.mil. IN A 199.252.157.234
    con2.nipr.mil. IN A 199.252.162.234
    eur1.nipr.mil. IN A 199.252.154.234
    eur2.nipr.mil. IN A 199.252.143.234
    pac1.nipr.mil. IN A 199.252.180.234
    pac2.nipr.mil. IN A 199.252.155.234

And I can still resolve child nodes of .mil, directly at least one
of the .mil nameservers.  For example, MX lookups for darpa.mil:

    DARPA.MIL. IN NS NS1.DARPA.MIL. ; AD=0
    DARPA.MIL. IN NS NS3.DARPA.MIL. ; AD=0
    DARPA.MIL. IN NS NS2.DARPA.MIL. ; AD=0
    NS1.DARPA.MIL. IN A 192.5.18.195 ; AD=0
    NS2.DARPA.MIL. IN A 192.5.18.70 ; AD=0
    NS3.DARPA.MIL. IN A 158.63.250.6 ; AD=0

> $  dig con1.nirp.mil @199.252.154.234

That's a typo, "nirp" is "nipr", but I get a quick NXDOMAIN for
that, and the real answer for the correct name.  All those upper-case
answers look rather military:

    $ hsdig -n 199.252.154.234 -t a con1.nipr.mil
    CON1.NIPR.MIL. IN A 199.252.157.234
    NIPR.MIL. IN NS PAC2.NIPR.MIL.
    NIPR.MIL. IN NS EUR1.NIPR.MIL.
    NIPR.MIL. IN NS EUR2.NIPR.MIL.
    NIPR.MIL. IN NS PAC1.NIPR.MIL.
    NIPR.MIL. IN NS CON2.NIPR.MIL.
    NIPR.MIL. IN NS CON1.NIPR.MIL.
    EUR1.NIPR.MIL. IN A 199.252.154.234
    EUR2.NIPR.MIL. IN A 199.252.143.234
    PAC1.NIPR.MIL. IN A 199.252.180.234
    PAC2.NIPR.MIL. IN A 199.252.155.234
    CON2.NIPR.MIL. IN A 199.252.162.234

-- 
	Viktor.

[ "hsdig" is my own minimal CLI for Haskell's DNS library, to
  which I've recently contributed some features. ]