duckdns.org zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (3.97.51.116, 3.97.58.28, 15.222.19.97, 15.223.106.16, 35.182.183.211, 35.183.157.249, 99.79.16.64, 99.79.143.35)
duckdns.org/DNSKEY: No response was received from the server over TCP (tried 10 times). See RFC 1035, Sec. 4.2. (35.182.183.211, 99.79.16.64, TCP_-_EDNS0_4096_D_N)
duckdns.org/DNSKEY: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (3.97.51.116, 15.222.19.97, TCP_-_EDNS0_4096_D_KN)
duckdns.org/DNSKEY: No response was received from the server over TCP (tried 6 times). See RFC 1035, Sec. 4.2. (15.223.106.16, TCP_-_EDNS0_4096_)
duckdns.org/DNSKEY: No response was received from the server over TCP (tried 8 times). See RFC 1035, Sec. 4.2. (3.97.58.28, TCP_-_EDNS0_4096_D)
duckdns.org/DNSKEY: No response was received from the server over TCP (tried 9 times). See RFC 1035, Sec. 4.2. (35.183.157.249, 99.79.143.35, TCP_-_EDNS0_4096_D)
duckdns.org/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (15.223.106.16, UDP_-_EDNS0_512_D_KN)
Warnings (5)
NSEC3 proving non-existence of duckdns.org/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of duckdns.org/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
familjenisback.duckdns.org/A: 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. (15.223.21.81, UDP_-_EDNS0_4096_D_KN)
duckdns.org/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
familjenisback.duckdns.org/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.