Hi Anand,
If it were me, I would instead use the
"max-udp-payload" option, set to
1280, so that Knot emits responses with TC set. This may cause some
clients to retry over TCP. But one missing feature in Knot is that it
doesn't allow tuning of the EDNS payload separately for IPv4 and IPv6.
It might be useful to have "max-udp-payload-ipv4" and
"max-udp-payload-ipv6" options for setting this separately, because IPv4
and IPv6 behaviours are different.
Thank you for the input! This sounds to be a better solution than
forcing the fragmentation. Based on the conclusions from the Geoff's
experiment... We will consider adding a separate option for IPv6.
Regards,
Jan