From 01b578f67e49ae2ad0d6070336fffef0dc40023e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ond=C5=99ej=20Sur=C3=BD?= Date: Mon, 3 Apr 2023 11:40:34 +0200 Subject: [PATCH] Clarify the documentation about DF-flag Remove the reference to setting the DF-flag as we don't do that right now. Rephrase the paragraph that the default value should not be causing fragmentation. (cherry picked from commit 61f276d5a407a473bc762cde25d417370c3f5ca0) --- doc/arm/reference.rst | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/doc/arm/reference.rst b/doc/arm/reference.rst index 322ec27b7b..3f45dae842 100644 --- a/doc/arm/reference.rst +++ b/doc/arm/reference.rst @@ -4506,9 +4506,8 @@ Tuning dropping patterns, the query is retried over TCP. Per-server EDNS statistics are only retained in memory for the lifetime of a given server's ADB entry. - The :iscman:`named` now sets the DON'T FRAGMENT flag on outgoing UDP packets. - According to the measurements done by multiple parties this should not be - causing any operational problems as most of the Internet "core" is able to + According to the measurements done by multiple parties the default value + should not be causing the fragmentation as most of the Internet "core" is able to cope with IP message sizes between 1400-1500 bytes, the 1232 size was picked as a conservative minimal number that could be changed by the DNS operator to a estimated path MTU minus the estimated header space. In practice, the