centcom.mil zone: The following NS name(s) did not resolve to address(es): ns1.centcom.mil
centcom.mil/A (NODATA): No NSEC RR(s) were returned to validate the NODATA response. (214.26.71.170, UDP_-_EDNS0_4096_D_KN)
centcom.mil/A (NODATA): No SOA RR was returned with the NODATA response. (214.26.71.170, UDP_-_EDNS0_4096_D_KN)
centcom.mil/DNSKEY (alg 8, id 2269): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (214.26.71.170, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
centcom.mil/DNSKEY (alg 8, id 49371): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (214.26.71.170, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
centcom.mil/NS (NODATA): No NSEC RR(s) were returned to validate the NODATA response. (214.26.71.170, UDP_-_EDNS0_4096_D_KN)
centcom.mil/NS (NODATA): No SOA RR was returned with the NODATA response. (214.26.71.170, UDP_-_EDNS0_4096_D_KN)
centcom.mil/NSEC3PARAM (NODATA): No NSEC RR(s) were returned to validate the NODATA response. (214.26.71.170, UDP_-_EDNS0_4096_D_KN)
centcom.mil/NSEC3PARAM (NODATA): No SOA RR was returned with the NODATA response. (214.26.71.170, UDP_-_EDNS0_4096_D_KN)
centcom.mil/SOA (NODATA): No NSEC RR(s) were returned to validate the NODATA response. (214.26.71.170, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
centcom.mil/SOA (NODATA): No SOA RR was returned with the NODATA response. (214.26.71.170, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
centcom.mil/TXT (NODATA): No NSEC RR(s) were returned to validate the NODATA response. (214.26.71.170, UDP_-_EDNS0_4096_D_KN)
centcom.mil/TXT (NODATA): No SOA RR was returned with the NODATA response. (214.26.71.170, UDP_-_EDNS0_4096_D_KN)
mil to centcom.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. (214.26.71.170, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
mil to centcom.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. (214.26.71.170, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
Warnings (8)
centcom.mil/DS (alg 8, id 2269): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
centcom.mil/DS (alg 8, id 2269): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
centcom.mil/DS (alg 8, id 2269): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
centcom.mil/DS (alg 8, id 2269): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
centcom.mil/DS (alg 8, id 2269): 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. (2608:c184:1:180::234, UDP_-_EDNS0_4096_D_KN)
centcom.mil/DS (alg 8, id 2269): 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. (2608:c184:1:180::234, UDP_-_EDNS0_4096_D_KN)
centcom.mil/DS (alg 8, id 2269): 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. (2608:c184:1:180::234, UDP_-_EDNS0_4096_D_KN)
centcom.mil/DS (alg 8, id 2269): 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. (2608:c184:1:180::234, UDP_-_EDNS0_4096_D_KN)