NSEC3 proving non-existence of ub.bw/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 ub.bw/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
ub.bw zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (168.167.8.18, 196.2.2.230, 196.2.2.231)
ub.bw zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:43f8:2a0::230, 2001:43f8:2a0::231, 2001:43f8:2a0:4::18)
ub.bw/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:43f8:2a0::230, 2001:43f8:2a0::231, 2001:43f8:2a0:4::18, UDP_-_NOEDNS_)
ub.bw/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:43f8:2a0::230, 2001:43f8:2a0::231, 2001:43f8:2a0:4::18, UDP_-_NOEDNS_)
ub.bw/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (168.167.8.18, 196.2.2.230, 196.2.2.231, TCP_-_EDNS0_4096_D_N)
ub.bw/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
NSEC3 proving non-existence of ub.bw/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of ub.bw/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
bw to ub.bw: Authoritative AAAA records exist for ns1.ub.bw, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
bw to ub.bw: Authoritative AAAA records exist for ns2.ub.bw, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
bw to ub.bw: Authoritative AAAA records exist for ns3.ub.bw, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
bw/DS (alg 8, id 50194): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
bw/DS (alg 8, id 50194): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
bw/DS (alg 8, id 50194): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
bw/DS (alg 8, id 50194): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
ub.bw/DS has warnings; select the "Denial of existence" DNSSEC option to see them.