mirror of
https://github.com/isc-projects/bind9.git
synced 2026-06-13 19:00:50 -04:00
regen v9_10
This commit is contained in:
Tinderbox User
parent
66ed5cbc11
commit
68db6e5fd2
10 changed files with 1185 additions and 1061 deletions
478
bin/rndc/rndc.8
478
bin/rndc/rndc.8
|
|
@ -1,4 +1,4 @@
|
|||
.\" Copyright (C) 2004, 2005, 2007, 2013, 2014 Internet Systems Consortium, Inc. ("ISC")
|
||||
.\" Copyright (C) 2004, 2005, 2007, 2013-2015 Internet Systems Consortium, Inc. ("ISC")
|
||||
.\" Copyright (C) 2000, 2001 Internet Software Consortium.
|
||||
.\"
|
||||
.\" Permission to use, copy, modify, and/or distribute this software for any
|
||||
|
|
@ -112,7 +112,9 @@ Use the key
|
|||
\fIkey_id\fR
|
||||
from the configuration file.
|
||||
\fIkey_id\fR
|
||||
must be known by named with the same algorithm and secret string in order for control message validation to succeed. If no
|
||||
must be known by
|
||||
\fBnamed\fR
|
||||
with the same algorithm and secret string in order for control message validation to succeed. If no
|
||||
\fIkey_id\fR
|
||||
is specified,
|
||||
\fBrndc\fR
|
||||
|
|
@ -128,222 +130,6 @@ without arguments.
|
|||
.PP
|
||||
Currently supported commands are:
|
||||
.PP
|
||||
\fBreload\fR
|
||||
.RS 4
|
||||
Reload configuration file and zones.
|
||||
.RE
|
||||
.PP
|
||||
\fBreload \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR
|
||||
.RS 4
|
||||
Reload the given zone.
|
||||
.RE
|
||||
.PP
|
||||
\fBrefresh \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR
|
||||
.RS 4
|
||||
Schedule zone maintenance for the given zone.
|
||||
.RE
|
||||
.PP
|
||||
\fBretransfer \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR
|
||||
.RS 4
|
||||
Retransfer the given slave zone from the master server.
|
||||
.sp
|
||||
If the zone is configured to use
|
||||
\fBinline\-signing\fR, the signed version of the zone is discarded; after the retransfer of the unsigned version is complete, the signed version will be regenerated with all new signatures.
|
||||
.RE
|
||||
.PP
|
||||
\fBsign \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR
|
||||
.RS 4
|
||||
Fetch all DNSSEC keys for the given zone from the key directory (see the
|
||||
\fBkey\-directory\fR
|
||||
option in the BIND 9 Administrator Reference Manual). If they are within their publication period, merge them into the zone's DNSKEY RRset. If the DNSKEY RRset is changed, then the zone is automatically re\-signed with the new key set.
|
||||
.sp
|
||||
This command requires that the
|
||||
\fBauto\-dnssec\fR
|
||||
zone option be set to
|
||||
allow
|
||||
or
|
||||
maintain, and also requires the zone to be configured to allow dynamic DNS. (See "Dynamic Update Policies" in the Administrator Reference Manual for more details.)
|
||||
.RE
|
||||
.PP
|
||||
\fBloadkeys \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR
|
||||
.RS 4
|
||||
Fetch all DNSSEC keys for the given zone from the key directory. If they are within their publication period, merge them into the zone's DNSKEY RRset. Unlike
|
||||
\fBrndc sign\fR, however, the zone is not immediately re\-signed by the new keys, but is allowed to incrementally re\-sign over time.
|
||||
.sp
|
||||
This command requires that the
|
||||
\fBauto\-dnssec\fR
|
||||
zone option be set to
|
||||
maintain, and also requires the zone to be configured to allow dynamic DNS. (See "Dynamic Update Policies" in the Administrator Reference Manual for more details.)
|
||||
.RE
|
||||
.PP
|
||||
\fBfreeze \fR\fB[\fIzone\fR [\fIclass\fR [\fIview\fR]]]\fR
|
||||
.RS 4
|
||||
Suspend updates to a dynamic zone. If no zone is specified, then all zones are suspended. This allows manual edits to be made to a zone normally updated by dynamic update. It also causes changes in the journal file to be synced into the master file. All dynamic update attempts will be refused while the zone is frozen.
|
||||
.RE
|
||||
.PP
|
||||
\fBthaw \fR\fB[\fIzone\fR [\fIclass\fR [\fIview\fR]]]\fR
|
||||
.RS 4
|
||||
Enable updates to a frozen dynamic zone. If no zone is specified, then all frozen zones are enabled. This causes the server to reload the zone from disk, and re\-enables dynamic updates after the load has completed. After a zone is thawed, dynamic updates will no longer be refused. If the zone has changed and the
|
||||
\fBixfr\-from\-differences\fR
|
||||
option is in use, then the journal file will be updated to reflect changes in the zone. Otherwise, if the zone has changed, any existing journal file will be removed.
|
||||
.RE
|
||||
.PP
|
||||
\fBscan\fR
|
||||
.RS 4
|
||||
Scan the list of available network interfaces for changes, without performing a full
|
||||
\fBreconfig\fR
|
||||
or waiting for the
|
||||
\fBinterface\-interval\fR
|
||||
timer.
|
||||
.RE
|
||||
.PP
|
||||
\fBsync \fR\fB[\-clean]\fR\fB \fR\fB[\fIzone\fR [\fIclass\fR [\fIview\fR]]]\fR
|
||||
.RS 4
|
||||
Sync changes in the journal file for a dynamic zone to the master file. If the "\-clean" option is specified, the journal file is also removed. If no zone is specified, then all zones are synced.
|
||||
.RE
|
||||
.PP
|
||||
\fBnotify \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR
|
||||
.RS 4
|
||||
Resend NOTIFY messages for the zone.
|
||||
.RE
|
||||
.PP
|
||||
\fBreconfig\fR
|
||||
.RS 4
|
||||
Reload the configuration file and load new zones, but do not reload existing zone files even if they have changed. This is faster than a full
|
||||
\fBreload\fR
|
||||
when there is a large number of zones because it avoids the need to examine the modification times of the zones files.
|
||||
.RE
|
||||
.PP
|
||||
\fBzonestatus \fR\fB[\fIzone\fR [\fIclass\fR [\fIview\fR]]]\fR
|
||||
.RS 4
|
||||
Displays the current status of the given zone, including the master file name and any include files from which it was loaded, when it was most recently loaded, the current serial number, the number of nodes, whether the zone supports dynamic updates, whether the zone is DNSSEC signed, whether it uses automatic DNSSEC key management or inline signing, and the scheduled refresh or expiry times for the zone.
|
||||
.RE
|
||||
.PP
|
||||
\fBstats\fR
|
||||
.RS 4
|
||||
Write server statistics to the statistics file.
|
||||
.RE
|
||||
.PP
|
||||
\fBquerylog\fR [on|off]
|
||||
.RS 4
|
||||
Enable or disable query logging. (For backward compatibility, this command can also be used without an argument to toggle query logging on and off.)
|
||||
.sp
|
||||
Query logging can also be enabled by explicitly directing the
|
||||
\fBqueries\fR
|
||||
\fBcategory\fR
|
||||
to a
|
||||
\fBchannel\fR
|
||||
in the
|
||||
\fBlogging\fR
|
||||
section of
|
||||
\fInamed.conf\fR
|
||||
or by specifying
|
||||
\fBquerylog yes;\fR
|
||||
in the
|
||||
\fBoptions\fR
|
||||
section of
|
||||
\fInamed.conf\fR.
|
||||
.RE
|
||||
.PP
|
||||
\fBdumpdb \fR\fB[\-all|\-cache|\-zone]\fR\fB \fR\fB[\fIview ...\fR]\fR
|
||||
.RS 4
|
||||
Dump the server's caches (default) and/or zones to the dump file for the specified views. If no view is specified, all views are dumped.
|
||||
.RE
|
||||
.PP
|
||||
\fBsecroots \fR\fB[\fIview ...\fR]\fR
|
||||
.RS 4
|
||||
Dump the server's security roots to the secroots file for the specified views. If no view is specified, security roots for all views are dumped.
|
||||
.RE
|
||||
.PP
|
||||
\fBstop \fR\fB[\-p]\fR
|
||||
.RS 4
|
||||
Stop the server, making sure any recent changes made through dynamic update or IXFR are first saved to the master files of the updated zones. If
|
||||
\fB\-p\fR
|
||||
is specified
|
||||
\fBnamed\fR's process id is returned. This allows an external process to determine when
|
||||
\fBnamed\fR
|
||||
had completed stopping.
|
||||
.RE
|
||||
.PP
|
||||
\fBhalt \fR\fB[\-p]\fR
|
||||
.RS 4
|
||||
Stop the server immediately. Recent changes made through dynamic update or IXFR are not saved to the master files, but will be rolled forward from the journal files when the server is restarted. If
|
||||
\fB\-p\fR
|
||||
is specified
|
||||
\fBnamed\fR's process id is returned. This allows an external process to determine when
|
||||
\fBnamed\fR
|
||||
had completed halting.
|
||||
.RE
|
||||
.PP
|
||||
\fBtrace\fR
|
||||
.RS 4
|
||||
Increment the servers debugging level by one.
|
||||
.RE
|
||||
.PP
|
||||
\fBtrace \fR\fB\fIlevel\fR\fR
|
||||
.RS 4
|
||||
Sets the server's debugging level to an explicit value.
|
||||
.RE
|
||||
.PP
|
||||
\fBnotrace\fR
|
||||
.RS 4
|
||||
Sets the server's debugging level to 0.
|
||||
.RE
|
||||
.PP
|
||||
\fBflush\fR
|
||||
.RS 4
|
||||
Flushes the server's cache.
|
||||
.RE
|
||||
.PP
|
||||
\fBflushname\fR \fIname\fR [\fIview\fR]
|
||||
.RS 4
|
||||
Flushes the given name from the server's DNS cache and, if applicable, from the server's nameserver address database or bad\-server cache.
|
||||
.RE
|
||||
.PP
|
||||
\fBflushtree\fR \fIname\fR [\fIview\fR]
|
||||
.RS 4
|
||||
Flushes the given name, and all of its subdomains, from the server's DNS cache, the address database, and the bad server cache.
|
||||
.RE
|
||||
.PP
|
||||
\fBstatus\fR
|
||||
.RS 4
|
||||
Display status of the server. Note that the number of zones includes the internal
|
||||
\fBbind/CH\fR
|
||||
zone and the default
|
||||
\fB./IN\fR
|
||||
hint zone if there is not an explicit root zone configured.
|
||||
.RE
|
||||
.PP
|
||||
\fBrecursing\fR
|
||||
.RS 4
|
||||
Dump the list of queries
|
||||
\fBnamed\fR
|
||||
is currently recursing on.
|
||||
.RE
|
||||
.PP
|
||||
\fBvalidation ( on | off | check ) \fR\fB[\fIview ...\fR]\fR\fB \fR
|
||||
.RS 4
|
||||
Enable, disable, or check the current status of DNSSEC validation. Note
|
||||
\fBdnssec\-enable\fR
|
||||
also needs to be set to
|
||||
\fByes\fR
|
||||
or
|
||||
\fBauto\fR
|
||||
to be effective. It defaults to enabled.
|
||||
.RE
|
||||
.PP
|
||||
\fBtsig\-list\fR
|
||||
.RS 4
|
||||
List the names of all TSIG keys currently configured for use by
|
||||
\fBnamed\fR
|
||||
in each view. The list both statically configured keys and dynamic TKEY\-negotiated keys.
|
||||
.RE
|
||||
.PP
|
||||
\fBtsig\-delete\fR \fIkeyname\fR [\fIview\fR]
|
||||
.RS 4
|
||||
Delete a given TKEY\-negotiated key from the server. (This does not apply to statically configured TSIG keys.)
|
||||
.RE
|
||||
.PP
|
||||
\fBaddzone \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR\fB \fR\fB\fIconfiguration\fR\fR\fB \fR
|
||||
.RS 4
|
||||
Add a zone while the server is running. This command requires the
|
||||
|
|
@ -370,6 +156,11 @@ to the default view:
|
|||
$\fBrndc addzone example.com '{ type master; file "example.com.db"; };'\fR
|
||||
.sp
|
||||
(Note the brackets and semi\-colon around the zone configuration text.)
|
||||
.sp
|
||||
See also
|
||||
\fBrndc delzone\fR
|
||||
and
|
||||
\fBrndc modzone\fR.
|
||||
.RE
|
||||
.PP
|
||||
\fBdelzone \fR\fB[\-clean]\fR\fB \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR\fB \fR
|
||||
|
|
@ -385,6 +176,170 @@ is specified, the zone's master file (and journal file, if any) will be deleted
|
|||
option, zone files must be cleaned up by hand. (If the zone is of type "slave" or "stub", the files needing to be cleaned up will be reported in the output of the
|
||||
\fBrndc delzone\fR
|
||||
command.)
|
||||
.sp
|
||||
See also
|
||||
\fBrndc addzone\fR
|
||||
and
|
||||
\fBrndc modzone\fR.
|
||||
.RE
|
||||
.PP
|
||||
\fBdumpdb \fR\fB[\-all|\-cache|\-zone]\fR\fB \fR\fB[\fIview ...\fR]\fR
|
||||
.RS 4
|
||||
Dump the server's caches (default) and/or zones to the dump file for the specified views. If no view is specified, all views are dumped. (See the
|
||||
\fBdump\-file\fR
|
||||
option in the BIND 9 Administrator Reference Manual.)
|
||||
.RE
|
||||
.PP
|
||||
\fBflush\fR
|
||||
.RS 4
|
||||
Flushes the server's cache.
|
||||
.RE
|
||||
.PP
|
||||
\fBflushname\fR \fIname\fR [\fIview\fR]
|
||||
.RS 4
|
||||
Flushes the given name from the server's DNS cache and, if applicable, from the server's nameserver address database or bad\-server cache.
|
||||
.RE
|
||||
.PP
|
||||
\fBflushtree\fR \fIname\fR [\fIview\fR]
|
||||
.RS 4
|
||||
Flushes the given name, and all of its subdomains, from the server's DNS cache, the address database, and the bad server cache.
|
||||
.RE
|
||||
.PP
|
||||
\fBfreeze \fR\fB[\fIzone\fR [\fIclass\fR [\fIview\fR]]]\fR
|
||||
.RS 4
|
||||
Suspend updates to a dynamic zone. If no zone is specified, then all zones are suspended. This allows manual edits to be made to a zone normally updated by dynamic update. It also causes changes in the journal file to be synced into the master file. All dynamic update attempts will be refused while the zone is frozen.
|
||||
.sp
|
||||
See also
|
||||
\fBrndc thaw\fR.
|
||||
.RE
|
||||
.PP
|
||||
\fBhalt \fR\fB[\-p]\fR
|
||||
.RS 4
|
||||
Stop the server immediately. Recent changes made through dynamic update or IXFR are not saved to the master files, but will be rolled forward from the journal files when the server is restarted. If
|
||||
\fB\-p\fR
|
||||
is specified
|
||||
\fBnamed\fR's process id is returned. This allows an external process to determine when
|
||||
\fBnamed\fR
|
||||
had completed halting.
|
||||
.sp
|
||||
See also
|
||||
\fBrndc stop\fR.
|
||||
.RE
|
||||
.PP
|
||||
\fBloadkeys \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR
|
||||
.RS 4
|
||||
Fetch all DNSSEC keys for the given zone from the key directory. If they are within their publication period, merge them into the zone's DNSKEY RRset. Unlike
|
||||
\fBrndc sign\fR, however, the zone is not immediately re\-signed by the new keys, but is allowed to incrementally re\-sign over time.
|
||||
.sp
|
||||
This command requires that the
|
||||
\fBauto\-dnssec\fR
|
||||
zone option be set to
|
||||
maintain, and also requires the zone to be configured to allow dynamic DNS. (See "Dynamic Update Policies" in the Administrator Reference Manual for more details.)
|
||||
.sp
|
||||
See also
|
||||
\fBrndc loadkeys\fR.
|
||||
.RE
|
||||
.PP
|
||||
\fBnotify \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR
|
||||
.RS 4
|
||||
Resend NOTIFY messages for the zone.
|
||||
.RE
|
||||
.PP
|
||||
\fBnotrace\fR
|
||||
.RS 4
|
||||
Sets the server's debugging level to 0.
|
||||
.sp
|
||||
See also
|
||||
\fBrndc trace\fR.
|
||||
.RE
|
||||
.PP
|
||||
\fBquerylog\fR [on|off]
|
||||
.RS 4
|
||||
Enable or disable query logging. (For backward compatibility, this command can also be used without an argument to toggle query logging on and off.)
|
||||
.sp
|
||||
Query logging can also be enabled by explicitly directing the
|
||||
\fBqueries\fR
|
||||
\fBcategory\fR
|
||||
to a
|
||||
\fBchannel\fR
|
||||
in the
|
||||
\fBlogging\fR
|
||||
section of
|
||||
\fInamed.conf\fR
|
||||
or by specifying
|
||||
\fBquerylog yes;\fR
|
||||
in the
|
||||
\fBoptions\fR
|
||||
section of
|
||||
\fInamed.conf\fR.
|
||||
.RE
|
||||
.PP
|
||||
\fBreconfig\fR
|
||||
.RS 4
|
||||
Reload the configuration file and load new zones, but do not reload existing zone files even if they have changed. This is faster than a full
|
||||
\fBreload\fR
|
||||
when there is a large number of zones because it avoids the need to examine the modification times of the zones files.
|
||||
.RE
|
||||
.PP
|
||||
\fBrecursing\fR
|
||||
.RS 4
|
||||
Dump the list of queries
|
||||
\fBnamed\fR
|
||||
is currently recursing on.
|
||||
.RE
|
||||
.PP
|
||||
\fBrefresh \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR
|
||||
.RS 4
|
||||
Schedule zone maintenance for the given zone.
|
||||
.RE
|
||||
.PP
|
||||
\fBreload\fR
|
||||
.RS 4
|
||||
Reload configuration file and zones.
|
||||
.RE
|
||||
.PP
|
||||
\fBreload \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR
|
||||
.RS 4
|
||||
Reload the given zone.
|
||||
.RE
|
||||
.PP
|
||||
\fBretransfer \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR
|
||||
.RS 4
|
||||
Retransfer the given slave zone from the master server.
|
||||
.sp
|
||||
If the zone is configured to use
|
||||
\fBinline\-signing\fR, the signed version of the zone is discarded; after the retransfer of the unsigned version is complete, the signed version will be regenerated with all new signatures.
|
||||
.RE
|
||||
.PP
|
||||
\fBscan\fR
|
||||
.RS 4
|
||||
Scan the list of available network interfaces for changes, without performing a full
|
||||
\fBreconfig\fR
|
||||
or waiting for the
|
||||
\fBinterface\-interval\fR
|
||||
timer.
|
||||
.RE
|
||||
.PP
|
||||
\fBsecroots \fR\fB[\fIview ...\fR]\fR
|
||||
.RS 4
|
||||
Dump the server's security roots to the secroots file for the specified views. If no view is specified, security roots for all views are dumped.
|
||||
.RE
|
||||
.PP
|
||||
\fBsign \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR
|
||||
.RS 4
|
||||
Fetch all DNSSEC keys for the given zone from the key directory (see the
|
||||
\fBkey\-directory\fR
|
||||
option in the BIND 9 Administrator Reference Manual). If they are within their publication period, merge them into the zone's DNSKEY RRset. If the DNSKEY RRset is changed, then the zone is automatically re\-signed with the new key set.
|
||||
.sp
|
||||
This command requires that the
|
||||
\fBauto\-dnssec\fR
|
||||
zone option be set to
|
||||
allow
|
||||
or
|
||||
maintain, and also requires the zone to be configured to allow dynamic DNS. (See "Dynamic Update Policies" in the Administrator Reference Manual for more details.)
|
||||
.sp
|
||||
See also
|
||||
\fBrndc loadkeys\fR.
|
||||
.RE
|
||||
.PP
|
||||
\fBsigning \fR\fB[( \-list | \-clear \fIkeyid/algorithm\fR | \-clear all | \-nsec3param ( \fIparameters\fR | none ) ) ]\fR\fB \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR\fB \fR
|
||||
|
|
@ -426,6 +381,91 @@ So, for example, to create an NSEC3 chain using the SHA\-1 hash algorithm, no op
|
|||
\fBrndc signing \-nsec3param none\fR
|
||||
removes an existing NSEC3 chain and replaces it with NSEC.
|
||||
.RE
|
||||
.PP
|
||||
\fBstats\fR
|
||||
.RS 4
|
||||
Write server statistics to the statistics file. (See the
|
||||
\fBstatistics\-file\fR
|
||||
option in the BIND 9 Administrator Reference Manual.)
|
||||
.RE
|
||||
.PP
|
||||
\fBstatus\fR
|
||||
.RS 4
|
||||
Display status of the server. Note that the number of zones includes the internal
|
||||
\fBbind/CH\fR
|
||||
zone and the default
|
||||
\fB./IN\fR
|
||||
hint zone if there is not an explicit root zone configured.
|
||||
.RE
|
||||
.PP
|
||||
\fBstop \fR\fB[\-p]\fR
|
||||
.RS 4
|
||||
Stop the server, making sure any recent changes made through dynamic update or IXFR are first saved to the master files of the updated zones. If
|
||||
\fB\-p\fR
|
||||
is specified
|
||||
\fBnamed\fR's process id is returned. This allows an external process to determine when
|
||||
\fBnamed\fR
|
||||
had completed stopping.
|
||||
.sp
|
||||
See also
|
||||
\fBrndc halt\fR.
|
||||
.RE
|
||||
.PP
|
||||
\fBsync \fR\fB[\-clean]\fR\fB \fR\fB[\fIzone\fR [\fIclass\fR [\fIview\fR]]]\fR
|
||||
.RS 4
|
||||
Sync changes in the journal file for a dynamic zone to the master file. If the "\-clean" option is specified, the journal file is also removed. If no zone is specified, then all zones are synced.
|
||||
.RE
|
||||
.PP
|
||||
\fBthaw \fR\fB[\fIzone\fR [\fIclass\fR [\fIview\fR]]]\fR
|
||||
.RS 4
|
||||
Enable updates to a frozen dynamic zone. If no zone is specified, then all frozen zones are enabled. This causes the server to reload the zone from disk, and re\-enables dynamic updates after the load has completed. After a zone is thawed, dynamic updates will no longer be refused. If the zone has changed and the
|
||||
\fBixfr\-from\-differences\fR
|
||||
option is in use, then the journal file will be updated to reflect changes in the zone. Otherwise, if the zone has changed, any existing journal file will be removed.
|
||||
.sp
|
||||
See also
|
||||
\fBrndc freeze\fR.
|
||||
.RE
|
||||
.PP
|
||||
\fBtrace\fR
|
||||
.RS 4
|
||||
Increment the servers debugging level by one.
|
||||
.RE
|
||||
.PP
|
||||
\fBtrace \fR\fB\fIlevel\fR\fR
|
||||
.RS 4
|
||||
Sets the server's debugging level to an explicit value.
|
||||
.sp
|
||||
See also
|
||||
\fBrndc notrace\fR.
|
||||
.RE
|
||||
.PP
|
||||
\fBtsig\-delete\fR \fIkeyname\fR [\fIview\fR]
|
||||
.RS 4
|
||||
Delete a given TKEY\-negotiated key from the server. (This does not apply to statically configured TSIG keys.)
|
||||
.RE
|
||||
.PP
|
||||
\fBtsig\-list\fR
|
||||
.RS 4
|
||||
List the names of all TSIG keys currently configured for use by
|
||||
\fBnamed\fR
|
||||
in each view. The list both statically configured keys and dynamic TKEY\-negotiated keys.
|
||||
.RE
|
||||
.PP
|
||||
\fBvalidation ( on | off | check ) \fR\fB[\fIview ...\fR]\fR\fB \fR
|
||||
.RS 4
|
||||
Enable, disable, or check the current status of DNSSEC validation. Note
|
||||
\fBdnssec\-enable\fR
|
||||
also needs to be set to
|
||||
\fByes\fR
|
||||
or
|
||||
\fBauto\fR
|
||||
to be effective. It defaults to enabled.
|
||||
.RE
|
||||
.PP
|
||||
\fBzonestatus \fR\fB[\fIzone\fR [\fIclass\fR [\fIview\fR]]]\fR
|
||||
.RS 4
|
||||
Displays the current status of the given zone, including the master file name and any include files from which it was loaded, when it was most recently loaded, the current serial number, the number of nodes, whether the zone supports dynamic updates, whether the zone is DNSSEC signed, whether it uses automatic DNSSEC key management or inline signing, and the scheduled refresh or expiry times for the zone.
|
||||
.RE
|
||||
.SH "LIMITATIONS"
|
||||
.PP
|
||||
There is currently no way to provide the shared secret for a
|
||||
|
|
@ -445,7 +485,7 @@ BIND 9 Administrator Reference Manual.
|
|||
.PP
|
||||
Internet Systems Consortium
|
||||
.SH "COPYRIGHT"
|
||||
Copyright \(co 2004, 2005, 2007, 2013, 2014 Internet Systems Consortium, Inc. ("ISC")
|
||||
Copyright \(co 2004, 2005, 2007, 2013\-2015 Internet Systems Consortium, Inc. ("ISC")
|
||||
.br
|
||||
Copyright \(co 2000, 2001 Internet Software Consortium.
|
||||
.br
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
<!--
|
||||
- Copyright (C) 2004, 2005, 2007, 2013, 2014 Internet Systems Consortium, Inc. ("ISC")
|
||||
- Copyright (C) 2004, 2005, 2007, 2013-2015 Internet Systems Consortium, Inc. ("ISC")
|
||||
- Copyright (C) 2000, 2001 Internet Software Consortium.
|
||||
-
|
||||
- Permission to use, copy, modify, and/or distribute this software for any
|
||||
|
|
@ -32,7 +32,7 @@
|
|||
<div class="cmdsynopsis"><p><code class="command">rndc</code> [<code class="option">-b <em class="replaceable"><code>source-address</code></em></code>] [<code class="option">-c <em class="replaceable"><code>config-file</code></em></code>] [<code class="option">-k <em class="replaceable"><code>key-file</code></em></code>] [<code class="option">-s <em class="replaceable"><code>server</code></em></code>] [<code class="option">-p <em class="replaceable"><code>port</code></em></code>] [<code class="option">-q</code>] [<code class="option">-V</code>] [<code class="option">-y <em class="replaceable"><code>key_id</code></em></code>] {command}</p></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2543432"></a><h2>DESCRIPTION</h2>
|
||||
<a name="id2543435"></a><h2>DESCRIPTION</h2>
|
||||
<p><span><strong class="command">rndc</strong></span>
|
||||
controls the operation of a name
|
||||
server. It supersedes the <span><strong class="command">ndc</strong></span> utility
|
||||
|
|
@ -63,78 +63,78 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2543467"></a><h2>OPTIONS</h2>
|
||||
<a name="id2543470"></a><h2>OPTIONS</h2>
|
||||
<div class="variablelist"><dl>
|
||||
<dt><span class="term">-b <em class="replaceable"><code>source-address</code></em></span></dt>
|
||||
<dd><p>
|
||||
Use <em class="replaceable"><code>source-address</code></em>
|
||||
as the source address for the connection to the server.
|
||||
Multiple instances are permitted to allow setting of both
|
||||
the IPv4 and IPv6 source addresses.
|
||||
</p></dd>
|
||||
Use <em class="replaceable"><code>source-address</code></em>
|
||||
as the source address for the connection to the server.
|
||||
Multiple instances are permitted to allow setting of both
|
||||
the IPv4 and IPv6 source addresses.
|
||||
</p></dd>
|
||||
<dt><span class="term">-c <em class="replaceable"><code>config-file</code></em></span></dt>
|
||||
<dd><p>
|
||||
Use <em class="replaceable"><code>config-file</code></em>
|
||||
as the configuration file instead of the default,
|
||||
<code class="filename">/etc/rndc.conf</code>.
|
||||
</p></dd>
|
||||
Use <em class="replaceable"><code>config-file</code></em>
|
||||
as the configuration file instead of the default,
|
||||
<code class="filename">/etc/rndc.conf</code>.
|
||||
</p></dd>
|
||||
<dt><span class="term">-k <em class="replaceable"><code>key-file</code></em></span></dt>
|
||||
<dd><p>
|
||||
Use <em class="replaceable"><code>key-file</code></em>
|
||||
as the key file instead of the default,
|
||||
<code class="filename">/etc/rndc.key</code>. The key in
|
||||
<code class="filename">/etc/rndc.key</code> will be used to
|
||||
authenticate
|
||||
commands sent to the server if the <em class="replaceable"><code>config-file</code></em>
|
||||
does not exist.
|
||||
</p></dd>
|
||||
Use <em class="replaceable"><code>key-file</code></em>
|
||||
as the key file instead of the default,
|
||||
<code class="filename">/etc/rndc.key</code>. The key in
|
||||
<code class="filename">/etc/rndc.key</code> will be used to
|
||||
authenticate
|
||||
commands sent to the server if the <em class="replaceable"><code>config-file</code></em>
|
||||
does not exist.
|
||||
</p></dd>
|
||||
<dt><span class="term">-s <em class="replaceable"><code>server</code></em></span></dt>
|
||||
<dd><p><em class="replaceable"><code>server</code></em> is
|
||||
the name or address of the server which matches a
|
||||
server statement in the configuration file for
|
||||
<span><strong class="command">rndc</strong></span>. If no server is supplied on the
|
||||
command line, the host named by the default-server clause
|
||||
in the options statement of the <span><strong class="command">rndc</strong></span>
|
||||
configuration file will be used.
|
||||
</p></dd>
|
||||
the name or address of the server which matches a
|
||||
server statement in the configuration file for
|
||||
<span><strong class="command">rndc</strong></span>. If no server is supplied on the
|
||||
command line, the host named by the default-server clause
|
||||
in the options statement of the <span><strong class="command">rndc</strong></span>
|
||||
configuration file will be used.
|
||||
</p></dd>
|
||||
<dt><span class="term">-p <em class="replaceable"><code>port</code></em></span></dt>
|
||||
<dd><p>
|
||||
Send commands to TCP port
|
||||
<em class="replaceable"><code>port</code></em>
|
||||
instead
|
||||
of BIND 9's default control channel port, 953.
|
||||
</p></dd>
|
||||
Send commands to TCP port
|
||||
<em class="replaceable"><code>port</code></em>
|
||||
instead
|
||||
of BIND 9's default control channel port, 953.
|
||||
</p></dd>
|
||||
<dt><span class="term">-q</span></dt>
|
||||
<dd><p>
|
||||
Quiet mode: Message text returned by the server
|
||||
will not be printed except when there is an error.
|
||||
</p></dd>
|
||||
Quiet mode: Message text returned by the server
|
||||
will not be printed except when there is an error.
|
||||
</p></dd>
|
||||
<dt><span class="term">-V</span></dt>
|
||||
<dd><p>
|
||||
Enable verbose logging.
|
||||
</p></dd>
|
||||
Enable verbose logging.
|
||||
</p></dd>
|
||||
<dt><span class="term">-y <em class="replaceable"><code>key_id</code></em></span></dt>
|
||||
<dd><p>
|
||||
Use the key <em class="replaceable"><code>key_id</code></em>
|
||||
from the configuration file.
|
||||
<em class="replaceable"><code>key_id</code></em>
|
||||
must be
|
||||
known by named with the same algorithm and secret string
|
||||
in order for control message validation to succeed.
|
||||
If no <em class="replaceable"><code>key_id</code></em>
|
||||
is specified, <span><strong class="command">rndc</strong></span> will first look
|
||||
for a key clause in the server statement of the server
|
||||
being used, or if no server statement is present for that
|
||||
host, then the default-key clause of the options statement.
|
||||
Note that the configuration file contains shared secrets
|
||||
which are used to send authenticated control commands
|
||||
to name servers. It should therefore not have general read
|
||||
or write access.
|
||||
</p></dd>
|
||||
Use the key <em class="replaceable"><code>key_id</code></em>
|
||||
from the configuration file.
|
||||
<em class="replaceable"><code>key_id</code></em>
|
||||
must be
|
||||
known by <span><strong class="command">named</strong></span> with the same algorithm and secret string
|
||||
in order for control message validation to succeed.
|
||||
If no <em class="replaceable"><code>key_id</code></em>
|
||||
is specified, <span><strong class="command">rndc</strong></span> will first look
|
||||
for a key clause in the server statement of the server
|
||||
being used, or if no server statement is present for that
|
||||
host, then the default-key clause of the options statement.
|
||||
Note that the configuration file contains shared secrets
|
||||
which are used to send authenticated control commands
|
||||
to name servers. It should therefore not have general read
|
||||
or write access.
|
||||
</p></dd>
|
||||
</dl></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2543676"></a><h2>COMMANDS</h2>
|
||||
<a name="id2543684"></a><h2>COMMANDS</h2>
|
||||
<p>
|
||||
A list of commands supported by <span><strong class="command">rndc</strong></span> can
|
||||
be seen by running <span><strong class="command">rndc</strong></span> without arguments.
|
||||
|
|
@ -143,383 +143,425 @@
|
|||
Currently supported commands are:
|
||||
</p>
|
||||
<div class="variablelist"><dl>
|
||||
<dt><span class="term"><strong class="userinput"><code>reload</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Reload configuration file and zones.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>reload <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Reload the given zone.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>refresh <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Schedule zone maintenance for the given zone.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>retransfer <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Retransfer the given slave zone from the master server.
|
||||
</p>
|
||||
<p>
|
||||
If the zone is configured to use
|
||||
<span><strong class="command">inline-signing</strong></span>, the signed
|
||||
version of the zone is discarded; after the
|
||||
retransfer of the unsigned version is complete, the
|
||||
signed version will be regenerated with all new
|
||||
signatures.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>sign <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Fetch all DNSSEC keys for the given zone
|
||||
from the key directory (see the
|
||||
<span><strong class="command">key-directory</strong></span> option in
|
||||
the BIND 9 Administrator Reference Manual). If they are within
|
||||
their publication period, merge them into the
|
||||
zone's DNSKEY RRset. If the DNSKEY RRset
|
||||
is changed, then the zone is automatically
|
||||
re-signed with the new key set.
|
||||
</p>
|
||||
<p>
|
||||
This command requires that the
|
||||
<span><strong class="command">auto-dnssec</strong></span> zone option be set
|
||||
to <code class="literal">allow</code> or
|
||||
<code class="literal">maintain</code>,
|
||||
and also requires the zone to be configured to
|
||||
allow dynamic DNS.
|
||||
(See "Dynamic Update Policies" in the Administrator
|
||||
Reference Manual for more details.)
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>loadkeys <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Fetch all DNSSEC keys for the given zone
|
||||
from the key directory. If they are within
|
||||
their publication period, merge them into the
|
||||
zone's DNSKEY RRset. Unlike <span><strong class="command">rndc
|
||||
sign</strong></span>, however, the zone is not
|
||||
immediately re-signed by the new keys, but is
|
||||
allowed to incrementally re-sign over time.
|
||||
</p>
|
||||
<p>
|
||||
This command requires that the
|
||||
<span><strong class="command">auto-dnssec</strong></span> zone option
|
||||
be set to <code class="literal">maintain</code>,
|
||||
and also requires the zone to be configured to
|
||||
allow dynamic DNS.
|
||||
(See "Dynamic Update Policies" in the Administrator
|
||||
Reference Manual for more details.)
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>freeze [<span class="optional"><em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Suspend updates to a dynamic zone. If no zone is
|
||||
specified, then all zones are suspended. This allows
|
||||
manual edits to be made to a zone normally updated by
|
||||
dynamic update. It also causes changes in the
|
||||
journal file to be synced into the master file.
|
||||
All dynamic update attempts will be refused while
|
||||
the zone is frozen.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>thaw [<span class="optional"><em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Enable updates to a frozen dynamic zone. If no
|
||||
zone is specified, then all frozen zones are
|
||||
enabled. This causes the server to reload the zone
|
||||
from disk, and re-enables dynamic updates after the
|
||||
load has completed. After a zone is thawed,
|
||||
dynamic updates will no longer be refused. If
|
||||
the zone has changed and the
|
||||
<span><strong class="command">ixfr-from-differences</strong></span> option is
|
||||
in use, then the journal file will be updated to
|
||||
reflect changes in the zone. Otherwise, if the
|
||||
zone has changed, any existing journal file will be
|
||||
removed.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>scan</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Scan the list of available network interfaces
|
||||
for changes, without performing a full
|
||||
<span><strong class="command">reconfig</strong></span> or waiting for the
|
||||
<span><strong class="command">interface-interval</strong></span> timer.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>sync [<span class="optional">-clean</span>] [<span class="optional"><em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Sync changes in the journal file for a dynamic zone
|
||||
to the master file. If the "-clean" option is
|
||||
specified, the journal file is also removed. If
|
||||
no zone is specified, then all zones are synced.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>notify <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Resend NOTIFY messages for the zone.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>reconfig</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Reload the configuration file and load new zones,
|
||||
but do not reload existing zone files even if they
|
||||
have changed.
|
||||
This is faster than a full <span><strong class="command">reload</strong></span> when there
|
||||
is a large number of zones because it avoids the need
|
||||
to examine the
|
||||
modification times of the zones files.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>zonestatus [<span class="optional"><em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Displays the current status of the given zone,
|
||||
including the master file name and any include
|
||||
files from which it was loaded, when it was most
|
||||
recently loaded, the current serial number, the
|
||||
number of nodes, whether the zone supports
|
||||
dynamic updates, whether the zone is DNSSEC
|
||||
signed, whether it uses automatic DNSSEC key
|
||||
management or inline signing, and the scheduled
|
||||
refresh or expiry times for the zone.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>stats</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Write server statistics to the statistics file.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>querylog</code></strong> [<span class="optional">on|off</span>] </span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Enable or disable query logging. (For backward
|
||||
compatibility, this command can also be used without
|
||||
an argument to toggle query logging on and off.)
|
||||
</p>
|
||||
<p>
|
||||
Query logging can also be enabled
|
||||
by explicitly directing the <span><strong class="command">queries</strong></span>
|
||||
<span><strong class="command">category</strong></span> to a
|
||||
<span><strong class="command">channel</strong></span> in the
|
||||
<span><strong class="command">logging</strong></span> section of
|
||||
<code class="filename">named.conf</code> or by specifying
|
||||
<span><strong class="command">querylog yes;</strong></span> in the
|
||||
<span><strong class="command">options</strong></span> section of
|
||||
<code class="filename">named.conf</code>.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>dumpdb [<span class="optional">-all|-cache|-zone</span>] [<span class="optional"><em class="replaceable"><code>view ...</code></em></span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Dump the server's caches (default) and/or zones to
|
||||
the
|
||||
dump file for the specified views. If no view is
|
||||
specified, all
|
||||
views are dumped.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>secroots [<span class="optional"><em class="replaceable"><code>view ...</code></em></span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Dump the server's security roots to the secroots
|
||||
file for the specified views. If no view is
|
||||
specified, security roots for all
|
||||
views are dumped.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>stop [<span class="optional">-p</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Stop the server, making sure any recent changes
|
||||
made through dynamic update or IXFR are first saved to
|
||||
the master files of the updated zones.
|
||||
If <code class="option">-p</code> is specified <span><strong class="command">named</strong></span>'s process id is returned.
|
||||
This allows an external process to determine when <span><strong class="command">named</strong></span>
|
||||
had completed stopping.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>halt [<span class="optional">-p</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Stop the server immediately. Recent changes
|
||||
made through dynamic update or IXFR are not saved to
|
||||
the master files, but will be rolled forward from the
|
||||
journal files when the server is restarted.
|
||||
If <code class="option">-p</code> is specified <span><strong class="command">named</strong></span>'s process id is returned.
|
||||
This allows an external process to determine when <span><strong class="command">named</strong></span>
|
||||
had completed halting.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>trace</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Increment the servers debugging level by one.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>trace <em class="replaceable"><code>level</code></em></code></strong></span></dt>
|
||||
<dd><p>
|
||||
Sets the server's debugging level to an explicit
|
||||
value.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>notrace</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Sets the server's debugging level to 0.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>flush</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Flushes the server's cache.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>flushname</code></strong> <em class="replaceable"><code>name</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>] </span></dt>
|
||||
<dd><p>
|
||||
Flushes the given name from the server's DNS cache
|
||||
and, if applicable, from the server's nameserver address
|
||||
database or bad-server cache.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>flushtree</code></strong> <em class="replaceable"><code>name</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>] </span></dt>
|
||||
<dd><p>
|
||||
Flushes the given name, and all of its subdomains,
|
||||
from the server's DNS cache, the address database,
|
||||
and the bad server cache.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>status</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Display status of the server.
|
||||
Note that the number of zones includes the internal <span><strong class="command">bind/CH</strong></span> zone
|
||||
and the default <span><strong class="command">./IN</strong></span>
|
||||
hint zone if there is not an
|
||||
explicit root zone configured.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>recursing</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Dump the list of queries <span><strong class="command">named</strong></span> is currently recursing
|
||||
on.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>validation ( on | off | check ) [<span class="optional"><em class="replaceable"><code>view ...</code></em></span>] </code></strong></span></dt>
|
||||
<dd><p>
|
||||
Enable, disable, or check the current status of
|
||||
DNSSEC validation.
|
||||
Note <span><strong class="command">dnssec-enable</strong></span> also needs to be
|
||||
set to <strong class="userinput"><code>yes</code></strong> or
|
||||
<strong class="userinput"><code>auto</code></strong> to be effective.
|
||||
It defaults to enabled.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>tsig-list</code></strong></span></dt>
|
||||
<dd><p>
|
||||
List the names of all TSIG keys currently configured
|
||||
for use by <span><strong class="command">named</strong></span> in each view. The
|
||||
list both statically configured keys and dynamic
|
||||
TKEY-negotiated keys.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>tsig-delete</code></strong> <em class="replaceable"><code>keyname</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span></dt>
|
||||
<dd><p>
|
||||
Delete a given TKEY-negotiated key from the server.
|
||||
(This does not apply to statically configured TSIG
|
||||
keys.)
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>addzone <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>] <em class="replaceable"><code>configuration</code></em> </code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Add a zone while the server is running. This
|
||||
command requires the
|
||||
<span><strong class="command">allow-new-zones</strong></span> option to be set
|
||||
to <strong class="userinput"><code>yes</code></strong>. The
|
||||
<em class="replaceable"><code>configuration</code></em> string
|
||||
specified on the command line is the zone
|
||||
configuration text that would ordinarily be
|
||||
placed in <code class="filename">named.conf</code>.
|
||||
</p>
|
||||
Add a zone while the server is running. This
|
||||
command requires the
|
||||
<span><strong class="command">allow-new-zones</strong></span> option to be set
|
||||
to <strong class="userinput"><code>yes</code></strong>. The
|
||||
<em class="replaceable"><code>configuration</code></em> string
|
||||
specified on the command line is the zone
|
||||
configuration text that would ordinarily be
|
||||
placed in <code class="filename">named.conf</code>.
|
||||
</p>
|
||||
<p>
|
||||
The configuration is saved in a file called
|
||||
<code class="filename"><em class="replaceable"><code>hash</code></em>.nzf</code>,
|
||||
where <em class="replaceable"><code>hash</code></em> is a
|
||||
cryptographic hash generated from the name of
|
||||
the view. When <span><strong class="command">named</strong></span> is
|
||||
restarted, the file will be loaded into the view
|
||||
configuration, so that zones that were added
|
||||
can persist after a restart.
|
||||
</p>
|
||||
The configuration is saved in a file called
|
||||
<code class="filename"><em class="replaceable"><code>hash</code></em>.nzf</code>,
|
||||
where <em class="replaceable"><code>hash</code></em> is a
|
||||
cryptographic hash generated from the name of
|
||||
the view. When <span><strong class="command">named</strong></span> is
|
||||
restarted, the file will be loaded into the view
|
||||
configuration, so that zones that were added
|
||||
can persist after a restart.
|
||||
</p>
|
||||
<p>
|
||||
This sample <span><strong class="command">addzone</strong></span> command
|
||||
would add the zone <code class="literal">example.com</code>
|
||||
to the default view:
|
||||
</p>
|
||||
This sample <span><strong class="command">addzone</strong></span> command
|
||||
would add the zone <code class="literal">example.com</code>
|
||||
to the default view:
|
||||
</p>
|
||||
<p>
|
||||
<code class="prompt">$ </code><strong class="userinput"><code>rndc addzone example.com '{ type master; file "example.com.db"; };'</code></strong>
|
||||
</p>
|
||||
</p>
|
||||
<p>
|
||||
(Note the brackets and semi-colon around the zone
|
||||
configuration text.)
|
||||
</p>
|
||||
(Note the brackets and semi-colon around the zone
|
||||
configuration text.)
|
||||
</p>
|
||||
<p>
|
||||
See also <span><strong class="command">rndc delzone</strong></span> and <span><strong class="command">rndc modzone</strong></span>.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>delzone [<span class="optional">-clean</span>] <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>] </code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Delete a zone while the server is running.
|
||||
Only zones that were originally added via
|
||||
<span><strong class="command">rndc addzone</strong></span> can be deleted
|
||||
in this manner.
|
||||
</p>
|
||||
Delete a zone while the server is running.
|
||||
Only zones that were originally added via
|
||||
<span><strong class="command">rndc addzone</strong></span> can be deleted
|
||||
in this manner.
|
||||
</p>
|
||||
<p>
|
||||
If the <code class="option">-clean</code> is specified,
|
||||
the zone's master file (and journal file, if any)
|
||||
will be deleted along with the zone. Without the
|
||||
<code class="option">-clean</code> option, zone files must
|
||||
be cleaned up by hand. (If the zone is of
|
||||
type "slave" or "stub", the files needing to
|
||||
be cleaned up will be reported in the output
|
||||
of the <span><strong class="command">rndc delzone</strong></span> command.)
|
||||
</p>
|
||||
If the <code class="option">-clean</code> is specified,
|
||||
the zone's master file (and journal file, if any)
|
||||
will be deleted along with the zone. Without the
|
||||
<code class="option">-clean</code> option, zone files must
|
||||
be cleaned up by hand. (If the zone is of
|
||||
type "slave" or "stub", the files needing to
|
||||
be cleaned up will be reported in the output
|
||||
of the <span><strong class="command">rndc delzone</strong></span> command.)
|
||||
</p>
|
||||
<p>
|
||||
See also <span><strong class="command">rndc addzone</strong></span> and <span><strong class="command">rndc modzone</strong></span>.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>dumpdb [<span class="optional">-all|-cache|-zone</span>] [<span class="optional"><em class="replaceable"><code>view ...</code></em></span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Dump the server's caches (default) and/or zones to
|
||||
the
|
||||
dump file for the specified views. If no view is
|
||||
specified, all
|
||||
views are dumped.
|
||||
(See the <span><strong class="command">dump-file</strong></span> option in
|
||||
the BIND 9 Administrator Reference Manual.)
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>flush</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Flushes the server's cache.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>flushname</code></strong> <em class="replaceable"><code>name</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>] </span></dt>
|
||||
<dd><p>
|
||||
Flushes the given name from the server's DNS cache
|
||||
and, if applicable, from the server's nameserver address
|
||||
database or bad-server cache.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>flushtree</code></strong> <em class="replaceable"><code>name</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>] </span></dt>
|
||||
<dd><p>
|
||||
Flushes the given name, and all of its subdomains,
|
||||
from the server's DNS cache, the address database,
|
||||
and the bad server cache.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>freeze [<span class="optional"><em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</span>]</code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Suspend updates to a dynamic zone. If no zone is
|
||||
specified, then all zones are suspended. This allows
|
||||
manual edits to be made to a zone normally updated by
|
||||
dynamic update. It also causes changes in the
|
||||
journal file to be synced into the master file.
|
||||
All dynamic update attempts will be refused while
|
||||
the zone is frozen.
|
||||
</p>
|
||||
<p>
|
||||
See also <span><strong class="command">rndc thaw</strong></span>.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>halt [<span class="optional">-p</span>]</code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Stop the server immediately. Recent changes
|
||||
made through dynamic update or IXFR are not saved to
|
||||
the master files, but will be rolled forward from the
|
||||
journal files when the server is restarted.
|
||||
If <code class="option">-p</code> is specified <span><strong class="command">named</strong></span>'s process id is returned.
|
||||
This allows an external process to determine when <span><strong class="command">named</strong></span>
|
||||
had completed halting.
|
||||
</p>
|
||||
<p>
|
||||
See also <span><strong class="command">rndc stop</strong></span>.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>loadkeys <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Fetch all DNSSEC keys for the given zone
|
||||
from the key directory. If they are within
|
||||
their publication period, merge them into the
|
||||
zone's DNSKEY RRset. Unlike <span><strong class="command">rndc
|
||||
sign</strong></span>, however, the zone is not
|
||||
immediately re-signed by the new keys, but is
|
||||
allowed to incrementally re-sign over time.
|
||||
</p>
|
||||
<p>
|
||||
This command requires that the
|
||||
<span><strong class="command">auto-dnssec</strong></span> zone option
|
||||
be set to <code class="literal">maintain</code>,
|
||||
and also requires the zone to be configured to
|
||||
allow dynamic DNS.
|
||||
(See "Dynamic Update Policies" in the Administrator
|
||||
Reference Manual for more details.)
|
||||
</p>
|
||||
<p>
|
||||
See also <span><strong class="command">rndc loadkeys</strong></span>.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>notify <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Resend NOTIFY messages for the zone.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>notrace</code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Sets the server's debugging level to 0.
|
||||
</p>
|
||||
<p>
|
||||
See also <span><strong class="command">rndc trace</strong></span>.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>querylog</code></strong> [<span class="optional">on|off</span>] </span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Enable or disable query logging. (For backward
|
||||
compatibility, this command can also be used without
|
||||
an argument to toggle query logging on and off.)
|
||||
</p>
|
||||
<p>
|
||||
Query logging can also be enabled
|
||||
by explicitly directing the <span><strong class="command">queries</strong></span>
|
||||
<span><strong class="command">category</strong></span> to a
|
||||
<span><strong class="command">channel</strong></span> in the
|
||||
<span><strong class="command">logging</strong></span> section of
|
||||
<code class="filename">named.conf</code> or by specifying
|
||||
<span><strong class="command">querylog yes;</strong></span> in the
|
||||
<span><strong class="command">options</strong></span> section of
|
||||
<code class="filename">named.conf</code>.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>reconfig</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Reload the configuration file and load new zones,
|
||||
but do not reload existing zone files even if they
|
||||
have changed.
|
||||
This is faster than a full <span><strong class="command">reload</strong></span> when there
|
||||
is a large number of zones because it avoids the need
|
||||
to examine the
|
||||
modification times of the zones files.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>recursing</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Dump the list of queries <span><strong class="command">named</strong></span> is currently recursing
|
||||
on.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>refresh <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Schedule zone maintenance for the given zone.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>reload</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Reload configuration file and zones.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>reload <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Reload the given zone.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>retransfer <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Retransfer the given slave zone from the master server.
|
||||
</p>
|
||||
<p>
|
||||
If the zone is configured to use
|
||||
<span><strong class="command">inline-signing</strong></span>, the signed
|
||||
version of the zone is discarded; after the
|
||||
retransfer of the unsigned version is complete, the
|
||||
signed version will be regenerated with all new
|
||||
signatures.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>scan</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Scan the list of available network interfaces
|
||||
for changes, without performing a full
|
||||
<span><strong class="command">reconfig</strong></span> or waiting for the
|
||||
<span><strong class="command">interface-interval</strong></span> timer.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>secroots [<span class="optional"><em class="replaceable"><code>view ...</code></em></span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Dump the server's security roots to the secroots
|
||||
file for the specified views. If no view is
|
||||
specified, security roots for all
|
||||
views are dumped.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>sign <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Fetch all DNSSEC keys for the given zone
|
||||
from the key directory (see the
|
||||
<span><strong class="command">key-directory</strong></span> option in
|
||||
the BIND 9 Administrator Reference Manual). If they are within
|
||||
their publication period, merge them into the
|
||||
zone's DNSKEY RRset. If the DNSKEY RRset
|
||||
is changed, then the zone is automatically
|
||||
re-signed with the new key set.
|
||||
</p>
|
||||
<p>
|
||||
This command requires that the
|
||||
<span><strong class="command">auto-dnssec</strong></span> zone option be set
|
||||
to <code class="literal">allow</code> or
|
||||
<code class="literal">maintain</code>,
|
||||
and also requires the zone to be configured to
|
||||
allow dynamic DNS.
|
||||
(See "Dynamic Update Policies" in the Administrator
|
||||
Reference Manual for more details.)
|
||||
</p>
|
||||
<p>
|
||||
See also <span><strong class="command">rndc loadkeys</strong></span>.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>signing [<span class="optional">( -list | -clear <em class="replaceable"><code>keyid/algorithm</code></em> | -clear <code class="literal">all</code> | -nsec3param ( <em class="replaceable"><code>parameters</code></em> | <code class="literal">none</code> ) ) </span>] <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>] </code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
List, edit, or remove the DNSSEC signing state records
|
||||
for the specified zone. The status of ongoing DNSSEC
|
||||
operations (such as signing or generating
|
||||
NSEC3 chains) is stored in the zone in the form
|
||||
of DNS resource records of type
|
||||
<span><strong class="command">sig-signing-type</strong></span>.
|
||||
<span><strong class="command">rndc signing -list</strong></span> converts
|
||||
these records into a human-readable form,
|
||||
indicating which keys are currently signing
|
||||
or have finished signing the zone, and which NSEC3
|
||||
chains are being created or removed.
|
||||
</p>
|
||||
List, edit, or remove the DNSSEC signing state records
|
||||
for the specified zone. The status of ongoing DNSSEC
|
||||
operations (such as signing or generating
|
||||
NSEC3 chains) is stored in the zone in the form
|
||||
of DNS resource records of type
|
||||
<span><strong class="command">sig-signing-type</strong></span>.
|
||||
<span><strong class="command">rndc signing -list</strong></span> converts
|
||||
these records into a human-readable form,
|
||||
indicating which keys are currently signing
|
||||
or have finished signing the zone, and which NSEC3
|
||||
chains are being created or removed.
|
||||
</p>
|
||||
<p>
|
||||
<span><strong class="command">rndc signing -clear</strong></span> can remove
|
||||
a single key (specified in the same format that
|
||||
<span><strong class="command">rndc signing -list</strong></span> uses to
|
||||
display it), or all keys. In either case, only
|
||||
completed keys are removed; any record indicating
|
||||
that a key has not yet finished signing the zone
|
||||
will be retained.
|
||||
</p>
|
||||
<span><strong class="command">rndc signing -clear</strong></span> can remove
|
||||
a single key (specified in the same format that
|
||||
<span><strong class="command">rndc signing -list</strong></span> uses to
|
||||
display it), or all keys. In either case, only
|
||||
completed keys are removed; any record indicating
|
||||
that a key has not yet finished signing the zone
|
||||
will be retained.
|
||||
</p>
|
||||
<p>
|
||||
<span><strong class="command">rndc signing -nsec3param</strong></span> sets
|
||||
the NSEC3 parameters for a zone. This is the
|
||||
only supported mechanism for using NSEC3 with
|
||||
<span><strong class="command">inline-signing</strong></span> zones.
|
||||
Parameters are specified in the same format as
|
||||
an NSEC3PARAM resource record: hash algorithm,
|
||||
flags, iterations, and salt, in that order.
|
||||
</p>
|
||||
<span><strong class="command">rndc signing -nsec3param</strong></span> sets
|
||||
the NSEC3 parameters for a zone. This is the
|
||||
only supported mechanism for using NSEC3 with
|
||||
<span><strong class="command">inline-signing</strong></span> zones.
|
||||
Parameters are specified in the same format as
|
||||
an NSEC3PARAM resource record: hash algorithm,
|
||||
flags, iterations, and salt, in that order.
|
||||
</p>
|
||||
<p>
|
||||
Currently, the only defined value for hash algorithm
|
||||
is <code class="literal">1</code>, representing SHA-1.
|
||||
The <code class="option">flags</code> may be set to
|
||||
<code class="literal">0</code> or <code class="literal">1</code>,
|
||||
depending on whether you wish to set the opt-out
|
||||
bit in the NSEC3 chain. <code class="option">iterations</code>
|
||||
defines the number of additional times to apply
|
||||
the algorithm when generating an NSEC3 hash. The
|
||||
<code class="option">salt</code> is a string of data expressed
|
||||
in hexadecimal, a hyphen (`-') if no salt is
|
||||
to be used, or the keyword <code class="literal">auto</code>,
|
||||
which causes <span><strong class="command">named</strong></span> to generate a
|
||||
random 64-bit salt.
|
||||
</p>
|
||||
Currently, the only defined value for hash algorithm
|
||||
is <code class="literal">1</code>, representing SHA-1.
|
||||
The <code class="option">flags</code> may be set to
|
||||
<code class="literal">0</code> or <code class="literal">1</code>,
|
||||
depending on whether you wish to set the opt-out
|
||||
bit in the NSEC3 chain. <code class="option">iterations</code>
|
||||
defines the number of additional times to apply
|
||||
the algorithm when generating an NSEC3 hash. The
|
||||
<code class="option">salt</code> is a string of data expressed
|
||||
in hexadecimal, a hyphen (`-') if no salt is
|
||||
to be used, or the keyword <code class="literal">auto</code>,
|
||||
which causes <span><strong class="command">named</strong></span> to generate a
|
||||
random 64-bit salt.
|
||||
</p>
|
||||
<p>
|
||||
So, for example, to create an NSEC3 chain using
|
||||
the SHA-1 hash algorithm, no opt-out flag,
|
||||
10 iterations, and a salt value of "FFFF", use:
|
||||
<span><strong class="command">rndc signing -nsec3param 1 0 10 FFFF <em class="replaceable"><code>zone</code></em></strong></span>.
|
||||
To set the opt-out flag, 15 iterations, and no
|
||||
salt, use:
|
||||
<span><strong class="command">rndc signing -nsec3param 1 1 15 - <em class="replaceable"><code>zone</code></em></strong></span>.
|
||||
</p>
|
||||
So, for example, to create an NSEC3 chain using
|
||||
the SHA-1 hash algorithm, no opt-out flag,
|
||||
10 iterations, and a salt value of "FFFF", use:
|
||||
<span><strong class="command">rndc signing -nsec3param 1 0 10 FFFF <em class="replaceable"><code>zone</code></em></strong></span>.
|
||||
To set the opt-out flag, 15 iterations, and no
|
||||
salt, use:
|
||||
<span><strong class="command">rndc signing -nsec3param 1 1 15 - <em class="replaceable"><code>zone</code></em></strong></span>.
|
||||
</p>
|
||||
<p>
|
||||
<span><strong class="command">rndc signing -nsec3param none</strong></span>
|
||||
removes an existing NSEC3 chain and replaces it
|
||||
with NSEC.
|
||||
</p>
|
||||
<span><strong class="command">rndc signing -nsec3param none</strong></span>
|
||||
removes an existing NSEC3 chain and replaces it
|
||||
with NSEC.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>stats</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Write server statistics to the statistics file.
|
||||
(See the <span><strong class="command">statistics-file</strong></span> option in
|
||||
the BIND 9 Administrator Reference Manual.)
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>status</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Display status of the server.
|
||||
Note that the number of zones includes the internal <span><strong class="command">bind/CH</strong></span> zone
|
||||
and the default <span><strong class="command">./IN</strong></span>
|
||||
hint zone if there is not an
|
||||
explicit root zone configured.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>stop [<span class="optional">-p</span>]</code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Stop the server, making sure any recent changes
|
||||
made through dynamic update or IXFR are first saved to
|
||||
the master files of the updated zones.
|
||||
If <code class="option">-p</code> is specified <span><strong class="command">named</strong></span>'s process id is returned.
|
||||
This allows an external process to determine when <span><strong class="command">named</strong></span>
|
||||
had completed stopping.
|
||||
</p>
|
||||
<p>See also <span><strong class="command">rndc halt</strong></span>.</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>sync [<span class="optional">-clean</span>] [<span class="optional"><em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Sync changes in the journal file for a dynamic zone
|
||||
to the master file. If the "-clean" option is
|
||||
specified, the journal file is also removed. If
|
||||
no zone is specified, then all zones are synced.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>thaw [<span class="optional"><em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</span>]</code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Enable updates to a frozen dynamic zone. If no
|
||||
zone is specified, then all frozen zones are
|
||||
enabled. This causes the server to reload the zone
|
||||
from disk, and re-enables dynamic updates after the
|
||||
load has completed. After a zone is thawed,
|
||||
dynamic updates will no longer be refused. If
|
||||
the zone has changed and the
|
||||
<span><strong class="command">ixfr-from-differences</strong></span> option is
|
||||
in use, then the journal file will be updated to
|
||||
reflect changes in the zone. Otherwise, if the
|
||||
zone has changed, any existing journal file will be
|
||||
removed.
|
||||
</p>
|
||||
<p>See also <span><strong class="command">rndc freeze</strong></span>.</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>trace</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Increment the servers debugging level by one.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>trace <em class="replaceable"><code>level</code></em></code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Sets the server's debugging level to an explicit
|
||||
value.
|
||||
</p>
|
||||
<p>
|
||||
See also <span><strong class="command">rndc notrace</strong></span>.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>tsig-delete</code></strong> <em class="replaceable"><code>keyname</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span></dt>
|
||||
<dd><p>
|
||||
Delete a given TKEY-negotiated key from the server.
|
||||
(This does not apply to statically configured TSIG
|
||||
keys.)
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>tsig-list</code></strong></span></dt>
|
||||
<dd><p>
|
||||
List the names of all TSIG keys currently configured
|
||||
for use by <span><strong class="command">named</strong></span> in each view. The
|
||||
list both statically configured keys and dynamic
|
||||
TKEY-negotiated keys.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>validation ( on | off | check ) [<span class="optional"><em class="replaceable"><code>view ...</code></em></span>] </code></strong></span></dt>
|
||||
<dd><p>
|
||||
Enable, disable, or check the current status of
|
||||
DNSSEC validation.
|
||||
Note <span><strong class="command">dnssec-enable</strong></span> also needs to be
|
||||
set to <strong class="userinput"><code>yes</code></strong> or
|
||||
<strong class="userinput"><code>auto</code></strong> to be effective.
|
||||
It defaults to enabled.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>zonestatus [<span class="optional"><em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Displays the current status of the given zone,
|
||||
including the master file name and any include
|
||||
files from which it was loaded, when it was most
|
||||
recently loaded, the current serial number, the
|
||||
number of nodes, whether the zone supports
|
||||
dynamic updates, whether the zone is DNSSEC
|
||||
signed, whether it uses automatic DNSSEC key
|
||||
management or inline signing, and the scheduled
|
||||
refresh or expiry times for the zone.
|
||||
</p></dd>
|
||||
</dl></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2542002"></a><h2>LIMITATIONS</h2>
|
||||
<a name="id2545086"></a><h2>LIMITATIONS</h2>
|
||||
<p>
|
||||
There is currently no way to provide the shared secret for a
|
||||
<code class="option">key_id</code> without using the configuration file.
|
||||
|
|
@ -529,7 +571,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2542020"></a><h2>SEE ALSO</h2>
|
||||
<a name="id2545105"></a><h2>SEE ALSO</h2>
|
||||
<p><span class="citerefentry"><span class="refentrytitle">rndc.conf</span>(5)</span>,
|
||||
<span class="citerefentry"><span class="refentrytitle">rndc-confgen</span>(8)</span>,
|
||||
<span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
|
||||
|
|
@ -539,7 +581,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2545420"></a><h2>AUTHOR</h2>
|
||||
<a name="id2545160"></a><h2>AUTHOR</h2>
|
||||
<p><span class="corpauthor">Internet Systems Consortium</span>
|
||||
</p>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -50,20 +50,20 @@
|
|||
<div class="cmdsynopsis"><p><code class="command">arpaname</code> {<em class="replaceable"><code>ipaddress </code></em>...}</p></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2622813"></a><h2>DESCRIPTION</h2>
|
||||
<a name="id2622858"></a><h2>DESCRIPTION</h2>
|
||||
<p>
|
||||
<span><strong class="command">arpaname</strong></span> translates IP addresses (IPv4 and
|
||||
IPv6) to the corresponding IN-ADDR.ARPA or IP6.ARPA names.
|
||||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2622828"></a><h2>SEE ALSO</h2>
|
||||
<a name="id2663492"></a><h2>SEE ALSO</h2>
|
||||
<p>
|
||||
<em class="citetitle">BIND 9 Administrator Reference Manual</em>.
|
||||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2622842"></a><h2>AUTHOR</h2>
|
||||
<a name="id2663506"></a><h2>AUTHOR</h2>
|
||||
<p><span class="corpauthor">Internet Systems Consortium</span>
|
||||
</p>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -51,7 +51,7 @@
|
|||
<div class="cmdsynopsis"><p><code class="command">ddns-confgen</code> [<code class="option">-a <em class="replaceable"><code>algorithm</code></em></code>] [<code class="option">-h</code>] [<code class="option">-k <em class="replaceable"><code>keyname</code></em></code>] [<code class="option">-q</code>] [<code class="option">-r <em class="replaceable"><code>randomfile</code></em></code>] [ -s <em class="replaceable"><code>name</code></em> | -z <em class="replaceable"><code>zone</code></em> ]</p></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2662747"></a><h2>DESCRIPTION</h2>
|
||||
<a name="id2662792"></a><h2>DESCRIPTION</h2>
|
||||
<p>
|
||||
<span><strong class="command">tsig-keygen</strong></span> and <span><strong class="command">ddns-confgen</strong></span>
|
||||
are invocation methods for a utility that generates keys for use
|
||||
|
|
@ -87,7 +87,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2662851"></a><h2>OPTIONS</h2>
|
||||
<a name="id2663100"></a><h2>OPTIONS</h2>
|
||||
<div class="variablelist"><dl>
|
||||
<dt><span class="term">-a <em class="replaceable"><code>algorithm</code></em></span></dt>
|
||||
<dd><p>
|
||||
|
|
@ -159,7 +159,7 @@
|
|||
</dl></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2663272"></a><h2>SEE ALSO</h2>
|
||||
<a name="id2663317"></a><h2>SEE ALSO</h2>
|
||||
<p><span class="citerefentry"><span class="refentrytitle">nsupdate</span>(1)</span>,
|
||||
<span class="citerefentry"><span class="refentrytitle">named.conf</span>(5)</span>,
|
||||
<span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
|
||||
|
|
@ -167,7 +167,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2663310"></a><h2>AUTHOR</h2>
|
||||
<a name="id2663424"></a><h2>AUTHOR</h2>
|
||||
<p><span class="corpauthor">Internet Systems Consortium</span>
|
||||
</p>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -50,7 +50,7 @@
|
|||
<div class="cmdsynopsis"><p><code class="command">genrandom</code> [<code class="option">-n <em class="replaceable"><code>number</code></em></code>] {<em class="replaceable"><code>size</code></em>} {<em class="replaceable"><code>filename</code></em>}</p></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2622939"></a><h2>DESCRIPTION</h2>
|
||||
<a name="id2622916"></a><h2>DESCRIPTION</h2>
|
||||
<p>
|
||||
<span><strong class="command">genrandom</strong></span>
|
||||
generates a file or a set of files containing a specified quantity
|
||||
|
|
@ -59,7 +59,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2663368"></a><h2>ARGUMENTS</h2>
|
||||
<a name="id2622931"></a><h2>ARGUMENTS</h2>
|
||||
<div class="variablelist"><dl>
|
||||
<dt><span class="term">-n <em class="replaceable"><code>number</code></em></span></dt>
|
||||
<dd><p>
|
||||
|
|
@ -77,14 +77,14 @@
|
|||
</dl></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2663497"></a><h2>SEE ALSO</h2>
|
||||
<a name="id2663952"></a><h2>SEE ALSO</h2>
|
||||
<p>
|
||||
<span class="citerefentry"><span class="refentrytitle">rand</span>(3)</span>,
|
||||
<span class="citerefentry"><span class="refentrytitle">arc4random</span>(3)</span>
|
||||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2663524"></a><h2>AUTHOR</h2>
|
||||
<a name="id2663978"></a><h2>AUTHOR</h2>
|
||||
<p><span class="corpauthor">Internet Systems Consortium</span>
|
||||
</p>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -50,7 +50,7 @@
|
|||
<div class="cmdsynopsis"><p><code class="command">isc-hmac-fixup</code> {<em class="replaceable"><code>algorithm</code></em>} {<em class="replaceable"><code>secret</code></em>}</p></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2663922"></a><h2>DESCRIPTION</h2>
|
||||
<a name="id2623143"></a><h2>DESCRIPTION</h2>
|
||||
<p>
|
||||
Versions of BIND 9 up to and including BIND 9.6 had a bug causing
|
||||
HMAC-SHA* TSIG keys which were longer than the digest length of the
|
||||
|
|
@ -76,7 +76,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2663949"></a><h2>SECURITY CONSIDERATIONS</h2>
|
||||
<a name="id2664472"></a><h2>SECURITY CONSIDERATIONS</h2>
|
||||
<p>
|
||||
Secrets that have been converted by <span><strong class="command">isc-hmac-fixup</strong></span>
|
||||
are shortened, but as this is how the HMAC protocol works in
|
||||
|
|
@ -87,14 +87,14 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2663965"></a><h2>SEE ALSO</h2>
|
||||
<a name="id2664488"></a><h2>SEE ALSO</h2>
|
||||
<p>
|
||||
<em class="citetitle">BIND 9 Administrator Reference Manual</em>,
|
||||
<em class="citetitle">RFC 2104</em>.
|
||||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2663982"></a><h2>AUTHOR</h2>
|
||||
<a name="id2664505"></a><h2>AUTHOR</h2>
|
||||
<p><span class="corpauthor">Internet Systems Consortium</span>
|
||||
</p>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -48,7 +48,7 @@
|
|||
<div class="cmdsynopsis"><p><code class="command">nsec3hash</code> {<em class="replaceable"><code>salt</code></em>} {<em class="replaceable"><code>algorithm</code></em>} {<em class="replaceable"><code>iterations</code></em>} {<em class="replaceable"><code>domain</code></em>}</p></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2623204"></a><h2>DESCRIPTION</h2>
|
||||
<a name="id2664618"></a><h2>DESCRIPTION</h2>
|
||||
<p>
|
||||
<span><strong class="command">nsec3hash</strong></span> generates an NSEC3 hash based on
|
||||
a set of NSEC3 parameters. This can be used to check the validity
|
||||
|
|
@ -56,7 +56,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2664452"></a><h2>ARGUMENTS</h2>
|
||||
<a name="id2664633"></a><h2>ARGUMENTS</h2>
|
||||
<div class="variablelist"><dl>
|
||||
<dt><span class="term">salt</span></dt>
|
||||
<dd><p>
|
||||
|
|
@ -80,14 +80,14 @@
|
|||
</dl></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2664514"></a><h2>SEE ALSO</h2>
|
||||
<a name="id2664763"></a><h2>SEE ALSO</h2>
|
||||
<p>
|
||||
<em class="citetitle">BIND 9 Administrator Reference Manual</em>,
|
||||
<em class="citetitle">RFC 5155</em>.
|
||||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2664531"></a><h2>AUTHOR</h2>
|
||||
<a name="id2664780"></a><h2>AUTHOR</h2>
|
||||
<p><span class="corpauthor">Internet Systems Consortium</span>
|
||||
</p>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -50,7 +50,7 @@
|
|||
<div class="cmdsynopsis"><p><code class="command">rndc-confgen</code> [<code class="option">-a</code>] [<code class="option">-A <em class="replaceable"><code>algorithm</code></em></code>] [<code class="option">-b <em class="replaceable"><code>keysize</code></em></code>] [<code class="option">-c <em class="replaceable"><code>keyfile</code></em></code>] [<code class="option">-h</code>] [<code class="option">-k <em class="replaceable"><code>keyname</code></em></code>] [<code class="option">-p <em class="replaceable"><code>port</code></em></code>] [<code class="option">-r <em class="replaceable"><code>randomfile</code></em></code>] [<code class="option">-s <em class="replaceable"><code>address</code></em></code>] [<code class="option">-t <em class="replaceable"><code>chrootdir</code></em></code>] [<code class="option">-u <em class="replaceable"><code>user</code></em></code>]</p></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2660952"></a><h2>DESCRIPTION</h2>
|
||||
<a name="id2661065"></a><h2>DESCRIPTION</h2>
|
||||
<p><span><strong class="command">rndc-confgen</strong></span>
|
||||
generates configuration files
|
||||
for <span><strong class="command">rndc</strong></span>. It can be used as a
|
||||
|
|
@ -66,7 +66,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2661018"></a><h2>OPTIONS</h2>
|
||||
<a name="id2661131"></a><h2>OPTIONS</h2>
|
||||
<div class="variablelist"><dl>
|
||||
<dt><span class="term">-a</span></dt>
|
||||
<dd>
|
||||
|
|
@ -180,7 +180,7 @@
|
|||
</dl></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2663742"></a><h2>EXAMPLES</h2>
|
||||
<a name="id2662217"></a><h2>EXAMPLES</h2>
|
||||
<p>
|
||||
To allow <span><strong class="command">rndc</strong></span> to be used with
|
||||
no manual configuration, run
|
||||
|
|
@ -197,7 +197,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2663799"></a><h2>SEE ALSO</h2>
|
||||
<a name="id2663844"></a><h2>SEE ALSO</h2>
|
||||
<p><span class="citerefentry"><span class="refentrytitle">rndc</span>(8)</span>,
|
||||
<span class="citerefentry"><span class="refentrytitle">rndc.conf</span>(5)</span>,
|
||||
<span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
|
||||
|
|
@ -205,7 +205,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2663837"></a><h2>AUTHOR</h2>
|
||||
<a name="id2663882"></a><h2>AUTHOR</h2>
|
||||
<p><span class="corpauthor">Internet Systems Consortium</span>
|
||||
</p>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -50,7 +50,7 @@
|
|||
<div class="cmdsynopsis"><p><code class="command">rndc.conf</code> </p></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2622186"></a><h2>DESCRIPTION</h2>
|
||||
<a name="id2622163"></a><h2>DESCRIPTION</h2>
|
||||
<p><code class="filename">rndc.conf</code> is the configuration file
|
||||
for <span><strong class="command">rndc</strong></span>, the BIND 9 name server control
|
||||
utility. This file has a similar structure and syntax to
|
||||
|
|
@ -136,7 +136,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2659290"></a><h2>EXAMPLE</h2>
|
||||
<a name="id2660496"></a><h2>EXAMPLE</h2>
|
||||
<pre class="programlisting">
|
||||
options {
|
||||
default-server localhost;
|
||||
|
|
@ -210,7 +210,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2660368"></a><h2>NAME SERVER CONFIGURATION</h2>
|
||||
<a name="id2660617"></a><h2>NAME SERVER CONFIGURATION</h2>
|
||||
<p>
|
||||
The name server must be configured to accept rndc connections and
|
||||
to recognize the key specified in the <code class="filename">rndc.conf</code>
|
||||
|
|
@ -220,7 +220,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2660393"></a><h2>SEE ALSO</h2>
|
||||
<a name="id2660779"></a><h2>SEE ALSO</h2>
|
||||
<p><span class="citerefentry"><span class="refentrytitle">rndc</span>(8)</span>,
|
||||
<span class="citerefentry"><span class="refentrytitle">rndc-confgen</span>(8)</span>,
|
||||
<span class="citerefentry"><span class="refentrytitle">mmencode</span>(1)</span>,
|
||||
|
|
@ -228,7 +228,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2660432"></a><h2>AUTHOR</h2>
|
||||
<a name="id2660818"></a><h2>AUTHOR</h2>
|
||||
<p><span class="corpauthor">Internet Systems Consortium</span>
|
||||
</p>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -50,7 +50,7 @@
|
|||
<div class="cmdsynopsis"><p><code class="command">rndc</code> [<code class="option">-b <em class="replaceable"><code>source-address</code></em></code>] [<code class="option">-c <em class="replaceable"><code>config-file</code></em></code>] [<code class="option">-k <em class="replaceable"><code>key-file</code></em></code>] [<code class="option">-s <em class="replaceable"><code>server</code></em></code>] [<code class="option">-p <em class="replaceable"><code>port</code></em></code>] [<code class="option">-q</code>] [<code class="option">-V</code>] [<code class="option">-y <em class="replaceable"><code>key_id</code></em></code>] {command}</p></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2655201"></a><h2>DESCRIPTION</h2>
|
||||
<a name="id2655180"></a><h2>DESCRIPTION</h2>
|
||||
<p><span><strong class="command">rndc</strong></span>
|
||||
controls the operation of a name
|
||||
server. It supersedes the <span><strong class="command">ndc</strong></span> utility
|
||||
|
|
@ -81,78 +81,78 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2655251"></a><h2>OPTIONS</h2>
|
||||
<a name="id2655230"></a><h2>OPTIONS</h2>
|
||||
<div class="variablelist"><dl>
|
||||
<dt><span class="term">-b <em class="replaceable"><code>source-address</code></em></span></dt>
|
||||
<dd><p>
|
||||
Use <em class="replaceable"><code>source-address</code></em>
|
||||
as the source address for the connection to the server.
|
||||
Multiple instances are permitted to allow setting of both
|
||||
the IPv4 and IPv6 source addresses.
|
||||
</p></dd>
|
||||
Use <em class="replaceable"><code>source-address</code></em>
|
||||
as the source address for the connection to the server.
|
||||
Multiple instances are permitted to allow setting of both
|
||||
the IPv4 and IPv6 source addresses.
|
||||
</p></dd>
|
||||
<dt><span class="term">-c <em class="replaceable"><code>config-file</code></em></span></dt>
|
||||
<dd><p>
|
||||
Use <em class="replaceable"><code>config-file</code></em>
|
||||
as the configuration file instead of the default,
|
||||
<code class="filename">/etc/rndc.conf</code>.
|
||||
</p></dd>
|
||||
Use <em class="replaceable"><code>config-file</code></em>
|
||||
as the configuration file instead of the default,
|
||||
<code class="filename">/etc/rndc.conf</code>.
|
||||
</p></dd>
|
||||
<dt><span class="term">-k <em class="replaceable"><code>key-file</code></em></span></dt>
|
||||
<dd><p>
|
||||
Use <em class="replaceable"><code>key-file</code></em>
|
||||
as the key file instead of the default,
|
||||
<code class="filename">/etc/rndc.key</code>. The key in
|
||||
<code class="filename">/etc/rndc.key</code> will be used to
|
||||
authenticate
|
||||
commands sent to the server if the <em class="replaceable"><code>config-file</code></em>
|
||||
does not exist.
|
||||
</p></dd>
|
||||
Use <em class="replaceable"><code>key-file</code></em>
|
||||
as the key file instead of the default,
|
||||
<code class="filename">/etc/rndc.key</code>. The key in
|
||||
<code class="filename">/etc/rndc.key</code> will be used to
|
||||
authenticate
|
||||
commands sent to the server if the <em class="replaceable"><code>config-file</code></em>
|
||||
does not exist.
|
||||
</p></dd>
|
||||
<dt><span class="term">-s <em class="replaceable"><code>server</code></em></span></dt>
|
||||
<dd><p><em class="replaceable"><code>server</code></em> is
|
||||
the name or address of the server which matches a
|
||||
server statement in the configuration file for
|
||||
<span><strong class="command">rndc</strong></span>. If no server is supplied on the
|
||||
command line, the host named by the default-server clause
|
||||
in the options statement of the <span><strong class="command">rndc</strong></span>
|
||||
configuration file will be used.
|
||||
</p></dd>
|
||||
the name or address of the server which matches a
|
||||
server statement in the configuration file for
|
||||
<span><strong class="command">rndc</strong></span>. If no server is supplied on the
|
||||
command line, the host named by the default-server clause
|
||||
in the options statement of the <span><strong class="command">rndc</strong></span>
|
||||
configuration file will be used.
|
||||
</p></dd>
|
||||
<dt><span class="term">-p <em class="replaceable"><code>port</code></em></span></dt>
|
||||
<dd><p>
|
||||
Send commands to TCP port
|
||||
<em class="replaceable"><code>port</code></em>
|
||||
instead
|
||||
of BIND 9's default control channel port, 953.
|
||||
</p></dd>
|
||||
Send commands to TCP port
|
||||
<em class="replaceable"><code>port</code></em>
|
||||
instead
|
||||
of BIND 9's default control channel port, 953.
|
||||
</p></dd>
|
||||
<dt><span class="term">-q</span></dt>
|
||||
<dd><p>
|
||||
Quiet mode: Message text returned by the server
|
||||
will not be printed except when there is an error.
|
||||
</p></dd>
|
||||
Quiet mode: Message text returned by the server
|
||||
will not be printed except when there is an error.
|
||||
</p></dd>
|
||||
<dt><span class="term">-V</span></dt>
|
||||
<dd><p>
|
||||
Enable verbose logging.
|
||||
</p></dd>
|
||||
Enable verbose logging.
|
||||
</p></dd>
|
||||
<dt><span class="term">-y <em class="replaceable"><code>key_id</code></em></span></dt>
|
||||
<dd><p>
|
||||
Use the key <em class="replaceable"><code>key_id</code></em>
|
||||
from the configuration file.
|
||||
<em class="replaceable"><code>key_id</code></em>
|
||||
must be
|
||||
known by named with the same algorithm and secret string
|
||||
in order for control message validation to succeed.
|
||||
If no <em class="replaceable"><code>key_id</code></em>
|
||||
is specified, <span><strong class="command">rndc</strong></span> will first look
|
||||
for a key clause in the server statement of the server
|
||||
being used, or if no server statement is present for that
|
||||
host, then the default-key clause of the options statement.
|
||||
Note that the configuration file contains shared secrets
|
||||
which are used to send authenticated control commands
|
||||
to name servers. It should therefore not have general read
|
||||
or write access.
|
||||
</p></dd>
|
||||
Use the key <em class="replaceable"><code>key_id</code></em>
|
||||
from the configuration file.
|
||||
<em class="replaceable"><code>key_id</code></em>
|
||||
must be
|
||||
known by <span><strong class="command">named</strong></span> with the same algorithm and secret string
|
||||
in order for control message validation to succeed.
|
||||
If no <em class="replaceable"><code>key_id</code></em>
|
||||
is specified, <span><strong class="command">rndc</strong></span> will first look
|
||||
for a key clause in the server statement of the server
|
||||
being used, or if no server statement is present for that
|
||||
host, then the default-key clause of the options statement.
|
||||
Note that the configuration file contains shared secrets
|
||||
which are used to send authenticated control commands
|
||||
to name servers. It should therefore not have general read
|
||||
or write access.
|
||||
</p></dd>
|
||||
</dl></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2655541"></a><h2>COMMANDS</h2>
|
||||
<a name="id2655527"></a><h2>COMMANDS</h2>
|
||||
<p>
|
||||
A list of commands supported by <span><strong class="command">rndc</strong></span> can
|
||||
be seen by running <span><strong class="command">rndc</strong></span> without arguments.
|
||||
|
|
@ -161,383 +161,425 @@
|
|||
Currently supported commands are:
|
||||
</p>
|
||||
<div class="variablelist"><dl>
|
||||
<dt><span class="term"><strong class="userinput"><code>reload</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Reload configuration file and zones.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>reload <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Reload the given zone.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>refresh <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Schedule zone maintenance for the given zone.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>retransfer <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Retransfer the given slave zone from the master server.
|
||||
</p>
|
||||
<p>
|
||||
If the zone is configured to use
|
||||
<span><strong class="command">inline-signing</strong></span>, the signed
|
||||
version of the zone is discarded; after the
|
||||
retransfer of the unsigned version is complete, the
|
||||
signed version will be regenerated with all new
|
||||
signatures.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>sign <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Fetch all DNSSEC keys for the given zone
|
||||
from the key directory (see the
|
||||
<span><strong class="command">key-directory</strong></span> option in
|
||||
the BIND 9 Administrator Reference Manual). If they are within
|
||||
their publication period, merge them into the
|
||||
zone's DNSKEY RRset. If the DNSKEY RRset
|
||||
is changed, then the zone is automatically
|
||||
re-signed with the new key set.
|
||||
</p>
|
||||
<p>
|
||||
This command requires that the
|
||||
<span><strong class="command">auto-dnssec</strong></span> zone option be set
|
||||
to <code class="literal">allow</code> or
|
||||
<code class="literal">maintain</code>,
|
||||
and also requires the zone to be configured to
|
||||
allow dynamic DNS.
|
||||
(See "Dynamic Update Policies" in the Administrator
|
||||
Reference Manual for more details.)
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>loadkeys <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Fetch all DNSSEC keys for the given zone
|
||||
from the key directory. If they are within
|
||||
their publication period, merge them into the
|
||||
zone's DNSKEY RRset. Unlike <span><strong class="command">rndc
|
||||
sign</strong></span>, however, the zone is not
|
||||
immediately re-signed by the new keys, but is
|
||||
allowed to incrementally re-sign over time.
|
||||
</p>
|
||||
<p>
|
||||
This command requires that the
|
||||
<span><strong class="command">auto-dnssec</strong></span> zone option
|
||||
be set to <code class="literal">maintain</code>,
|
||||
and also requires the zone to be configured to
|
||||
allow dynamic DNS.
|
||||
(See "Dynamic Update Policies" in the Administrator
|
||||
Reference Manual for more details.)
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>freeze [<span class="optional"><em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Suspend updates to a dynamic zone. If no zone is
|
||||
specified, then all zones are suspended. This allows
|
||||
manual edits to be made to a zone normally updated by
|
||||
dynamic update. It also causes changes in the
|
||||
journal file to be synced into the master file.
|
||||
All dynamic update attempts will be refused while
|
||||
the zone is frozen.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>thaw [<span class="optional"><em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Enable updates to a frozen dynamic zone. If no
|
||||
zone is specified, then all frozen zones are
|
||||
enabled. This causes the server to reload the zone
|
||||
from disk, and re-enables dynamic updates after the
|
||||
load has completed. After a zone is thawed,
|
||||
dynamic updates will no longer be refused. If
|
||||
the zone has changed and the
|
||||
<span><strong class="command">ixfr-from-differences</strong></span> option is
|
||||
in use, then the journal file will be updated to
|
||||
reflect changes in the zone. Otherwise, if the
|
||||
zone has changed, any existing journal file will be
|
||||
removed.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>scan</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Scan the list of available network interfaces
|
||||
for changes, without performing a full
|
||||
<span><strong class="command">reconfig</strong></span> or waiting for the
|
||||
<span><strong class="command">interface-interval</strong></span> timer.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>sync [<span class="optional">-clean</span>] [<span class="optional"><em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Sync changes in the journal file for a dynamic zone
|
||||
to the master file. If the "-clean" option is
|
||||
specified, the journal file is also removed. If
|
||||
no zone is specified, then all zones are synced.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>notify <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Resend NOTIFY messages for the zone.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>reconfig</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Reload the configuration file and load new zones,
|
||||
but do not reload existing zone files even if they
|
||||
have changed.
|
||||
This is faster than a full <span><strong class="command">reload</strong></span> when there
|
||||
is a large number of zones because it avoids the need
|
||||
to examine the
|
||||
modification times of the zones files.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>zonestatus [<span class="optional"><em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Displays the current status of the given zone,
|
||||
including the master file name and any include
|
||||
files from which it was loaded, when it was most
|
||||
recently loaded, the current serial number, the
|
||||
number of nodes, whether the zone supports
|
||||
dynamic updates, whether the zone is DNSSEC
|
||||
signed, whether it uses automatic DNSSEC key
|
||||
management or inline signing, and the scheduled
|
||||
refresh or expiry times for the zone.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>stats</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Write server statistics to the statistics file.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>querylog</code></strong> [<span class="optional">on|off</span>] </span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Enable or disable query logging. (For backward
|
||||
compatibility, this command can also be used without
|
||||
an argument to toggle query logging on and off.)
|
||||
</p>
|
||||
<p>
|
||||
Query logging can also be enabled
|
||||
by explicitly directing the <span><strong class="command">queries</strong></span>
|
||||
<span><strong class="command">category</strong></span> to a
|
||||
<span><strong class="command">channel</strong></span> in the
|
||||
<span><strong class="command">logging</strong></span> section of
|
||||
<code class="filename">named.conf</code> or by specifying
|
||||
<span><strong class="command">querylog yes;</strong></span> in the
|
||||
<span><strong class="command">options</strong></span> section of
|
||||
<code class="filename">named.conf</code>.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>dumpdb [<span class="optional">-all|-cache|-zone</span>] [<span class="optional"><em class="replaceable"><code>view ...</code></em></span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Dump the server's caches (default) and/or zones to
|
||||
the
|
||||
dump file for the specified views. If no view is
|
||||
specified, all
|
||||
views are dumped.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>secroots [<span class="optional"><em class="replaceable"><code>view ...</code></em></span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Dump the server's security roots to the secroots
|
||||
file for the specified views. If no view is
|
||||
specified, security roots for all
|
||||
views are dumped.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>stop [<span class="optional">-p</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Stop the server, making sure any recent changes
|
||||
made through dynamic update or IXFR are first saved to
|
||||
the master files of the updated zones.
|
||||
If <code class="option">-p</code> is specified <span><strong class="command">named</strong></span>'s process id is returned.
|
||||
This allows an external process to determine when <span><strong class="command">named</strong></span>
|
||||
had completed stopping.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>halt [<span class="optional">-p</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Stop the server immediately. Recent changes
|
||||
made through dynamic update or IXFR are not saved to
|
||||
the master files, but will be rolled forward from the
|
||||
journal files when the server is restarted.
|
||||
If <code class="option">-p</code> is specified <span><strong class="command">named</strong></span>'s process id is returned.
|
||||
This allows an external process to determine when <span><strong class="command">named</strong></span>
|
||||
had completed halting.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>trace</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Increment the servers debugging level by one.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>trace <em class="replaceable"><code>level</code></em></code></strong></span></dt>
|
||||
<dd><p>
|
||||
Sets the server's debugging level to an explicit
|
||||
value.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>notrace</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Sets the server's debugging level to 0.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>flush</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Flushes the server's cache.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>flushname</code></strong> <em class="replaceable"><code>name</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>] </span></dt>
|
||||
<dd><p>
|
||||
Flushes the given name from the server's DNS cache
|
||||
and, if applicable, from the server's nameserver address
|
||||
database or bad-server cache.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>flushtree</code></strong> <em class="replaceable"><code>name</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>] </span></dt>
|
||||
<dd><p>
|
||||
Flushes the given name, and all of its subdomains,
|
||||
from the server's DNS cache, the address database,
|
||||
and the bad server cache.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>status</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Display status of the server.
|
||||
Note that the number of zones includes the internal <span><strong class="command">bind/CH</strong></span> zone
|
||||
and the default <span><strong class="command">./IN</strong></span>
|
||||
hint zone if there is not an
|
||||
explicit root zone configured.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>recursing</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Dump the list of queries <span><strong class="command">named</strong></span> is currently recursing
|
||||
on.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>validation ( on | off | check ) [<span class="optional"><em class="replaceable"><code>view ...</code></em></span>] </code></strong></span></dt>
|
||||
<dd><p>
|
||||
Enable, disable, or check the current status of
|
||||
DNSSEC validation.
|
||||
Note <span><strong class="command">dnssec-enable</strong></span> also needs to be
|
||||
set to <strong class="userinput"><code>yes</code></strong> or
|
||||
<strong class="userinput"><code>auto</code></strong> to be effective.
|
||||
It defaults to enabled.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>tsig-list</code></strong></span></dt>
|
||||
<dd><p>
|
||||
List the names of all TSIG keys currently configured
|
||||
for use by <span><strong class="command">named</strong></span> in each view. The
|
||||
list both statically configured keys and dynamic
|
||||
TKEY-negotiated keys.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>tsig-delete</code></strong> <em class="replaceable"><code>keyname</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span></dt>
|
||||
<dd><p>
|
||||
Delete a given TKEY-negotiated key from the server.
|
||||
(This does not apply to statically configured TSIG
|
||||
keys.)
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>addzone <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>] <em class="replaceable"><code>configuration</code></em> </code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Add a zone while the server is running. This
|
||||
command requires the
|
||||
<span><strong class="command">allow-new-zones</strong></span> option to be set
|
||||
to <strong class="userinput"><code>yes</code></strong>. The
|
||||
<em class="replaceable"><code>configuration</code></em> string
|
||||
specified on the command line is the zone
|
||||
configuration text that would ordinarily be
|
||||
placed in <code class="filename">named.conf</code>.
|
||||
</p>
|
||||
Add a zone while the server is running. This
|
||||
command requires the
|
||||
<span><strong class="command">allow-new-zones</strong></span> option to be set
|
||||
to <strong class="userinput"><code>yes</code></strong>. The
|
||||
<em class="replaceable"><code>configuration</code></em> string
|
||||
specified on the command line is the zone
|
||||
configuration text that would ordinarily be
|
||||
placed in <code class="filename">named.conf</code>.
|
||||
</p>
|
||||
<p>
|
||||
The configuration is saved in a file called
|
||||
<code class="filename"><em class="replaceable"><code>hash</code></em>.nzf</code>,
|
||||
where <em class="replaceable"><code>hash</code></em> is a
|
||||
cryptographic hash generated from the name of
|
||||
the view. When <span><strong class="command">named</strong></span> is
|
||||
restarted, the file will be loaded into the view
|
||||
configuration, so that zones that were added
|
||||
can persist after a restart.
|
||||
</p>
|
||||
The configuration is saved in a file called
|
||||
<code class="filename"><em class="replaceable"><code>hash</code></em>.nzf</code>,
|
||||
where <em class="replaceable"><code>hash</code></em> is a
|
||||
cryptographic hash generated from the name of
|
||||
the view. When <span><strong class="command">named</strong></span> is
|
||||
restarted, the file will be loaded into the view
|
||||
configuration, so that zones that were added
|
||||
can persist after a restart.
|
||||
</p>
|
||||
<p>
|
||||
This sample <span><strong class="command">addzone</strong></span> command
|
||||
would add the zone <code class="literal">example.com</code>
|
||||
to the default view:
|
||||
</p>
|
||||
This sample <span><strong class="command">addzone</strong></span> command
|
||||
would add the zone <code class="literal">example.com</code>
|
||||
to the default view:
|
||||
</p>
|
||||
<p>
|
||||
<code class="prompt">$ </code><strong class="userinput"><code>rndc addzone example.com '{ type master; file "example.com.db"; };'</code></strong>
|
||||
</p>
|
||||
</p>
|
||||
<p>
|
||||
(Note the brackets and semi-colon around the zone
|
||||
configuration text.)
|
||||
</p>
|
||||
(Note the brackets and semi-colon around the zone
|
||||
configuration text.)
|
||||
</p>
|
||||
<p>
|
||||
See also <span><strong class="command">rndc delzone</strong></span> and <span><strong class="command">rndc modzone</strong></span>.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>delzone [<span class="optional">-clean</span>] <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>] </code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Delete a zone while the server is running.
|
||||
Only zones that were originally added via
|
||||
<span><strong class="command">rndc addzone</strong></span> can be deleted
|
||||
in this manner.
|
||||
</p>
|
||||
Delete a zone while the server is running.
|
||||
Only zones that were originally added via
|
||||
<span><strong class="command">rndc addzone</strong></span> can be deleted
|
||||
in this manner.
|
||||
</p>
|
||||
<p>
|
||||
If the <code class="option">-clean</code> is specified,
|
||||
the zone's master file (and journal file, if any)
|
||||
will be deleted along with the zone. Without the
|
||||
<code class="option">-clean</code> option, zone files must
|
||||
be cleaned up by hand. (If the zone is of
|
||||
type "slave" or "stub", the files needing to
|
||||
be cleaned up will be reported in the output
|
||||
of the <span><strong class="command">rndc delzone</strong></span> command.)
|
||||
</p>
|
||||
If the <code class="option">-clean</code> is specified,
|
||||
the zone's master file (and journal file, if any)
|
||||
will be deleted along with the zone. Without the
|
||||
<code class="option">-clean</code> option, zone files must
|
||||
be cleaned up by hand. (If the zone is of
|
||||
type "slave" or "stub", the files needing to
|
||||
be cleaned up will be reported in the output
|
||||
of the <span><strong class="command">rndc delzone</strong></span> command.)
|
||||
</p>
|
||||
<p>
|
||||
See also <span><strong class="command">rndc addzone</strong></span> and <span><strong class="command">rndc modzone</strong></span>.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>dumpdb [<span class="optional">-all|-cache|-zone</span>] [<span class="optional"><em class="replaceable"><code>view ...</code></em></span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Dump the server's caches (default) and/or zones to
|
||||
the
|
||||
dump file for the specified views. If no view is
|
||||
specified, all
|
||||
views are dumped.
|
||||
(See the <span><strong class="command">dump-file</strong></span> option in
|
||||
the BIND 9 Administrator Reference Manual.)
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>flush</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Flushes the server's cache.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>flushname</code></strong> <em class="replaceable"><code>name</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>] </span></dt>
|
||||
<dd><p>
|
||||
Flushes the given name from the server's DNS cache
|
||||
and, if applicable, from the server's nameserver address
|
||||
database or bad-server cache.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>flushtree</code></strong> <em class="replaceable"><code>name</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>] </span></dt>
|
||||
<dd><p>
|
||||
Flushes the given name, and all of its subdomains,
|
||||
from the server's DNS cache, the address database,
|
||||
and the bad server cache.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>freeze [<span class="optional"><em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</span>]</code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Suspend updates to a dynamic zone. If no zone is
|
||||
specified, then all zones are suspended. This allows
|
||||
manual edits to be made to a zone normally updated by
|
||||
dynamic update. It also causes changes in the
|
||||
journal file to be synced into the master file.
|
||||
All dynamic update attempts will be refused while
|
||||
the zone is frozen.
|
||||
</p>
|
||||
<p>
|
||||
See also <span><strong class="command">rndc thaw</strong></span>.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>halt [<span class="optional">-p</span>]</code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Stop the server immediately. Recent changes
|
||||
made through dynamic update or IXFR are not saved to
|
||||
the master files, but will be rolled forward from the
|
||||
journal files when the server is restarted.
|
||||
If <code class="option">-p</code> is specified <span><strong class="command">named</strong></span>'s process id is returned.
|
||||
This allows an external process to determine when <span><strong class="command">named</strong></span>
|
||||
had completed halting.
|
||||
</p>
|
||||
<p>
|
||||
See also <span><strong class="command">rndc stop</strong></span>.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>loadkeys <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Fetch all DNSSEC keys for the given zone
|
||||
from the key directory. If they are within
|
||||
their publication period, merge them into the
|
||||
zone's DNSKEY RRset. Unlike <span><strong class="command">rndc
|
||||
sign</strong></span>, however, the zone is not
|
||||
immediately re-signed by the new keys, but is
|
||||
allowed to incrementally re-sign over time.
|
||||
</p>
|
||||
<p>
|
||||
This command requires that the
|
||||
<span><strong class="command">auto-dnssec</strong></span> zone option
|
||||
be set to <code class="literal">maintain</code>,
|
||||
and also requires the zone to be configured to
|
||||
allow dynamic DNS.
|
||||
(See "Dynamic Update Policies" in the Administrator
|
||||
Reference Manual for more details.)
|
||||
</p>
|
||||
<p>
|
||||
See also <span><strong class="command">rndc loadkeys</strong></span>.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>notify <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Resend NOTIFY messages for the zone.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>notrace</code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Sets the server's debugging level to 0.
|
||||
</p>
|
||||
<p>
|
||||
See also <span><strong class="command">rndc trace</strong></span>.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>querylog</code></strong> [<span class="optional">on|off</span>] </span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Enable or disable query logging. (For backward
|
||||
compatibility, this command can also be used without
|
||||
an argument to toggle query logging on and off.)
|
||||
</p>
|
||||
<p>
|
||||
Query logging can also be enabled
|
||||
by explicitly directing the <span><strong class="command">queries</strong></span>
|
||||
<span><strong class="command">category</strong></span> to a
|
||||
<span><strong class="command">channel</strong></span> in the
|
||||
<span><strong class="command">logging</strong></span> section of
|
||||
<code class="filename">named.conf</code> or by specifying
|
||||
<span><strong class="command">querylog yes;</strong></span> in the
|
||||
<span><strong class="command">options</strong></span> section of
|
||||
<code class="filename">named.conf</code>.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>reconfig</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Reload the configuration file and load new zones,
|
||||
but do not reload existing zone files even if they
|
||||
have changed.
|
||||
This is faster than a full <span><strong class="command">reload</strong></span> when there
|
||||
is a large number of zones because it avoids the need
|
||||
to examine the
|
||||
modification times of the zones files.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>recursing</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Dump the list of queries <span><strong class="command">named</strong></span> is currently recursing
|
||||
on.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>refresh <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Schedule zone maintenance for the given zone.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>reload</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Reload configuration file and zones.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>reload <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Reload the given zone.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>retransfer <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Retransfer the given slave zone from the master server.
|
||||
</p>
|
||||
<p>
|
||||
If the zone is configured to use
|
||||
<span><strong class="command">inline-signing</strong></span>, the signed
|
||||
version of the zone is discarded; after the
|
||||
retransfer of the unsigned version is complete, the
|
||||
signed version will be regenerated with all new
|
||||
signatures.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>scan</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Scan the list of available network interfaces
|
||||
for changes, without performing a full
|
||||
<span><strong class="command">reconfig</strong></span> or waiting for the
|
||||
<span><strong class="command">interface-interval</strong></span> timer.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>secroots [<span class="optional"><em class="replaceable"><code>view ...</code></em></span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Dump the server's security roots to the secroots
|
||||
file for the specified views. If no view is
|
||||
specified, security roots for all
|
||||
views are dumped.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>sign <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Fetch all DNSSEC keys for the given zone
|
||||
from the key directory (see the
|
||||
<span><strong class="command">key-directory</strong></span> option in
|
||||
the BIND 9 Administrator Reference Manual). If they are within
|
||||
their publication period, merge them into the
|
||||
zone's DNSKEY RRset. If the DNSKEY RRset
|
||||
is changed, then the zone is automatically
|
||||
re-signed with the new key set.
|
||||
</p>
|
||||
<p>
|
||||
This command requires that the
|
||||
<span><strong class="command">auto-dnssec</strong></span> zone option be set
|
||||
to <code class="literal">allow</code> or
|
||||
<code class="literal">maintain</code>,
|
||||
and also requires the zone to be configured to
|
||||
allow dynamic DNS.
|
||||
(See "Dynamic Update Policies" in the Administrator
|
||||
Reference Manual for more details.)
|
||||
</p>
|
||||
<p>
|
||||
See also <span><strong class="command">rndc loadkeys</strong></span>.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>signing [<span class="optional">( -list | -clear <em class="replaceable"><code>keyid/algorithm</code></em> | -clear <code class="literal">all</code> | -nsec3param ( <em class="replaceable"><code>parameters</code></em> | <code class="literal">none</code> ) ) </span>] <em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>] </code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
List, edit, or remove the DNSSEC signing state records
|
||||
for the specified zone. The status of ongoing DNSSEC
|
||||
operations (such as signing or generating
|
||||
NSEC3 chains) is stored in the zone in the form
|
||||
of DNS resource records of type
|
||||
<span><strong class="command">sig-signing-type</strong></span>.
|
||||
<span><strong class="command">rndc signing -list</strong></span> converts
|
||||
these records into a human-readable form,
|
||||
indicating which keys are currently signing
|
||||
or have finished signing the zone, and which NSEC3
|
||||
chains are being created or removed.
|
||||
</p>
|
||||
List, edit, or remove the DNSSEC signing state records
|
||||
for the specified zone. The status of ongoing DNSSEC
|
||||
operations (such as signing or generating
|
||||
NSEC3 chains) is stored in the zone in the form
|
||||
of DNS resource records of type
|
||||
<span><strong class="command">sig-signing-type</strong></span>.
|
||||
<span><strong class="command">rndc signing -list</strong></span> converts
|
||||
these records into a human-readable form,
|
||||
indicating which keys are currently signing
|
||||
or have finished signing the zone, and which NSEC3
|
||||
chains are being created or removed.
|
||||
</p>
|
||||
<p>
|
||||
<span><strong class="command">rndc signing -clear</strong></span> can remove
|
||||
a single key (specified in the same format that
|
||||
<span><strong class="command">rndc signing -list</strong></span> uses to
|
||||
display it), or all keys. In either case, only
|
||||
completed keys are removed; any record indicating
|
||||
that a key has not yet finished signing the zone
|
||||
will be retained.
|
||||
</p>
|
||||
<span><strong class="command">rndc signing -clear</strong></span> can remove
|
||||
a single key (specified in the same format that
|
||||
<span><strong class="command">rndc signing -list</strong></span> uses to
|
||||
display it), or all keys. In either case, only
|
||||
completed keys are removed; any record indicating
|
||||
that a key has not yet finished signing the zone
|
||||
will be retained.
|
||||
</p>
|
||||
<p>
|
||||
<span><strong class="command">rndc signing -nsec3param</strong></span> sets
|
||||
the NSEC3 parameters for a zone. This is the
|
||||
only supported mechanism for using NSEC3 with
|
||||
<span><strong class="command">inline-signing</strong></span> zones.
|
||||
Parameters are specified in the same format as
|
||||
an NSEC3PARAM resource record: hash algorithm,
|
||||
flags, iterations, and salt, in that order.
|
||||
</p>
|
||||
<span><strong class="command">rndc signing -nsec3param</strong></span> sets
|
||||
the NSEC3 parameters for a zone. This is the
|
||||
only supported mechanism for using NSEC3 with
|
||||
<span><strong class="command">inline-signing</strong></span> zones.
|
||||
Parameters are specified in the same format as
|
||||
an NSEC3PARAM resource record: hash algorithm,
|
||||
flags, iterations, and salt, in that order.
|
||||
</p>
|
||||
<p>
|
||||
Currently, the only defined value for hash algorithm
|
||||
is <code class="literal">1</code>, representing SHA-1.
|
||||
The <code class="option">flags</code> may be set to
|
||||
<code class="literal">0</code> or <code class="literal">1</code>,
|
||||
depending on whether you wish to set the opt-out
|
||||
bit in the NSEC3 chain. <code class="option">iterations</code>
|
||||
defines the number of additional times to apply
|
||||
the algorithm when generating an NSEC3 hash. The
|
||||
<code class="option">salt</code> is a string of data expressed
|
||||
in hexadecimal, a hyphen (`-') if no salt is
|
||||
to be used, or the keyword <code class="literal">auto</code>,
|
||||
which causes <span><strong class="command">named</strong></span> to generate a
|
||||
random 64-bit salt.
|
||||
</p>
|
||||
Currently, the only defined value for hash algorithm
|
||||
is <code class="literal">1</code>, representing SHA-1.
|
||||
The <code class="option">flags</code> may be set to
|
||||
<code class="literal">0</code> or <code class="literal">1</code>,
|
||||
depending on whether you wish to set the opt-out
|
||||
bit in the NSEC3 chain. <code class="option">iterations</code>
|
||||
defines the number of additional times to apply
|
||||
the algorithm when generating an NSEC3 hash. The
|
||||
<code class="option">salt</code> is a string of data expressed
|
||||
in hexadecimal, a hyphen (`-') if no salt is
|
||||
to be used, or the keyword <code class="literal">auto</code>,
|
||||
which causes <span><strong class="command">named</strong></span> to generate a
|
||||
random 64-bit salt.
|
||||
</p>
|
||||
<p>
|
||||
So, for example, to create an NSEC3 chain using
|
||||
the SHA-1 hash algorithm, no opt-out flag,
|
||||
10 iterations, and a salt value of "FFFF", use:
|
||||
<span><strong class="command">rndc signing -nsec3param 1 0 10 FFFF <em class="replaceable"><code>zone</code></em></strong></span>.
|
||||
To set the opt-out flag, 15 iterations, and no
|
||||
salt, use:
|
||||
<span><strong class="command">rndc signing -nsec3param 1 1 15 - <em class="replaceable"><code>zone</code></em></strong></span>.
|
||||
</p>
|
||||
So, for example, to create an NSEC3 chain using
|
||||
the SHA-1 hash algorithm, no opt-out flag,
|
||||
10 iterations, and a salt value of "FFFF", use:
|
||||
<span><strong class="command">rndc signing -nsec3param 1 0 10 FFFF <em class="replaceable"><code>zone</code></em></strong></span>.
|
||||
To set the opt-out flag, 15 iterations, and no
|
||||
salt, use:
|
||||
<span><strong class="command">rndc signing -nsec3param 1 1 15 - <em class="replaceable"><code>zone</code></em></strong></span>.
|
||||
</p>
|
||||
<p>
|
||||
<span><strong class="command">rndc signing -nsec3param none</strong></span>
|
||||
removes an existing NSEC3 chain and replaces it
|
||||
with NSEC.
|
||||
</p>
|
||||
<span><strong class="command">rndc signing -nsec3param none</strong></span>
|
||||
removes an existing NSEC3 chain and replaces it
|
||||
with NSEC.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>stats</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Write server statistics to the statistics file.
|
||||
(See the <span><strong class="command">statistics-file</strong></span> option in
|
||||
the BIND 9 Administrator Reference Manual.)
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>status</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Display status of the server.
|
||||
Note that the number of zones includes the internal <span><strong class="command">bind/CH</strong></span> zone
|
||||
and the default <span><strong class="command">./IN</strong></span>
|
||||
hint zone if there is not an
|
||||
explicit root zone configured.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>stop [<span class="optional">-p</span>]</code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Stop the server, making sure any recent changes
|
||||
made through dynamic update or IXFR are first saved to
|
||||
the master files of the updated zones.
|
||||
If <code class="option">-p</code> is specified <span><strong class="command">named</strong></span>'s process id is returned.
|
||||
This allows an external process to determine when <span><strong class="command">named</strong></span>
|
||||
had completed stopping.
|
||||
</p>
|
||||
<p>See also <span><strong class="command">rndc halt</strong></span>.</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>sync [<span class="optional">-clean</span>] [<span class="optional"><em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Sync changes in the journal file for a dynamic zone
|
||||
to the master file. If the "-clean" option is
|
||||
specified, the journal file is also removed. If
|
||||
no zone is specified, then all zones are synced.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>thaw [<span class="optional"><em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</span>]</code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Enable updates to a frozen dynamic zone. If no
|
||||
zone is specified, then all frozen zones are
|
||||
enabled. This causes the server to reload the zone
|
||||
from disk, and re-enables dynamic updates after the
|
||||
load has completed. After a zone is thawed,
|
||||
dynamic updates will no longer be refused. If
|
||||
the zone has changed and the
|
||||
<span><strong class="command">ixfr-from-differences</strong></span> option is
|
||||
in use, then the journal file will be updated to
|
||||
reflect changes in the zone. Otherwise, if the
|
||||
zone has changed, any existing journal file will be
|
||||
removed.
|
||||
</p>
|
||||
<p>See also <span><strong class="command">rndc freeze</strong></span>.</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>trace</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Increment the servers debugging level by one.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>trace <em class="replaceable"><code>level</code></em></code></strong></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Sets the server's debugging level to an explicit
|
||||
value.
|
||||
</p>
|
||||
<p>
|
||||
See also <span><strong class="command">rndc notrace</strong></span>.
|
||||
</p>
|
||||
</dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>tsig-delete</code></strong> <em class="replaceable"><code>keyname</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span></dt>
|
||||
<dd><p>
|
||||
Delete a given TKEY-negotiated key from the server.
|
||||
(This does not apply to statically configured TSIG
|
||||
keys.)
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>tsig-list</code></strong></span></dt>
|
||||
<dd><p>
|
||||
List the names of all TSIG keys currently configured
|
||||
for use by <span><strong class="command">named</strong></span> in each view. The
|
||||
list both statically configured keys and dynamic
|
||||
TKEY-negotiated keys.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>validation ( on | off | check ) [<span class="optional"><em class="replaceable"><code>view ...</code></em></span>] </code></strong></span></dt>
|
||||
<dd><p>
|
||||
Enable, disable, or check the current status of
|
||||
DNSSEC validation.
|
||||
Note <span><strong class="command">dnssec-enable</strong></span> also needs to be
|
||||
set to <strong class="userinput"><code>yes</code></strong> or
|
||||
<strong class="userinput"><code>auto</code></strong> to be effective.
|
||||
It defaults to enabled.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>zonestatus [<span class="optional"><em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Displays the current status of the given zone,
|
||||
including the master file name and any include
|
||||
files from which it was loaded, when it was most
|
||||
recently loaded, the current serial number, the
|
||||
number of nodes, whether the zone supports
|
||||
dynamic updates, whether the zone is DNSSEC
|
||||
signed, whether it uses automatic DNSSEC key
|
||||
management or inline signing, and the scheduled
|
||||
refresh or expiry times for the zone.
|
||||
</p></dd>
|
||||
</dl></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2688131"></a><h2>LIMITATIONS</h2>
|
||||
<a name="id2688016"></a><h2>LIMITATIONS</h2>
|
||||
<p>
|
||||
There is currently no way to provide the shared secret for a
|
||||
<code class="option">key_id</code> without using the configuration file.
|
||||
|
|
@ -547,7 +589,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2688149"></a><h2>SEE ALSO</h2>
|
||||
<a name="id2688034"></a><h2>SEE ALSO</h2>
|
||||
<p><span class="citerefentry"><span class="refentrytitle">rndc.conf</span>(5)</span>,
|
||||
<span class="citerefentry"><span class="refentrytitle">rndc-confgen</span>(8)</span>,
|
||||
<span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
|
||||
|
|
@ -557,7 +599,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2688204"></a><h2>AUTHOR</h2>
|
||||
<a name="id2688089"></a><h2>AUTHOR</h2>
|
||||
<p><span class="corpauthor">Internet Systems Consortium</span>
|
||||
</p>
|
||||
</div>
|
||||
|
|
|
|||
Loading…
Reference in a new issue