ComputerSurge/bind9
3
0
Fork 0
Code Pull Requests 1 Activity

Refer to RFC 4592 for DNS wildcards

Browse Source 
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 178aef5b8c)
This commit is contained in:
Tony Finch
2022-03-10 18:37:32 +00:00
committed by Petr Špaček
parent da3369179f
commit 1558adbcdf
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
bin/check/named-checkzone.rst
View File

@@ -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``

2
doc/man/named-checkzone.8in
View File

@@ -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

2
doc/man/named-compilezone.1in
View File

@@ -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