3120s.com zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (185.28.194.194, 185.38.108.108, 2a00:fea0:dead::beef)
3120s.com zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (185.28.194.194, 185.38.108.108, 2a00:fea0:dead::beef)
3120s.com/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (185.28.194.194, 185.38.108.108, 2a00:fea0:dead::beef, UDP_-_EDNS0_4096_D_KN)
3120s.com/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (185.28.194.194, 185.38.108.108, 2a00:fea0:dead::beef, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
3120s.com/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (185.28.194.194, 185.38.108.108, 2a00:fea0:dead::beef, UDP_-_EDNS0_4096_D_KN)
3120s.com/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (185.28.194.194, 185.38.108.108, 2a00:fea0:dead::beef, TCP_-_EDNS0_4096_D_N)
3120s.com/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (185.28.194.194, 185.38.108.108, 2a00:fea0:dead::beef, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
3120s.com/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
3120s.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
8h1gq9yris.3120s.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
3120s.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
3120s.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
3120s.com/MX has errors; select the "Denial of existence" DNSSEC option to see them.
3120s.com/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (1)
com to 3120s.com: The following NS name(s) were found in the delegation NS RRset (i.e., in the com zone), but not in the authoritative NS RRset: ns3.blacknight.com, ns4.blacknight.com See RFC 1034, Sec. 4.2.2.