From bffb7c52d57e3b1f9e046bf3bfad06a4a838936d Mon Sep 17 00:00:00 2001 From: Wouter Wijngaards Date: Mon, 30 Apr 2018 07:24:05 +0000 Subject: [PATCH] - Fix spelling error in man page and note defaults as no instead of off. git-svn-id: file:///svn/unbound/trunk@4666 be551aaa-1e26-0410-a405-d3ace91eadb9 --- doc/Changelog | 4 ++++ doc/unbound.conf.5.in | 6 +++--- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/doc/Changelog b/doc/Changelog index b44bdec83..62534161c 100644 --- a/doc/Changelog +++ b/doc/Changelog @@ -1,3 +1,7 @@ +30 April 2018: Wouter + - Fix spelling error in man page and note defaults as no instead of + off. + 26 April 2018: Wouter - Fix for crash in daemon_cleanup with dnstap during reload, from Saksham Manchanda. diff --git a/doc/unbound.conf.5.in b/doc/unbound.conf.5.in index 4ddb92fae..57dceeb86 100644 --- a/doc/unbound.conf.5.in +++ b/doc/unbound.conf.5.in @@ -691,7 +691,7 @@ infrastructure data. Validates the replies if trust anchors are configured and the zones are signed. This enforces DNSSEC validation on nameserver NS sets and the nameserver addresses that are encountered on the referral path to the answer. -Default off, because it burdens the authority servers, and it is +Default no, because it burdens the authority servers, and it is not RFC standard, and could lead to performance problems because of the extra query load that is generated. Experimental option. If you enable it consider adding more numbers after the target\-fetch\-policy @@ -1429,7 +1429,7 @@ IP address of stub zone nameserver. Can be IP 4 or IP 6. To use a nondefault port for DNS communication append '@' with the port number. .TP .B stub\-prime: \fI -This option is by default off. If enabled it performs NS set priming, +This option is by default no. If enabled it performs NS set priming, which is similar to root hints, where it starts using the list of nameservers currently published by the zone. Thus, if the hint list is slightly outdated, the resolver picks up a correct list online. @@ -1827,7 +1827,7 @@ If Unbound was built with on a system that has installed the hiredis C client library of Redis, then the "redis" backend can be used. This backend communicates with the specified Redis server over a TCP -connection to store and retrive cache data. +connection to store and retrieve cache data. It can be used as a persistent and/or shared cache backend. It should be noted that Unbound never removes data stored in the Redis server, even if some data have expired in terms of DNS TTL or the Redis server has -- 2.47.3