diff --git a/bin/check/named-checkzone.8 b/bin/check/named-checkzone.8
index 6d939b3842..17d4a29c2f 100644
--- a/bin/check/named-checkzone.8
+++ b/bin/check/named-checkzone.8
@@ -13,14 +13,14 @@
.\" OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
.\" PERFORMANCE OF THIS SOFTWARE.
.\"
-.\" $Id: named-checkzone.8,v 1.18.18.3 2004/06/03 04:17:52 marka Exp $
+.\" $Id: named-checkzone.8,v 1.18.18.4 2005/01/10 05:59:15 marka Exp $
.\"
.TH "NAMED-CHECKZONE" "8" "June 13, 2000" "BIND9" ""
.SH NAME
named-checkzone \- zone file validity checking tool
.SH SYNOPSIS
.sp
-\fBnamed-checkzone\fR [ \fB-d\fR ] [ \fB-j\fR ] [ \fB-q\fR ] [ \fB-v\fR ] [ \fB-c \fIclass\fB\fR ] [ \fB-k \fImode\fB\fR ] [ \fB-n \fImode\fB\fR ] [ \fB-o \fIfilename\fB\fR ] [ \fB-t \fIdirectory\fB\fR ] [ \fB-w \fIdirectory\fB\fR ] [ \fB-D\fR ] \fBzonename\fR \fBfilename\fR
+\fBnamed-checkzone\fR [ \fB-d\fR ] [ \fB-j\fR ] [ \fB-q\fR ] [ \fB-v\fR ] [ \fB-c \fIclass\fB\fR ] [ \fB-k \fImode\fB\fR ] [ \fB-n \fImode\fB\fR ] [ \fB-o \fIfilename\fB\fR ] [ \fB-t \fIdirectory\fB\fR ] [ \fB-w \fIdirectory\fB\fR ] [ \fB-D\fR ] [ \fB-W \fImode\fB\fR ] \fBzonename\fR \fBfilename\fR
.SH "DESCRIPTION"
.PP
\fBnamed-checkzone\fR checks the syntax and integrity of
@@ -75,6 +75,13 @@ is similar to the directory clause in
\fB-D\fR
Dump zone file in canonical format.
.TP
+\fB-W \fImode\fB\fR
+Specify 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 \fB"warn"\fR (default) and
+\fB"ignore"\fR.
+.TP
\fBzonename\fR
The domain name of the zone being checked.
.TP
diff --git a/bin/check/named-checkzone.html b/bin/check/named-checkzone.html
index 1813a7576e..2e8bdcb9ba 100644
--- a/bin/check/named-checkzone.html
+++ b/bin/check/named-checkzone.html
@@ -15,7 +15,7 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
-
+
] [-D] [-W mode] {zonename} {filename}
DESCRIPTION
OPTIONS
-W mode
Specify 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" (default) and
+ "ignore".
+
This option is used to check for non-terminal wildcards.
+The use of non-terminal wildcards is almost always as a result of a failure
+to understand the wildcard matching algorithm (RFC 1034). This option
+affects master zones. The default (yes) is to check
+for non-terminal wildcards and issue a warning.
+