NSEC3 proving non-existence of cloudns.nz/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 cloudns.nz/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
cloudns.nz to networkconsulting.cloudns.nz: No delegation NS records were detected in the parent zone (cloudns.nz). This results in an NXDOMAIN response to a DS query (for DNSSEC), even if the parent servers are authoritative for the child. See RFC 1034, Sec. 4.2.2. (108.62.121.219, 109.201.133.196, 185.10.17.44, 185.206.180.140, 2604:9a00:2100:b000:1::1, 2a00:1768:1001:9::196, 2a07:8dc0:19:0:5d:37ff:fea5:bacd, 2a0b:1640:1:1:1:1:762:9aa6, UDP_-_EDNS0_4096_D_KN)
Warnings (2)
NSEC3 proving non-existence of cloudns.nz/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of cloudns.nz/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.