NSEC3 proving non-existence of uca.ma/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 uca.ma/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
uca.ma zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (196.200.176.7)
uca.ma/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (196.200.176.7, UDP_-_NOEDNS_)
uca.ma/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (196.200.176.7, UDP_-_NOEDNS_)
uca.ma/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
NSEC3 proving non-existence of uca.ma/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of uca.ma/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
ma to uca.ma: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the ma zone): nsb.uca.ma, nsa.uca.ma See RFC 1034, Sec. 4.2.2.
ma to uca.ma: The following NS name(s) were found in the delegation NS RRset (i.e., in the ma zone), but not in the authoritative NS RRset: srv1-uca.ma, srv2-uca.ma See RFC 1034, Sec. 4.2.2.
uca.ma/DS has warnings; select the "Denial of existence" DNSSEC option to see them.