hpc.mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (140.32.61.226, 2001:480:b0:f003::226)
hpc.mil/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.32.61.226, 2001:480:b0:f003::226, UDP_-_NOEDNS_)
hpc.mil/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.32.61.226, 2001:480:b0:f003::226, UDP_-_NOEDNS_)
mil zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (199.252.154.234)
mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (199.252.162.234)
mil/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.252.154.234, UDP_-_EDNS0_4096_D_KN)
Warnings (6)
hpc.mil/DS (alg 13, id 51716): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
hpc.mil/DS (alg 13, id 51716): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
hpc.mil/DS (alg 13, id 51716): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
hpc.mil/DS (alg 13, id 51716): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
mil to hpc.mil: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the mil zone): auth-sandiego.dren.mil See RFC 1034, Sec. 4.2.2.
mil to hpc.mil: The following NS name(s) were found in the delegation NS RRset (i.e., in the mil zone), but not in the authoritative NS RRset: auth-west.dren.mil See RFC 1034, Sec. 4.2.2.