pgecorp.com zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (131.90.0.50, 131.90.0.51)
pgecorp.com zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (131.90.0.50, 131.90.0.51)
pgecorp.com/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (131.90.0.50, 131.90.0.51, UDP_-_EDNS0_4096_D_KN)
pgecorp.com/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (131.90.0.50, 131.90.0.51, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
pgecorp.com/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (131.90.0.50, 131.90.0.51, UDP_-_EDNS0_4096_D_KN)
pgecorp.com/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (131.90.0.50, 131.90.0.51, TCP_-_EDNS0_4096_D_N)
pgecorp.com/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (131.90.0.50, 131.90.0.51, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
pgecorp.com/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (131.90.0.50, 131.90.0.51, UDP_-_EDNS0_4096_D_KN)
pgecorp.com/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
pgecorp.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
pgecorp.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
pgecorp.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
pgecorp.com/MX has errors; select the "Denial of existence" DNSSEC option to see them.
n89txqukwa.pgecorp.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (2)
com to pgecorp.com: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the com zone): ns3.pge.com, ns4.pge.com See RFC 1034, Sec. 4.2.2.
com to pgecorp.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: can13.pge.com, can14.pge.com See RFC 1034, Sec. 4.2.2.