NSEC3 proving non-existence of tim.rs/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 tim.rs/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
tim.rs zone: The following NS name(s) did not resolve to address(es): ares1.tim.rs
tim.rs zone: The server(s) did not respond authoritatively for the namespace. See RFC 1035, Sec. 4.1.1. (80.93.224.2)
tim.rs zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (185.22.144.58)
tim.rs/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
NSEC3 proving non-existence of tim.rs/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of tim.rs/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
rs to tim.rs: The following NS name(s) were found in the delegation NS RRset (i.e., in the rs zone), but not in the authoritative NS RRset: ns2.absolutok.com, ares1.tim.rs See RFC 1034, Sec. 4.2.2.