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)
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)
southcom.mil/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
8v3jo.5xuht.southcom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
southcom.mil/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
southcom.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
southcom.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
southcom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (14)
mil/DNSKEY (alg 8, id 26770): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (199.252.155.234, UDP_-_EDNS0_4096_D_KN)
mil/DNSKEY (alg 8, id 40843): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (199.252.155.234, UDP_-_EDNS0_4096_D_KN)
mil/DNSKEY (alg 8, id 63500): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (199.252.155.234, UDP_-_EDNS0_4096_D_KN)
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.
southcom.mil/SOA: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (130.22.36.4, UDP_-_EDNS0_4096_D_KN_0x20)
southcom.mil/CDNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
8v3jo.5xuht.southcom.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
southcom.mil/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
southcom.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
southcom.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
southcom.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.