NSEC3 proving non-existence of ipac.gov/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 ipac.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
ipac.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (199.169.192.28, 199.169.194.28, 2605:3100:fffc:100::7, 2605:3100:fffd:100::7)
ipac.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.169.192.28, 199.169.194.28, 2605:3100:fffc:100::7, 2605:3100:fffd:100::7, UDP_-_NOEDNS_)
ipac.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.169.192.28, 2605:3100:fffc:100::7, UDP_-_NOEDNS_)
ipac.gov/NS: No response was received from the server over UDP (tried 13 times). See RFC 1035, Sec. 4.2. (199.169.194.28, 2605:3100:fffd:100::7, UDP_-_EDNS0_4096_D)
ipac.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
NSEC3 proving non-existence of ipac.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of ipac.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
gov to ipac.gov: Authoritative AAAA records exist for ns1.twai.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
ipac.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.