akamaiedge.net to a.akamaiedge.net: The glue address(es) for n1a.akamaiedge.net (2600:140b:1:f000:f888::, 2600:140b:1:f000:f888:dc72:9ccd:dcf8) differed from its authoritative address(es) (2600:140b:1:f000:f888:dc72:9ccd:dcf8). See RFC 1034, Sec. 4.2.2.
com to tiqcdn.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): dns5.c01.nsone.net.cn, dns2.c01.nsone.net.cn, dns3.c01.nsone.net.cn, dns4.c01.nsone.net.cn, dns1.c01.nsone.net.cn See RFC 1034, Sec. 4.2.2.
net to akamaiedge.net: Authoritative AAAA records exist for a11-192.akamaiedge.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
net to edgekey.net: Authoritative AAAA records exist for a13-65.akam.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
net to edgekey.net: Authoritative AAAA records exist for a5-65.akam.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
net to edgekey.net: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the net zone): a11-65.akam.net, ns1-2.akam.net, a9-65.akam.net, a3-65.akam.net See RFC 1034, Sec. 4.2.2.
net to edgekey.net: The following NS name(s) were found in the delegation NS RRset (i.e., in the net zone), but not in the authoritative NS RRset: ns1-66.akam.net, ns4-66.akam.net, ns5-66.akam.net, ns7-65.akam.net See RFC 1034, Sec. 4.2.2.