- Update man page templates from rst.

diff --git a/doc/unbound-control.8.in b/doc/unbound-control.8.in
index 4a3bf6374898fbb3980e59bc0b4d656b8a0728b9..687c680e2444e1c51364721e23414e2c3f6359e4 100644 (file)
--- a/doc/unbound-control.8.in
+++ b/doc/unbound-control.8.in
@@ -1367,6 +1367,15 @@ Increased for every RRset inspection that fails.
 .UNINDENT
 .INDENT 0.0
 .TP
 .UNINDENT
 .INDENT 0.0
 .TP

+.B num.valops 
+The number of validation operations performed by the validator.
+Increased for every RRSIG verification operation regardless of the
+validation result.
+The RRSIG and key combination needs to first pass some sanity checks before
+Unbound even performs the verification, e.g., length/protocol checks.
+.UNINDENT
+.INDENT 0.0
+.TP

 .B unwanted.queries 
 Number of queries that were refused or dropped because they failed the
 access control settings.
 .B unwanted.queries 
 Number of queries that were refused or dropped because they failed the
 access control settings.

diff --git a/doc/unbound.conf.5.in b/doc/unbound.conf.5.in
index f6b748d5c5fe7486de6778c42a2ea2fdd775471b..5cb497c97862bf3ef45c493c8d6ae789fd235ffd 100644 (file)
--- a/doc/unbound.conf.5.in
+++ b/doc/unbound.conf.5.in
@@ -996,6 +996,7 @@ that likely the client does not need a reply for any more.
 This could happen if the host has not been able to service the queries for
 a while, i.e. Unbound is not running, and then is enabled again.
 It uses timestamp socket options.
 This could happen if the host has not been able to service the queries for
 a while, i.e. Unbound is not running, and then is enabled again.
 It uses timestamp socket options.

+The socket option is available on the Linux and FreeBSD platforms.

 .sp
 Default: 0 (disabled)
 .UNINDENT
 .sp
 Default: 0 (disabled)
 .UNINDENT


@@ -2283,8 +2284,8 @@ Default: yes
 .INDENT 0.0
 .TP
 .B disable\-dnssec\-lame\-check: \fI<yes or no>\fP 
 .INDENT 0.0
 .TP
 .B disable\-dnssec\-lame\-check: \fI<yes or no>\fP 

-If true, disables the DNSSEC lameness check in the iterator.
-This check sees if RRSIGs are present in the answer, when dnssec is
+If yes, disables the DNSSEC lameness check in the iterator.
+This check sees if RRSIGs are present in the answer, when DNSSEC is

 expected, and retries another authority if RRSIGs are unexpectedly missing.
 The validator will insist in RRSIGs for DNSSEC signed domains regardless of
 this setting, if a trust anchor is loaded.
 expected, and retries another authority if RRSIGs are unexpectedly missing.
 The validator will insist in RRSIGs for DNSSEC signed domains regardless of
 this setting, if a trust anchor is loaded.


@@ -3750,7 +3751,7 @@ Default: 65001
 .B ede: \fI<yes or no>\fP 
 If enabled, Unbound will respond with Extended DNS Error codes
 (\fI\%RFC 8914\fP).
 .B ede: \fI<yes or no>\fP 
 If enabled, Unbound will respond with Extended DNS Error codes
 (\fI\%RFC 8914\fP).

-These EDEs privide additional information with a response mainly for, but
+These EDEs provide additional information with a response mainly for, but

 not limited to, DNS and DNSSEC errors.
 .sp
 When the \fI\%val\-log\-level\fP option is also
 not limited to, DNS and DNSSEC errors.
 .sp
 When the \fI\%val\-log\-level\fP option is also