named-checkconf \- named configuration file syntax checking tool
.SH SYNOPSIS
.sp
-\fBnamed-checkconf\fR [ \fB-v\fR ] [ \fB-t \fIdirectory\fB\fR ] \fBfilename\fR
+\fBnamed-checkconf\fR [ \fB-v\fR ] [ \fB-t \fIdirectory\fB\fR ] \fBfilename\fR [ \fB-z\fR ]
.SH "DESCRIPTION"
.PP
\fBnamed-checkconf\fR checks the syntax, but not
Print the version of the \fBnamed-checkconf\fR
program and exit.
.TP
+\fB-z\fR
+Perform a check load the master zonefiles found in
+\fInamed.conf\fR.
+.TP
\fBfilename\fR
The name of the configuration file to be checked. If not
specified, it defaults to \fI/etc/named.conf\fR.
>directory</I
></TT
></TT
->] {filename}</P
+>] {filename} [<TT
+CLASS="OPTION"
+>-z</TT
+>]</P
></DIV
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN22"
+NAME="AEN24"
></A
><H2
>DESCRIPTION</H2
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN26"
+NAME="AEN28"
></A
><H2
>OPTIONS</H2
</P
></DD
><DT
+>-z</DT
+><DD
+><P
+> Perform a check load the master zonefiles found in
+ <TT
+CLASS="FILENAME"
+>named.conf</TT
+>.
+ </P
+></DD
+><DT
>filename</DT
><DD
><P
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN45"
+NAME="AEN52"
></A
><H2
>RETURN VALUES</H2
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN49"
+NAME="AEN56"
></A
><H2
>SEE ALSO</H2
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN56"
+NAME="AEN63"
></A
><H2
>AUTHOR</H2
named-checkzone \- zone file validity checking tool
.SH SYNOPSIS
.sp
-\fBnamed-checkzone\fR [ \fB-d\fR ] [ \fB-q\fR ] [ \fB-v\fR ] [ \fB-c \fIclass\fB\fR ] \fBzonename\fR \fBfilename\fR
+\fBnamed-checkzone\fR [ \fB-d\fR ] [ \fB-q\fR ] [ \fB-v\fR ] [ \fB-c \fIclass\fB\fR ] [ \fB-t \fIdirectory\fB\fR ] [ \fB-w \fIdirectory\fB\fR ] \fBzonename\fR \fBfilename\fR
.SH "DESCRIPTION"
.PP
\fBnamed-checkzone\fR checks the syntax and integrity of
\fB-c \fIclass\fB\fR
Specify the class of the zone. If not specified "IN" is assumed.
.TP
+\fB-t \fIdirectory\fB\fR
+chroot to \fIdirectory\fR so that include
+directives in the configuration file are processed as if
+run by a similarly chrooted named.
+.TP
+\fB-w \fIdirectory\fB\fR
+chdir to \fIdirectory\fR so that relative
+filenames in master file $INCLUDE directives work. This
+is similar to the directory clause in
+\fInamed.conf\fR.
+.TP
\fBzonename\fR
The domain name of the zone being checked.
.TP
>class</I
></TT
></TT
+>] [<TT
+CLASS="OPTION"
+>-t <TT
+CLASS="REPLACEABLE"
+><I
+>directory</I
+></TT
+></TT
+>] [<TT
+CLASS="OPTION"
+>-w <TT
+CLASS="REPLACEABLE"
+><I
+>directory</I
+></TT
+></TT
>] {zonename} {filename}</P
></DIV
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN27"
+NAME="AEN33"
></A
><H2
>DESCRIPTION</H2
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN33"
+NAME="AEN39"
></A
><H2
>OPTIONS</H2
</P
></DD
><DT
+>-t <TT
+CLASS="REPLACEABLE"
+><I
+>directory</I
+></TT
+></DT
+><DD
+><P
+> chroot to <TT
+CLASS="FILENAME"
+>directory</TT
+> so that include
+ directives in the configuration file are processed as if
+ run by a similarly chrooted named.
+ </P
+></DD
+><DT
+>-w <TT
+CLASS="REPLACEABLE"
+><I
+>directory</I
+></TT
+></DT
+><DD
+><P
+> chdir to <TT
+CLASS="FILENAME"
+>directory</TT
+> so that relative
+ filenames in master file $INCLUDE directives work. This
+ is similar to the directory clause in
+ <TT
+CLASS="FILENAME"
+>named.conf</TT
+>.
+ </P
+></DD
+><DT
>zonename</DT
><DD
><P
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN62"
+NAME="AEN81"
></A
><H2
>RETURN VALUES</H2
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN66"
+NAME="AEN85"
></A
><H2
>SEE ALSO</H2
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN74"
+NAME="AEN93"
></A
><H2
>AUTHOR</H2
.TP
\fB-p \fIprotocol\fB\fR
Sets the protocol value for the generated key. The protocol
-is a number between 0 and 255. The default is 2 (email) for
-keys of type USER and 3 (DNSSEC) for all other key types.
+is a number between 0 and 255. The default is 3 (DNSSEC).
Other possible values for this argument are listed in
RFC 2535 and its successors.
.TP
><DD
><P
> Sets the protocol value for the generated key. The protocol
- is a number between 0 and 255. The default is 2 (email) for
- keys of type USER and 3 (DNSSEC) for all other key types.
+ is a number between 0 and 255. The default is 3 (DNSSEC).
Other possible values for this argument are listed in
RFC 2535 and its successors.
</P
>Stub zones can also be used as a way of forcing the resolution
of a given domain to use a particular set of authoritative servers.
For example, the caching name servers on a private network using
-RFC2157 addressing may be configured with stub zones for
+RFC1981 addressing may be configured with stub zones for
<TT
CLASS="literal"
>10.in-addr.arpa</TT
min-refresh-time <integer>;
sig-validity-interval <integer>;
zone-statistics <boolean>;
+ key-directory <quoted_string>;
};
controls {
min-refresh-time <integer>;
sig-validity-interval <integer>;
zone-statistics <boolean>;
+ key-directory <quoted_string>;
};
server {
bogus <boolean>;
min-refresh-time <integer>;
sig-validity-interval <integer>;
zone-statistics <boolean>;
+ key-directory <quoted_string>;
};
lwres {
min-refresh-time <integer>;
sig-validity-interval <integer>;
zone-statistics <boolean>;
+ key-directory <quoted_string>;
};
server {