From 7beb4ba7ef8bff55974b4ed6d59bdf4f4712c623 Mon Sep 17 00:00:00 2001 From: Andreas Gustafsson Date: Thu, 28 Sep 2000 22:16:48 +0000 Subject: [PATCH] note that disabling recursion does not prevent access to data that is already cached --- doc/arm/Bv9ARM-book.xml | 19 ++++++++++++++----- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git a/doc/arm/Bv9ARM-book.xml b/doc/arm/Bv9ARM-book.xml index f0f8fbba27..7ad244bde9 100644 --- a/doc/arm/Bv9ARM-book.xml +++ b/doc/arm/Bv9ARM-book.xml @@ -2,7 +2,7 @@ - + @@ -2619,9 +2619,15 @@ to crash. recursion If yes, and a DNS query requests recursion, then the server will attempt to do -all the work required to answer the query. If recursion is not on, -the server will return a referral to the client if it doesn't know -the answer. The default is yes. See also fetch-glue above. +all the work required to answer the query. If recursion is off +and the server does not already know the answer, it will return a +referral response. The default is yes. +Note that setting recursion no; does not prevent +clients from getting data from the server's cache; it only +prevents new data from being cached as an effect of client queries. +Caching may still occur as an effect the server's internal +operation, such as NOTIFY address lookups. +See also fetch-glue above. rfc2308-type1 @@ -2770,7 +2776,10 @@ not specified, the default is to allow queries from all hosts. allow-recursion Specifies which hosts are allowed to make recursive queries through this server. If not specified, the -default is to allow recursive queries from all hosts. +default is to allow recursive queries from all hosts. +Note that disallowing recursive queries for a host does not prevent the +host from retrieving data that is already in the server's cache. + allow-transfer