NSEC3 proving non-existence of dds.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of dds.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
dds.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
NSEC3 proving non-existence of dds.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of dds.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
dds.mil/A: 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. (2608:140:c:157::235, UDP_-_EDNS0_4096_D_KN)
dds.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. (2608:c144:1:155::243, UDP_-_EDNS0_4096_D_KN)
mil to dds.mil: 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.154.234, UDP_-_EDNS0_4096_D_KN)
tm9wpi7ygs.dds.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
dds.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.