> On Oct 13, 2021, at 1:07 AM, Stephane Bortzmeyer wrote:
>
> On Tue, Oct 12, 2021 at 01:01:08PM -0400,
> Matthew Pounsett wrote
> a message of 11 lines which said:
>
>>> This might be a known intermittent IPv6 routing issue with DNSviz, do
>>> you see this problem for v4 and/or v6 ?
>>
>>
On Tue, Oct 12, 2021 at 01:01:08PM -0400,
Matthew Pounsett wrote
a message of 11 lines which said:
> > This might be a known intermittent IPv6 routing issue with DNSviz, do
> > you see this problem for v4 and/or v6 ?
>
> That would show up as a non-answer over IPv6, rather than an apparent
>
On Tue, 12 Oct 2021 at 11:24, Keith Mitchell wrote:
>
> This might be a known intermittent IPv6 routing issue with DNSviz, do
> you see this problem for v4 and/or v6 ?
That would show up as a non-answer over IPv6, rather than an apparent
PMTU/EDNS problem.
On Tue, Oct 12, 2021 at 11:21:44AM -0400,
Keith Mitchell wrote
a message of 22 lines which said:
> > (192.112.36.4, UDP_-_EDNS0_4096_D_KN)".
> >
> > Testing G-root/192.112.36.4
> This might be a known intermittent IPv6 routing issue with DNSviz, do you
> see this problem for v4 and/or v6 ?
On 10/12/21 11:14 AM, Stephane Bortzmeyer wrote:
DNSviz currently always flags the root with a warning "./DNSKEY (alg
8, id 14748): 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
DNSviz currently always flags the root with a warning "./DNSKEY (alg
8, id 14748): 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. (192.112.36.4,
