From 17834caa6cf2d05656d3162ab525023d2de06fe2 Mon Sep 17 00:00:00 2001 From: Evan Hunt Date: Fri, 6 Nov 2015 13:44:28 -0800 Subject: [PATCH] [master] clarify message-compression doc - mention TCP and RFC compliance issues --- doc/arm/Bv9ARM-book.xml | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/doc/arm/Bv9ARM-book.xml b/doc/arm/Bv9ARM-book.xml index b7e268bd09..01a7041a10 100644 --- a/doc/arm/Bv9ARM-book.xml +++ b/doc/arm/Bv9ARM-book.xml @@ -6154,12 +6154,15 @@ options { message-compression - If yes, DNS name compression will - be used for responses to regular queries (not including + If yes, DNS name compression is + used in responses to regular queries (not including AXFR or IXFR, which always uses compression). Setting - this option to no can result in - larger responses, but will reduce CPU usage on servers. - The default is yes. + this option to no reduces CPU + usage on servers and may improve throughput. However, + it increases response size, which may cause more queries + to be processed using TCP; a server with compression + disabled is out of compiance with RFC 1123 Section + 6.1.3.2. The default is yes. @@ -6699,7 +6702,7 @@ options { auto-dnssec - + Zones configured for dynamic DNS may use this option to allow varying levels of automatic DNSSEC key management. There are three possible settings: