NSEC3 proving non-existence of in.ua/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 in.ua/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
Warnings (4)
NSEC3 proving non-existence of in.ua/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of in.ua/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
in.ua to dej.in.ua: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the in.ua zone): ns2.h0zt.in, ns1.h0zt.in See RFC 1034, Sec. 4.2.2.
in.ua to dej.in.ua: The following NS name(s) were found in the delegation NS RRset (i.e., in the in.ua zone), but not in the authoritative NS RRset: ns1.dezh.in, ns2.dezh.in See RFC 1034, Sec. 4.2.2.