From 2e4d64684e0bc6352d469650689c14690218bf57 Mon Sep 17 00:00:00 2001 From: "W.C.A. Wijngaards" Date: Wed, 6 Jan 2021 13:42:00 +0100 Subject: [PATCH] - Fix #387: client-subnet-always-forward seems to effectively bypass any caching? --- doc/Changelog | 2 ++ doc/unbound.conf.5.in | 3 ++- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/doc/Changelog b/doc/Changelog index 6c1e9a20e..7e8313333 100644 --- a/doc/Changelog +++ b/doc/Changelog @@ -1,6 +1,8 @@ 6 January 2021: Wouter - Fix #379: zone loading over HTTP appears to have buffer issues. - Merge PR #395 from mptre: add missing null check. + - Fix #387: client-subnet-always-forward seems to effectively bypass + any caching? 5 January 2021: Wouter - Fix #385: autoconf 2.70 impacts unbound build diff --git a/doc/unbound.conf.5.in b/doc/unbound.conf.5.in index 38bbc44df..fa6f91b7c 100644 --- a/doc/unbound.conf.5.in +++ b/doc/unbound.conf.5.in @@ -2033,7 +2033,8 @@ Specify whether the ECS address check (configured using query contains an ECS record, or only for queries for which the ECS record is generated using the querier address (and therefore did not contain ECS data in the client query). If enabled, the address check is skipped when the client -query contains an ECS record. Default is no. +query contains an ECS record. And the lookup in the regular cache is skipped. +Default is no. .TP .B max\-client\-subnet\-ipv6: \fI\fR Specifies the maximum prefix length of the client source address we are willing