From 1558adbcdf328d06bd265a1fb7cc0b9cbe1eaeba Mon Sep 17 00:00:00 2001 From: Tony Finch Date: Thu, 10 Mar 2022 18:37:32 +0000 Subject: [PATCH] Refer to RFC 4592 for DNS wildcards The named-checkzone(1) and named-compilezone(1) manual pages used to refer to the description of wildcards in RFC 1034. (cherry picked from commit 178aef5b8c05b70d780b150f165398811853e709) --- bin/check/named-checkzone.rst | 2 +- doc/man/named-checkzone.8in | 2 +- doc/man/named-compilezone.1in | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/bin/check/named-checkzone.rst b/bin/check/named-checkzone.rst index 45d07732f0..dae72dcd4d 100644 --- a/bin/check/named-checkzone.rst +++ b/bin/check/named-checkzone.rst @@ -171,7 +171,7 @@ Options ``-W mode`` This option specifies whether to check for non-terminal wildcards. Non-terminal wildcards are almost always the result of a failure to understand the - wildcard matching algorithm (:rfc:`1034`). Possible modes are ``warn`` + wildcard matching algorithm (:rfc:`4592`). Possible modes are ``warn`` (the default) and ``ignore``. ``zonename`` diff --git a/doc/man/named-checkzone.8in b/doc/man/named-checkzone.8in index 74555b1a8f..06ba6966a3 100644 --- a/doc/man/named-checkzone.8in +++ b/doc/man/named-checkzone.8in @@ -179,7 +179,7 @@ This option dumps the zone file in canonical format. .B \fB\-W mode\fP This option specifies whether to check for non\-terminal wildcards. Non\-terminal wildcards are almost always the result of a failure to understand the -wildcard matching algorithm (\fI\%RFC 1034\fP). Possible modes are \fBwarn\fP +wildcard matching algorithm (\fI\%RFC 4592\fP). Possible modes are \fBwarn\fP (the default) and \fBignore\fP\&. .TP .B \fBzonename\fP diff --git a/doc/man/named-compilezone.1in b/doc/man/named-compilezone.1in index 88aa24230f..7635bd07ad 100644 --- a/doc/man/named-compilezone.1in +++ b/doc/man/named-compilezone.1in @@ -181,7 +181,7 @@ This option dumps the zone file in canonical format. This is always enabled for .B \fB\-W mode\fP This option specifies whether to check for non\-terminal wildcards. Non\-terminal wildcards are almost always the result of a failure to understand the -wildcard matching algorithm (\fI\%RFC 1034\fP). Possible modes are \fBwarn\fP +wildcard matching algorithm (\fI\%RFC 4592\fP). Possible modes are \fBwarn\fP (the default) and \fBignore\fP\&. .TP .B \fBzonename\fP