RRSIG NSEC3 proving non-existence of yandex.ru/DS alg 8, id 52263: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG NSEC3 proving non-existence of yandex.ru/DS alg 8, id 52263: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG ru/SOA alg 8, id 52263: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
ru zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (193.232.156.17)
ru/DNSKEY: No response was received from the server over TCP (tried 1 times). See RFC 1035, Sec. 4.2. (193.232.156.17, TCP_-_EDNS0_4096_D_KN)
ru/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (193.232.142.17, UDP_-_EDNS0_512_D_KN)
yandex.ru/NS: The TCP connection was interrupted (ECONNRESET). See RFC 1035, Sec. 4.2. (193.232.142.17, TCP_-_EDNS0_4096_D_KN)
yandex.ru/NS: There was an error communicating with the server over TCP (UNKNOWN). See RFC 1035, Sec. 4.2. (193.232.128.6, TCP_-_EDNS0_4096_D_KN)
yandex.ru/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
ru/DNSKEY (alg 8, id 43786): No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (193.232.142.17, UDP_-_EDNS0_4096_D_KN)
ru/DNSKEY (alg 8, id 44301): No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (193.232.142.17, UDP_-_EDNS0_4096_D_KN)
ru/DNSKEY (alg 8, id 52263): No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (193.232.142.17, UDP_-_EDNS0_4096_D_KN)
yandex.ru/TXT: 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. (2a02:6b8::1, UDP_-_EDNS0_4096_D_KN)
vfotp8gak3.yandex.ru/A has warnings; select the "Denial of existence" DNSSEC option to see them.