faa.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (155.178.199.16, 155.178.206.21, 162.58.33.66, 162.58.35.136, 2001:19e8:8001:2990::16, 2001:19e8:8041:21::80)
faa.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (155.178.199.16, 155.178.206.21, 162.58.33.66, 162.58.35.136, 2001:19e8:8001:2990::16, 2001:19e8:8041:21::80, UDP_-_NOEDNS_)
faa.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2600:1480:1::41, UDP_-_EDNS0_512_D_KN)
faa.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2600:1480:1::41, UDP_-_EDNS0_512_D_KN)
faa.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (155.178.199.16, 155.178.206.21, 162.58.33.66, 162.58.35.136, 2001:19e8:8001:2990::16, 2001:19e8:8041:21::80, UDP_-_NOEDNS_)
faa.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (2)
faa.gov/SOA: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2600:1480:1::41, UDP_-_EDNS0_4096_D_KN_0x20)
gov to faa.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): faa-ct-egm1.faa.gov, faa-mc-egm1.faa.gov See RFC 1034, Sec. 4.2.2.