mil to southcom.mil: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
mil to southcom.mil: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
southcom.mil zone: The following NS name(s) did not resolve to address(es): ehuibdns02.southcom.mil, esuibdns01.southcom.mil
southcom.mil/A (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN)
southcom.mil/A (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN)
southcom.mil/AAAA (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN)
southcom.mil/AAAA (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN)
southcom.mil/MX (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
southcom.mil/MX (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
southcom.mil/NS (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN)
southcom.mil/NS (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN)
southcom.mil/NSEC3PARAM (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN)
southcom.mil/NSEC3PARAM (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN)
southcom.mil/SOA (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (130.22.36.4, 130.22.177.211, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
southcom.mil/SOA (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (130.22.36.4, 130.22.177.211, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
southcom.mil/TXT (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN)
southcom.mil/TXT (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN)
southcom.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
s7dl0q6n8m.southcom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
southcom.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
southcom.mil/DS (alg 8, id 60496): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
southcom.mil/DS (alg 8, id 60496): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
southcom.mil/DS (alg 8, id 60496): 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.
southcom.mil/DS (alg 8, id 60496): 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.