NSEC3 proving non-existence of ku.dk/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 ku.dk/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
ku.dk zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:878:1070:10::174, 2001:878:1070:11::190)
ku.dk/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:878:1070:10::174, 2001:878:1070:11::190, UDP_-_NOEDNS_)
ku.dk/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:878:1070:10::174, 2001:878:1070:11::190, UDP_-_NOEDNS_)
ku.dk/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
NSEC3 proving non-existence of ku.dk/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of ku.dk/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
dk to ku.dk: Authoritative AAAA records exist for ns1.ku.dk, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
dk to ku.dk: Authoritative AAAA records exist for ns2.ku.dk, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
ku.dk/DS has warnings; select the "Denial of existence" DNSSEC option to see them.