NSEC3 proving non-existence of one.pl/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of one.pl/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
Warnings (5)
NSEC3 proving non-existence of one.pl/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of one.pl/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
pl/DNSKEY (alg 8, id 36705): 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. (2001:6d8:1001:1::252, UDP_-_EDNS0_4096_D_K)
pl/DNSKEY (alg 8, id 6064): 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. (2001:6d8:1001:1::252, UDP_-_EDNS0_4096_D_K)
pl/DNSKEY (alg 8, id 64224): 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. (2001:6d8:1001:1::252, UDP_-_EDNS0_4096_D_K)