bnn.go.id zone: The following NS name(s) did not resolve to address(es): nx1.sentinel.id
bnn.go.id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (103.112.223.1, 2001:df4:bd00::990:1)
bnn.go.id/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (103.112.223.1, 2001:df4:bd00::990:1, UDP_-_NOEDNS_)
bnn.go.id/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (103.112.223.1, 2001:df4:bd00::990:1, UDP_-_NOEDNS_)
Warnings (8)
RRSIG bnn.go.id/DS alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG go.id/DNSKEY alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG go.id/DNSKEY alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG go.id/DNSKEY alg 10, id 48051: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG go.id/DNSKEY alg 10, id 48051: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
go.id to bnn.go.id: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the go.id zone): nx1.sentinel.id See RFC 1034, Sec. 4.2.2.
go.id to bnn.go.id: The following NS name(s) were found in the delegation NS RRset (i.e., in the go.id zone), but not in the authoritative NS RRset: nx2.bnn.go.id See RFC 1034, Sec. 4.2.2.
bnn.go.id/DS has warnings; select the "Denial of existence" DNSSEC option to see them.