+ --- 9.11.25 released ---
+
5527. [bug] A NULL pointer dereference occurred when creating an NTA
recheck query failed. [GL #2244]
BIND 9.11.24 is a maintenance release.
+BIND 9.11.25
+
+BIND 9.11.25 is a maintenance release.
+
Building BIND
Minimally, BIND requires a UNIX or Linux system with an ANSI C compiler,
BIND 9.11.24 is a maintenance release.
+#### BIND 9.11.25
+
+BIND 9.11.25 is a maintenance release.
+
### <a name="build"/> Building BIND
Minimally, BIND requires a UNIX or Linux system with an ANSI C compiler,
'\" t
.\" Title: named-checkconf
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2014-01-10
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
named-checkconf \- named configuration file syntax checking tool
-.SH "SYNOPSIS"
-.HP \w'\fBnamed\-checkconf\fR\ 'u
-\fBnamed\-checkconf\fR [\fB\-hjvz\fR] [\fB\-p\fR\ [\fB\-x\fR\ ]] [\fB\-t\ \fR\fB\fIdirectory\fR\fR] {filename}
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBnamed\-checkconf\fR\ 'u
+ \fBnamed\-checkconf\fR
+ [\fB\-hjvz\fR]
+ [\fB\-p\fR\ [\fB\-x\fR\ ]]
+ [\fB\-t\ \fR\fB\fIdirectory\fR\fR]
+ {filename}
+ .SH "DESCRIPTION"
+ .PP
\fBnamed\-checkconf\fR
checks the syntax, but not the semantics, of a
\fBnamed\fR
configuration file\&. The file is parsed and checked for syntax errors, along with all files included by it\&. If no file is specified,
/etc/named\&.conf
is read by default\&.
-.PP
+ .PP
Note: files that
\fBnamed\fR
reads in separate parser contexts, such as
was successful\&.
\fBnamed\-checkconf\fR
can be run on these files explicitly, however\&.
-.SH "OPTIONS"
-.PP
+ .SH "OPTIONS"
+ .PP
\-h
.RS 4
-Print the usage summary and exit\&.
-.RE
-.PP
+ Print the usage summary and exit\&.
+ .RE
+ .PP
\-j
.RS 4
-When loading a zonefile read the journal if it exists\&.
-.RE
-.PP
+ When loading a zonefile read the journal if it exists\&.
+ .RE
+ .PP
\-p
.RS 4
-Print out the
+ Print out the
named\&.conf
and included files in canonical form if no errors were detected\&. See also the
\fB\-x\fR
option\&.
-.RE
-.PP
+ .RE
+ .PP
\-t \fIdirectory\fR
.RS 4
-Chroot to
+ Chroot to
directory
so that include directives in the configuration file are processed as if run by a similarly chrooted
\fBnamed\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-v
.RS 4
-Print the version of the
+ Print the version of the
\fBnamed\-checkconf\fR
program and exit\&.
-.RE
-.PP
+ .RE
+ .PP
\-x
.RS 4
-When printing the configuration files in canonical form, obscure shared secrets by replacing them with strings of question marks (\*(Aq?\*(Aq)\&. This allows the contents of
+ When printing the configuration files in canonical form, obscure shared secrets by replacing them with strings of question marks (\*(Aq?\*(Aq)\&. This allows the contents of
named\&.conf
and related files to be shared \(em for example, when submitting bug reports \(em without compromising private data\&. This option cannot be used without
\fB\-p\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-z
.RS 4
-Perform a test load of all master zones found in
+ Perform a test load of all master zones found in
named\&.conf\&.
-.RE
-.PP
+ .RE
+ .PP
filename
.RS 4
-The name of the configuration file to be checked\&. If not specified, it defaults to
+ The name of the configuration file to be checked\&. If not specified, it defaults to
/etc/named\&.conf\&.
-.RE
-.SH "RETURN VALUES"
-.PP
+ .RE
+ .SH "RETURN VALUES"
+ .PP
\fBnamed\-checkconf\fR
returns an exit status of 1 if errors were detected and 0 otherwise\&.
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBnamed\fR(8),
\fBnamed-checkzone\fR(8),
BIND 9 Administrator Reference Manual\&.
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>named-checkconf</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.named-checkconf"></a><div class="titlepage"></div>
'\" t
.\" Title: named-checkzone
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2014-02-19
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
named-checkzone, named-compilezone \- zone file validity checking or converting tool
-.SH "SYNOPSIS"
-.HP \w'\fBnamed\-checkzone\fR\ 'u
-\fBnamed\-checkzone\fR [\fB\-d\fR] [\fB\-h\fR] [\fB\-j\fR] [\fB\-q\fR] [\fB\-v\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-f\ \fR\fB\fIformat\fR\fR] [\fB\-F\ \fR\fB\fIformat\fR\fR] [\fB\-J\ \fR\fB\fIfilename\fR\fR] [\fB\-i\ \fR\fB\fImode\fR\fR] [\fB\-k\ \fR\fB\fImode\fR\fR] [\fB\-m\ \fR\fB\fImode\fR\fR] [\fB\-M\ \fR\fB\fImode\fR\fR] [\fB\-n\ \fR\fB\fImode\fR\fR] [\fB\-l\ \fR\fB\fIttl\fR\fR] [\fB\-L\ \fR\fB\fIserial\fR\fR] [\fB\-o\ \fR\fB\fIfilename\fR\fR] [\fB\-r\ \fR\fB\fImode\fR\fR] [\fB\-s\ \fR\fB\fIstyle\fR\fR] [\fB\-S\ \fR\fB\fImode\fR\fR] [\fB\-t\ \fR\fB\fIdirectory\fR\fR] [\fB\-T\ \fR\fB\fImode\fR\fR] [\fB\-w\ \fR\fB\fIdirectory\fR\fR] [\fB\-D\fR] [\fB\-W\ \fR\fB\fImode\fR\fR] {zonename} {filename}
-.HP \w'\fBnamed\-compilezone\fR\ 'u
-\fBnamed\-compilezone\fR [\fB\-d\fR] [\fB\-j\fR] [\fB\-q\fR] [\fB\-v\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-C\ \fR\fB\fImode\fR\fR] [\fB\-f\ \fR\fB\fIformat\fR\fR] [\fB\-F\ \fR\fB\fIformat\fR\fR] [\fB\-J\ \fR\fB\fIfilename\fR\fR] [\fB\-i\ \fR\fB\fImode\fR\fR] [\fB\-k\ \fR\fB\fImode\fR\fR] [\fB\-m\ \fR\fB\fImode\fR\fR] [\fB\-n\ \fR\fB\fImode\fR\fR] [\fB\-l\ \fR\fB\fIttl\fR\fR] [\fB\-L\ \fR\fB\fIserial\fR\fR] [\fB\-r\ \fR\fB\fImode\fR\fR] [\fB\-s\ \fR\fB\fIstyle\fR\fR] [\fB\-t\ \fR\fB\fIdirectory\fR\fR] [\fB\-T\ \fR\fB\fImode\fR\fR] [\fB\-w\ \fR\fB\fIdirectory\fR\fR] [\fB\-D\fR] [\fB\-W\ \fR\fB\fImode\fR\fR] {\fB\-o\ \fR\fB\fIfilename\fR\fR} {zonename} {filename}
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBnamed\-checkzone\fR\ 'u
+ \fBnamed\-checkzone\fR
+ [\fB\-d\fR]
+ [\fB\-h\fR]
+ [\fB\-j\fR]
+ [\fB\-q\fR]
+ [\fB\-v\fR]
+ [\fB\-c\ \fR\fB\fIclass\fR\fR]
+ [\fB\-f\ \fR\fB\fIformat\fR\fR]
+ [\fB\-F\ \fR\fB\fIformat\fR\fR]
+ [\fB\-J\ \fR\fB\fIfilename\fR\fR]
+ [\fB\-i\ \fR\fB\fImode\fR\fR]
+ [\fB\-k\ \fR\fB\fImode\fR\fR]
+ [\fB\-m\ \fR\fB\fImode\fR\fR]
+ [\fB\-M\ \fR\fB\fImode\fR\fR]
+ [\fB\-n\ \fR\fB\fImode\fR\fR]
+ [\fB\-l\ \fR\fB\fIttl\fR\fR]
+ [\fB\-L\ \fR\fB\fIserial\fR\fR]
+ [\fB\-o\ \fR\fB\fIfilename\fR\fR]
+ [\fB\-r\ \fR\fB\fImode\fR\fR]
+ [\fB\-s\ \fR\fB\fIstyle\fR\fR]
+ [\fB\-S\ \fR\fB\fImode\fR\fR]
+ [\fB\-t\ \fR\fB\fIdirectory\fR\fR]
+ [\fB\-T\ \fR\fB\fImode\fR\fR]
+ [\fB\-w\ \fR\fB\fIdirectory\fR\fR]
+ [\fB\-D\fR]
+ [\fB\-W\ \fR\fB\fImode\fR\fR]
+ {zonename}
+ {filename}
+ .HP \w'\fBnamed\-compilezone\fR\ 'u
+ \fBnamed\-compilezone\fR
+ [\fB\-d\fR]
+ [\fB\-j\fR]
+ [\fB\-q\fR]
+ [\fB\-v\fR]
+ [\fB\-c\ \fR\fB\fIclass\fR\fR]
+ [\fB\-C\ \fR\fB\fImode\fR\fR]
+ [\fB\-f\ \fR\fB\fIformat\fR\fR]
+ [\fB\-F\ \fR\fB\fIformat\fR\fR]
+ [\fB\-J\ \fR\fB\fIfilename\fR\fR]
+ [\fB\-i\ \fR\fB\fImode\fR\fR]
+ [\fB\-k\ \fR\fB\fImode\fR\fR]
+ [\fB\-m\ \fR\fB\fImode\fR\fR]
+ [\fB\-n\ \fR\fB\fImode\fR\fR]
+ [\fB\-l\ \fR\fB\fIttl\fR\fR]
+ [\fB\-L\ \fR\fB\fIserial\fR\fR]
+ [\fB\-r\ \fR\fB\fImode\fR\fR]
+ [\fB\-s\ \fR\fB\fIstyle\fR\fR]
+ [\fB\-t\ \fR\fB\fIdirectory\fR\fR]
+ [\fB\-T\ \fR\fB\fImode\fR\fR]
+ [\fB\-w\ \fR\fB\fIdirectory\fR\fR]
+ [\fB\-D\fR]
+ [\fB\-W\ \fR\fB\fImode\fR\fR]
+ {\fB\-o\ \fR\fB\fIfilename\fR\fR}
+ {zonename}
+ {filename}
+ .SH "DESCRIPTION"
+ .PP
\fBnamed\-checkzone\fR
checks the syntax and integrity of a zone file\&. It performs the same checks as
\fBnamed\fR
does when loading a zone\&. This makes
\fBnamed\-checkzone\fR
useful for checking zone files before configuring them into a name server\&.
-.PP
+ .PP
\fBnamed\-compilezone\fR
is similar to
\fBnamed\-checkzone\fR, but it always dumps the zone contents to a specified file in a specified format\&. Additionally, it applies stricter check levels by default, since the dump output will be used as an actual zone file loaded by
\fBnamed\fR\&. When manually specified otherwise, the check levels must at least be as strict as those specified in the
\fBnamed\fR
configuration file\&.
-.SH "OPTIONS"
-.PP
+ .SH "OPTIONS"
+ .PP
\-d
.RS 4
-Enable debugging\&.
-.RE
-.PP
+ Enable debugging\&.
+ .RE
+ .PP
\-h
.RS 4
-Print the usage summary and exit\&.
-.RE
-.PP
+ Print the usage summary and exit\&.
+ .RE
+ .PP
\-q
.RS 4
-Quiet mode \- exit code only\&.
-.RE
-.PP
+ Quiet mode \- exit code only\&.
+ .RE
+ .PP
\-v
.RS 4
-Print the version of the
+ Print the version of the
\fBnamed\-checkzone\fR
program and exit\&.
-.RE
-.PP
+ .RE
+ .PP
\-j
.RS 4
-When loading a zone file, read the journal if it exists\&. The journal file name is assumed to be the zone file name appended with the string
+ When loading a zone file, read the journal if it exists\&. The journal file name is assumed to be the zone file name appended with the string
\&.jnl\&.
-.RE
-.PP
+ .RE
+ .PP
\-J \fIfilename\fR
.RS 4
-When loading the zone file read the journal from the given file, if it exists\&. (Implies \-j\&.)
-.RE
-.PP
+ When loading the zone file read the journal from the given file, if it exists\&. (Implies \-j\&.)
+ .RE
+ .PP
\-c \fIclass\fR
.RS 4
-Specify the class of the zone\&. If not specified, "IN" is assumed\&.
-.RE
-.PP
+ Specify the class of the zone\&. If not specified, "IN" is assumed\&.
+ .RE
+ .PP
\-i \fImode\fR
.RS 4
-Perform post\-load zone integrity checks\&. Possible modes are
+ Perform post\-load zone integrity checks\&. Possible modes are
\fB"full"\fR
(default),
\fB"full\-sibling"\fR,
and
\fB"none"\fR\&.
.sp
-Mode
+ Mode
\fB"full"\fR
checks that MX records refer to A or AAAA record (both in\-zone and out\-of\-zone hostnames)\&. Mode
\fB"local"\fR
only checks MX records which refer to in\-zone hostnames\&.
.sp
-Mode
+ Mode
\fB"full"\fR
checks that SRV records refer to A or AAAA record (both in\-zone and out\-of\-zone hostnames)\&. Mode
\fB"local"\fR
only checks SRV records which refer to in\-zone hostnames\&.
.sp
-Mode
+ Mode
\fB"full"\fR
checks that delegation NS records refer to A or AAAA record (both in\-zone and out\-of\-zone hostnames)\&. It also checks that glue address records in the zone match those advertised by the child\&. Mode
\fB"local"\fR
only checks NS records which refer to in\-zone hostnames or that some required glue exists, that is when the nameserver is in a child zone\&.
.sp
-Mode
+ Mode
\fB"full\-sibling"\fR
and
\fB"local\-sibling"\fR
\fB"local"\fR
respectively\&.
.sp
-Mode
+ Mode
\fB"none"\fR
disables the checks\&.
-.RE
-.PP
+ .RE
+ .PP
\-f \fIformat\fR
.RS 4
-Specify the format of the zone file\&. Possible formats are
+ Specify the format of the zone file\&. Possible formats are
\fB"text"\fR
(default),
\fB"raw"\fR, and
\fB"map"\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-F \fIformat\fR
.RS 4
-Specify the format of the output file specified\&. For
+ Specify the format of the output file specified\&. For
\fBnamed\-checkzone\fR, this does not cause any effects unless it dumps the zone contents\&.
.sp
-Possible formats are
+ Possible formats are
\fB"text"\fR
(default), which is the standard textual representation of the zone, and
\fB"map"\fR,
\fB"raw=N"\fR
specifies the format version of the raw zone file: if N is 0, the raw file can be read by any version of
\fBnamed\fR; if N is 1, the file can be read by release 9\&.9\&.0 or higher; the default is 1\&.
-.RE
-.PP
+ .RE
+ .PP
\-k \fImode\fR
.RS 4
-Perform
+ Perform
\fB"check\-names"\fR
checks with the specified failure mode\&. Possible modes are
\fB"fail"\fR
(default for
\fBnamed\-checkzone\fR) and
\fB"ignore"\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-l \fIttl\fR
.RS 4
-Sets a maximum permissible TTL for the input file\&. Any record with a TTL higher than this value will cause the zone to be rejected\&. This is similar to using the
+ Sets a maximum permissible TTL for the input file\&. Any record with a TTL higher than this value will cause the zone to be rejected\&. This is similar to using the
\fBmax\-zone\-ttl\fR
option in
named\&.conf\&.
-.RE
-.PP
+ .RE
+ .PP
\-L \fIserial\fR
.RS 4
-When compiling a zone to "raw" or "map" format, set the "source serial" value in the header to the specified serial number\&. (This is expected to be used primarily for testing purposes\&.)
-.RE
-.PP
+ When compiling a zone to "raw" or "map" format, set the "source serial" value in the header to the specified serial number\&. (This is expected to be used primarily for testing purposes\&.)
+ .RE
+ .PP
\-m \fImode\fR
.RS 4
-Specify whether MX records should be checked to see if they are addresses\&. Possible modes are
+ Specify whether MX records should be checked to see if they are addresses\&. Possible modes are
\fB"fail"\fR,
\fB"warn"\fR
(default) and
\fB"ignore"\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-M \fImode\fR
.RS 4
-Check if a MX record refers to a CNAME\&. Possible modes are
+ Check if a MX record refers to a CNAME\&. Possible modes are
\fB"fail"\fR,
\fB"warn"\fR
(default) and
\fB"ignore"\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-n \fImode\fR
.RS 4
-Specify whether NS records should be checked to see if they are addresses\&. Possible modes are
+ Specify whether NS records should be checked to see if they are addresses\&. Possible modes are
\fB"fail"\fR
(default for
\fBnamed\-compilezone\fR),
(default for
\fBnamed\-checkzone\fR) and
\fB"ignore"\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-o \fIfilename\fR
.RS 4
-Write zone output to
+ Write zone output to
filename\&. If
filename
is
\-
then write to standard out\&. This is mandatory for
\fBnamed\-compilezone\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-r \fImode\fR
.RS 4
-Check for records that are treated as different by DNSSEC but are semantically equal in plain DNS\&. Possible modes are
+ Check for records that are treated as different by DNSSEC but are semantically equal in plain DNS\&. Possible modes are
\fB"fail"\fR,
\fB"warn"\fR
(default) and
\fB"ignore"\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-s \fIstyle\fR
.RS 4
-Specify the style of the dumped zone file\&. Possible styles are
+ Specify the style of the dumped zone file\&. Possible styles are
\fB"full"\fR
(default) and
\fB"relative"\fR\&. The full format is most suitable for processing automatically by a separate script\&. On the other hand, the relative format is more human\-readable and is thus suitable for editing by hand\&. For
\fBnamed\-checkzone\fR
this does not cause any effects unless it dumps the zone contents\&. It also does not have any meaning if the output format is not text\&.
-.RE
-.PP
+ .RE
+ .PP
\-S \fImode\fR
.RS 4
-Check if a SRV record refers to a CNAME\&. Possible modes are
+ Check if a SRV record refers to a CNAME\&. Possible modes are
\fB"fail"\fR,
\fB"warn"\fR
(default) and
\fB"ignore"\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-t \fIdirectory\fR
.RS 4
-Chroot to
+ Chroot to
directory
so that include directives in the configuration file are processed as if run by a similarly chrooted
\fBnamed\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-T \fImode\fR
.RS 4
-Check if Sender Policy Framework (SPF) records exist and issues a warning if an SPF\-formatted TXT record is not also present\&. Possible modes are
+ Check if Sender Policy Framework (SPF) records exist and issues a warning if an SPF\-formatted TXT record is not also present\&. Possible modes are
\fB"warn"\fR
(default),
\fB"ignore"\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-w \fIdirectory\fR
.RS 4
-chdir to
+ chdir to
directory
so that relative filenames in master file $INCLUDE directives work\&. This is similar to the directory clause in
named\&.conf\&.
-.RE
-.PP
+ .RE
+ .PP
\-D
.RS 4
-Dump zone file in canonical format\&. This is always enabled for
+ Dump zone file in canonical format\&. This is always enabled for
\fBnamed\-compilezone\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-W \fImode\fR
.RS 4
-Specify whether to check for non\-terminal wildcards\&. Non\-terminal wildcards are almost always the result of a failure to understand the wildcard matching algorithm (RFC 1034)\&. Possible modes are
+ Specify whether to check for non\-terminal wildcards\&. Non\-terminal wildcards are almost always the result of a failure to understand the wildcard matching algorithm (RFC 1034)\&. Possible modes are
\fB"warn"\fR
(default) and
\fB"ignore"\fR\&.
-.RE
-.PP
+ .RE
+ .PP
zonename
.RS 4
-The domain name of the zone being checked\&.
-.RE
-.PP
+ The domain name of the zone being checked\&.
+ .RE
+ .PP
filename
.RS 4
-The name of the zone file\&.
-.RE
-.SH "RETURN VALUES"
-.PP
+ The name of the zone file\&.
+ .RE
+ .SH "RETURN VALUES"
+ .PP
\fBnamed\-checkzone\fR
returns an exit status of 1 if errors were detected and 0 otherwise\&.
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBnamed\fR(8),
\fBnamed-checkconf\fR(8),
RFC 1035,
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>named-checkzone</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.named-checkzone"></a><div class="titlepage"></div>
'\" t
.\" Title: ddns-confgen
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2014-03-06
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
ddns-confgen \- ddns key generation tool
-.SH "SYNOPSIS"
-.HP \w'\fBtsig\-keygen\fR\ 'u
-\fBtsig\-keygen\fR [\fB\-a\ \fR\fB\fIalgorithm\fR\fR] [\fB\-h\fR] [\fB\-r\ \fR\fB\fIrandomfile\fR\fR] [name]
-.HP \w'\fBddns\-confgen\fR\ 'u
-\fBddns\-confgen\fR [\fB\-a\ \fR\fB\fIalgorithm\fR\fR] [\fB\-h\fR] [\fB\-k\ \fR\fB\fIkeyname\fR\fR] [\fB\-q\fR] [\fB\-r\ \fR\fB\fIrandomfile\fR\fR] [\-s\ \fIname\fR | \-z\ \fIzone\fR]
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBtsig\-keygen\fR\ 'u
+ \fBtsig\-keygen\fR
+ [\fB\-a\ \fR\fB\fIalgorithm\fR\fR]
+ [\fB\-h\fR]
+ [\fB\-r\ \fR\fB\fIrandomfile\fR\fR]
+ [name]
+ .HP \w'\fBddns\-confgen\fR\ 'u
+ \fBddns\-confgen\fR
+ [\fB\-a\ \fR\fB\fIalgorithm\fR\fR]
+ [\fB\-h\fR]
+ [\fB\-k\ \fR\fB\fIkeyname\fR\fR]
+ [\fB\-q\fR]
+ [\fB\-r\ \fR\fB\fIrandomfile\fR\fR]
+ [
+ | \-s\ \fIname\fR
+ | \-z\ \fIzone\fR
+ ]
+ .SH "DESCRIPTION"
+ .PP
\fBtsig\-keygen\fR
and
\fBddns\-confgen\fR
are invocation methods for a utility that generates keys for use in TSIG signing\&. The resulting keys can be used, for example, to secure dynamic DNS updates to a zone or for the
\fBrndc\fR
command channel\&.
-.PP
+ .PP
When run as
\fBtsig\-keygen\fR, a domain name can be specified on the command line which will be used as the name of the generated key\&. If no name is specified, the default is
\fBtsig\-key\fR\&.
-.PP
+ .PP
When run as
\fBddns\-confgen\fR, the generated key is accompanied by configuration text and instructions that can be used with
\fBnsupdate\fR
statement\&. (This usage similar to the
\fBrndc\-confgen\fR
command for setting up command channel security\&.)
-.PP
+ .PP
Note that
\fBnamed\fR
itself can configure a local DDNS key for use with
is only needed when a more elaborate configuration is required: for instance, if
\fBnsupdate\fR
is to be used from a remote system\&.
-.SH "OPTIONS"
-.PP
+ .SH "OPTIONS"
+ .PP
\-a \fIalgorithm\fR
.RS 4
-Specifies the algorithm to use for the TSIG key\&. Available choices are: hmac\-md5, hmac\-sha1, hmac\-sha224, hmac\-sha256, hmac\-sha384 and hmac\-sha512\&. The default is hmac\-sha256\&. Options are case\-insensitive, and the "hmac\-" prefix may be omitted\&.
-.RE
-.PP
+ Specifies the algorithm to use for the TSIG key\&. Available choices are: hmac\-md5, hmac\-sha1, hmac\-sha224, hmac\-sha256, hmac\-sha384 and hmac\-sha512\&. The default is hmac\-sha256\&. Options are case\-insensitive, and the "hmac\-" prefix may be omitted\&.
+ .RE
+ .PP
\-h
.RS 4
-Prints a short summary of options and arguments\&.
-.RE
-.PP
+ Prints a short summary of options and arguments\&.
+ .RE
+ .PP
\-k \fIkeyname\fR
.RS 4
-Specifies the key name of the DDNS authentication key\&. The default is
+ Specifies the key name of the DDNS authentication key\&. The default is
\fBddns\-key\fR
when neither the
\fB\-s\fR
as a separate label followed by the argument of the option, e\&.g\&.,
\fBddns\-key\&.example\&.com\&.\fR
The key name must have the format of a valid domain name, consisting of letters, digits, hyphens and periods\&.
-.RE
-.PP
+ .RE
+ .PP
\-q
.RS 4
-(\fBddns\-confgen\fR
+ (\fBddns\-confgen\fR
only\&.) Quiet mode: Print only the key, with no explanatory text or usage examples; This is essentially identical to
\fBtsig\-keygen\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-r \fIrandomfile\fR
.RS 4
-Specifies a source of random data for generating the authorization\&. If the operating system does not provide a
+ Specifies a source of random data for generating the authorization\&. If the operating system does not provide a
/dev/random
or equivalent device, the default source of randomness is keyboard input\&.
randomdev
specifies the name of a character device or file containing random data to be used instead of the default\&. The special value
keyboard
indicates that keyboard input should be used\&.
-.RE
-.PP
+ .RE
+ .PP
\-s \fIname\fR
.RS 4
-(\fBddns\-confgen\fR
+ (\fBddns\-confgen\fR
only\&.) Generate configuration example to allow dynamic updates of a single hostname\&. The example
\fBnamed\&.conf\fR
text shows how to set an update policy for the specified
using the "name" nametype\&. The default key name is ddns\-key\&.\fIname\fR\&. Note that the "self" nametype cannot be used, since the name to be updated may differ from the key name\&. This option cannot be used with the
\fB\-z\fR
option\&.
-.RE
-.PP
+ .RE
+ .PP
\-z \fIzone\fR
.RS 4
-(\fBddns\-confgen\fR
+ (\fBddns\-confgen\fR
only\&.) Generate configuration example to allow dynamic updates of a zone: The example
\fBnamed\&.conf\fR
text shows how to set an update policy for the specified
\fIzone\fR\&. This option cannot be used with the
\fB\-s\fR
option\&.
-.RE
-.SH "SEE ALSO"
-.PP
+ .RE
+ .SH "SEE ALSO"
+ .PP
\fBnsupdate\fR(1),
\fBnamed.conf\fR(5),
\fBnamed\fR(8),
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>ddns-confgen</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.ddns-confgen"></a><div class="titlepage"></div>
'\" t
.\" Title: rndc-confgen
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2013-03-14
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
rndc-confgen \- rndc key generation tool
-.SH "SYNOPSIS"
-.HP \w'\fBrndc\-confgen\fR\ 'u
-\fBrndc\-confgen\fR [\fB\-a\fR] [\fB\-A\ \fR\fB\fIalgorithm\fR\fR] [\fB\-b\ \fR\fB\fIkeysize\fR\fR] [\fB\-c\ \fR\fB\fIkeyfile\fR\fR] [\fB\-h\fR] [\fB\-k\ \fR\fB\fIkeyname\fR\fR] [\fB\-p\ \fR\fB\fIport\fR\fR] [\fB\-r\ \fR\fB\fIrandomfile\fR\fR] [\fB\-s\ \fR\fB\fIaddress\fR\fR] [\fB\-t\ \fR\fB\fIchrootdir\fR\fR] [\fB\-u\ \fR\fB\fIuser\fR\fR]
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBrndc\-confgen\fR\ 'u
+ \fBrndc\-confgen\fR
+ [\fB\-a\fR]
+ [\fB\-A\ \fR\fB\fIalgorithm\fR\fR]
+ [\fB\-b\ \fR\fB\fIkeysize\fR\fR]
+ [\fB\-c\ \fR\fB\fIkeyfile\fR\fR]
+ [\fB\-h\fR]
+ [\fB\-k\ \fR\fB\fIkeyname\fR\fR]
+ [\fB\-p\ \fR\fB\fIport\fR\fR]
+ [\fB\-r\ \fR\fB\fIrandomfile\fR\fR]
+ [\fB\-s\ \fR\fB\fIaddress\fR\fR]
+ [\fB\-t\ \fR\fB\fIchrootdir\fR\fR]
+ [\fB\-u\ \fR\fB\fIuser\fR\fR]
+ .SH "DESCRIPTION"
+ .PP
\fBrndc\-confgen\fR
generates configuration files for
\fBrndc\fR\&. It can be used as a convenient alternative to writing the
file and a
\fBcontrols\fR
statement altogether\&.
-.SH "OPTIONS"
-.PP
+ .SH "OPTIONS"
+ .PP
\-a
.RS 4
-Do automatic
+ Do automatic
\fBrndc\fR
configuration\&. This creates a file
rndc\&.key
\fBnamed\fR
on the local host with no further configuration\&.
.sp
-Running
+ Running
\fBrndc\-confgen \-a\fR
allows BIND 9 and
\fBrndc\fR
named\&.conf
file\&.
.sp
-If a more elaborate configuration than that generated by
+ If a more elaborate configuration than that generated by
\fBrndc\-confgen \-a\fR
is required, for example if rndc is to be used remotely, you should run
\fBrndc\-confgen\fR
and
named\&.conf
as directed\&.
-.RE
-.PP
+ .RE
+ .PP
\-A \fIalgorithm\fR
.RS 4
-Specifies the algorithm to use for the TSIG key\&. Available choices are: hmac\-md5, hmac\-sha1, hmac\-sha224, hmac\-sha256, hmac\-sha384 and hmac\-sha512\&. The default is hmac\-md5 or if MD5 was disabled hmac\-sha256\&.
-.RE
-.PP
+ Specifies the algorithm to use for the TSIG key\&. Available choices are: hmac\-md5, hmac\-sha1, hmac\-sha224, hmac\-sha256, hmac\-sha384 and hmac\-sha512\&. The default is hmac\-md5 or if MD5 was disabled hmac\-sha256\&.
+ .RE
+ .PP
\-b \fIkeysize\fR
.RS 4
-Specifies the size of the authentication key in bits\&. Must be between 1 and 512 bits; the default is the hash size\&.
-.RE
-.PP
+ Specifies the size of the authentication key in bits\&. Must be between 1 and 512 bits; the default is the hash size\&.
+ .RE
+ .PP
\-c \fIkeyfile\fR
.RS 4
-Used with the
+ Used with the
\fB\-a\fR
option to specify an alternate location for
rndc\&.key\&.
-.RE
-.PP
+ .RE
+ .PP
\-h
.RS 4
-Prints a short summary of the options and arguments to
+ Prints a short summary of the options and arguments to
\fBrndc\-confgen\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-k \fIkeyname\fR
.RS 4
-Specifies the key name of the rndc authentication key\&. This must be a valid domain name\&. The default is
+ Specifies the key name of the rndc authentication key\&. This must be a valid domain name\&. The default is
\fBrndc\-key\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-p \fIport\fR
.RS 4
-Specifies the command channel port where
+ Specifies the command channel port where
\fBnamed\fR
listens for connections from
\fBrndc\fR\&. The default is 953\&.
-.RE
-.PP
+ .RE
+ .PP
\-r \fIrandomfile\fR
.RS 4
-Specifies a source of random data for generating the authorization\&. If the operating system does not provide a
+ Specifies a source of random data for generating the authorization\&. If the operating system does not provide a
/dev/random
or equivalent device, the default source of randomness is keyboard input\&.
randomdev
specifies the name of a character device or file containing random data to be used instead of the default\&. The special value
keyboard
indicates that keyboard input should be used\&.
-.RE
-.PP
+ .RE
+ .PP
\-s \fIaddress\fR
.RS 4
-Specifies the IP address where
+ Specifies the IP address where
\fBnamed\fR
listens for command channel connections from
\fBrndc\fR\&. The default is the loopback address 127\&.0\&.0\&.1\&.
-.RE
-.PP
+ .RE
+ .PP
\-t \fIchrootdir\fR
.RS 4
-Used with the
+ Used with the
\fB\-a\fR
option to specify a directory where
\fBnamed\fR
rndc\&.key
will be written relative to this directory so that it will be found by the chrooted
\fBnamed\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-u \fIuser\fR
.RS 4
-Used with the
+ Used with the
\fB\-a\fR
option to set the owner of the
rndc\&.key
file generated\&. If
\fB\-t\fR
is also specified only the file in the chroot area has its owner changed\&.
-.RE
-.SH "EXAMPLES"
-.PP
+ .RE
+ .SH "EXAMPLES"
+ .PP
To allow
\fBrndc\fR
to be used with no manual configuration, run
-.PP
+ .PP
\fBrndc\-confgen \-a\fR
-.PP
+ .PP
To print a sample
rndc\&.conf
file and corresponding
\fBkey\fR
statements to be manually inserted into
named\&.conf, run
-.PP
+ .PP
\fBrndc\-confgen\fR
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBrndc\fR(8),
\fBrndc.conf\fR(5),
\fBnamed\fR(8),
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>rndc-confgen</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.rndc-confgen"></a><div class="titlepage"></div>
'\" t
.\" Title: delv
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2014-04-23
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
delv \- DNS lookup and validation utility
-.SH "SYNOPSIS"
-.HP \w'\fBdelv\fR\ 'u
-\fBdelv\fR [@server] [[\fB\-4\fR] | [\fB\-6\fR]] [\fB\-a\ \fR\fB\fIanchor\-file\fR\fR] [\fB\-b\ \fR\fB\fIaddress\fR\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-d\ \fR\fB\fIlevel\fR\fR] [\fB\-i\fR] [\fB\-m\fR] [\fB\-p\ \fR\fB\fIport#\fR\fR] [\fB\-q\ \fR\fB\fIname\fR\fR] [\fB\-t\ \fR\fB\fItype\fR\fR] [\fB\-x\ \fR\fB\fIaddr\fR\fR] [name] [type] [class] [queryopt...]
-.HP \w'\fBdelv\fR\ 'u
-\fBdelv\fR [\fB\-h\fR]
-.HP \w'\fBdelv\fR\ 'u
-\fBdelv\fR [\fB\-v\fR]
-.HP \w'\fBdelv\fR\ 'u
-\fBdelv\fR [queryopt...] [query...]
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBdelv\fR\ 'u
+ \fBdelv\fR
+ [@server]
+ [
+ | [\fB\-4\fR]
+ | [\fB\-6\fR]
+ ]
+ [\fB\-a\ \fR\fB\fIanchor\-file\fR\fR]
+ [\fB\-b\ \fR\fB\fIaddress\fR\fR]
+ [\fB\-c\ \fR\fB\fIclass\fR\fR]
+ [\fB\-d\ \fR\fB\fIlevel\fR\fR]
+ [\fB\-i\fR]
+ [\fB\-m\fR]
+ [\fB\-p\ \fR\fB\fIport#\fR\fR]
+ [\fB\-q\ \fR\fB\fIname\fR\fR]
+ [\fB\-t\ \fR\fB\fItype\fR\fR]
+ [\fB\-x\ \fR\fB\fIaddr\fR\fR]
+ [name]
+ [type]
+ [class]
+ [queryopt...]
+ .HP \w'\fBdelv\fR\ 'u
+ \fBdelv\fR
+ [\fB\-h\fR]
+ .HP \w'\fBdelv\fR\ 'u
+ \fBdelv\fR
+ [\fB\-v\fR]
+ .HP \w'\fBdelv\fR\ 'u
+ \fBdelv\fR
+ [queryopt...]
+ [query...]
+ .SH "DESCRIPTION"
+ .PP
\fBdelv\fR
is a tool for sending DNS queries and validating the results, using the same internal resolver and validator logic as
\fBnamed\fR\&.
-.PP
+ .PP
\fBdelv\fR
will send to a specified name server all queries needed to fetch and validate the requested data; this includes the original requested query, subsequent queries to follow CNAME or DNAME chains, and queries for DNSKEY, DS and DLV records to establish a chain of trust for DNSSEC validation\&. It does not perform iterative resolution, but simulates the behavior of a name server configured for DNSSEC validating and forwarding\&.
-.PP
+ .PP
By default, responses are validated using built\-in DNSSEC trust anchor for the root zone ("\&.")\&. Records returned by
\fBdelv\fR
are either fully validated or were not signed\&. If validation fails, an explanation of the failure is included in the output; the validation process can be traced in detail\&. Because
\fBdelv\fR
does not rely on an external server to carry out validation, it can be used to check the validity of DNS responses in environments where local name servers may not be trustworthy\&.
-.PP
+ .PP
Unless it is told to query a specific name server,
\fBdelv\fR
will try each of the servers listed in
/etc/resolv\&.conf\&. If no usable server addresses are found,
\fBdelv\fR
will send queries to the localhost addresses (127\&.0\&.0\&.1 for IPv4, ::1 for IPv6)\&.
-.PP
+ .PP
When no command line arguments or options are given,
\fBdelv\fR
will perform an NS query for "\&." (the root zone)\&.
-.SH "SIMPLE USAGE"
-.PP
+ .SH "SIMPLE USAGE"
+ .PP
A typical invocation of
\fBdelv\fR
looks like:
.\}
.sp
where:
-.PP
+ .PP
\fBserver\fR
.RS 4
-is the name or IP address of the name server to query\&. This can be an IPv4 address in dotted\-decimal notation or an IPv6 address in colon\-delimited notation\&. When the supplied
+ is the name or IP address of the name server to query\&. This can be an IPv4 address in dotted\-decimal notation or an IPv6 address in colon\-delimited notation\&. When the supplied
\fIserver\fR
argument is a hostname,
\fBdelv\fR
\fInot\fR
validated by DNSSEC)\&.
.sp
-If no
+ If no
\fIserver\fR
argument is provided,
\fBdelv\fR
options are in use, then only addresses for the corresponding transport will be tried\&. If no usable addresses are found,
\fBdelv\fR
will send queries to the localhost addresses (127\&.0\&.0\&.1 for IPv4, ::1 for IPv6)\&.
-.RE
-.PP
+ .RE
+ .PP
\fBname\fR
.RS 4
-is the domain name to be looked up\&.
-.RE
-.PP
+ is the domain name to be looked up\&.
+ .RE
+ .PP
\fBtype\fR
.RS 4
-indicates what type of query is required \(em ANY, A, MX, etc\&.
+ indicates what type of query is required \(em ANY, A, MX, etc\&.
\fItype\fR
can be any valid query type\&. If no
\fItype\fR
argument is supplied,
\fBdelv\fR
will perform a lookup for an A record\&.
-.RE
-.SH "OPTIONS"
-.PP
+ .RE
+ .SH "OPTIONS"
+ .PP
\-a \fIanchor\-file\fR
.RS 4
-Specifies a file from which to read DNSSEC trust anchors\&. The default is
+ Specifies a file from which to read DNSSEC trust anchors\&. The default is
/etc/bind\&.keys, which is included with
BIND
9 and contains one or more trust anchors for the root zone ("\&.")\&.
.sp
-Keys that do not match the root zone name are ignored\&. An alternate key name can be specified using the
+ Keys that do not match the root zone name are ignored\&. An alternate key name can be specified using the
\fB+root=NAME\fR
options\&. DNSSEC Lookaside Validation can also be turned on by using the
\fB+dlv=NAME\fR
to specify the name of a zone containing DLV records\&.
.sp
-Note: When reading the trust anchor file,
+ Note: When reading the trust anchor file,
\fBdelv\fR
treats
\fBmanaged\-keys\fR
/etc/bind\&.keys
to use DNSSEC validation in
\fBdelv\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-b \fIaddress\fR
.RS 4
-Sets the source IP address of the query to
+ Sets the source IP address of the query to
\fIaddress\fR\&. This must be a valid address on one of the host\*(Aqs network interfaces or "0\&.0\&.0\&.0" or "::"\&. An optional source port may be specified by appending "#<port>"
-.RE
-.PP
+ .RE
+ .PP
\-c \fIclass\fR
.RS 4
-Sets the query class for the requested data\&. Currently, only class "IN" is supported in
+ Sets the query class for the requested data\&. Currently, only class "IN" is supported in
\fBdelv\fR
and any other value is ignored\&.
-.RE
-.PP
+ .RE
+ .PP
\-d \fIlevel\fR
.RS 4
-Set the systemwide debug level to
+ Set the systemwide debug level to
\fBlevel\fR\&. The allowed range is from 0 to 99\&. The default is 0 (no debugging)\&. Debugging traces from
\fBdelv\fR
become more verbose as the debug level increases\&. See the
\fB+rtrace\fR, and
\fB+vtrace\fR
options below for additional debugging details\&.
-.RE
-.PP
+ .RE
+ .PP
\-h
.RS 4
-Display the
+ Display the
\fBdelv\fR
help usage output and exit\&.
-.RE
-.PP
+ .RE
+ .PP
\-i
.RS 4
-Insecure mode\&. This disables internal DNSSEC validation\&. (Note, however, this does not set the CD bit on upstream queries\&. If the server being queried is performing DNSSEC validation, then it will not return invalid data; this can cause
+ Insecure mode\&. This disables internal DNSSEC validation\&. (Note, however, this does not set the CD bit on upstream queries\&. If the server being queried is performing DNSSEC validation, then it will not return invalid data; this can cause
\fBdelv\fR
to time out\&. When it is necessary to examine invalid data to debug a DNSSEC problem, use
\fBdig +cd\fR\&.)
-.RE
-.PP
+ .RE
+ .PP
\-m
.RS 4
-Enables memory usage debugging\&.
-.RE
-.PP
+ Enables memory usage debugging\&.
+ .RE
+ .PP
\-p \fIport#\fR
.RS 4
-Specifies a destination port to use for queries instead of the standard DNS port number 53\&. This option would be used with a name server that has been configured to listen for queries on a non\-standard port number\&.
-.RE
-.PP
+ Specifies a destination port to use for queries instead of the standard DNS port number 53\&. This option would be used with a name server that has been configured to listen for queries on a non\-standard port number\&.
+ .RE
+ .PP
\-q \fIname\fR
.RS 4
-Sets the query name to
+ Sets the query name to
\fIname\fR\&. While the query name can be specified without using the
\fB\-q\fR, it is sometimes necessary to disambiguate names from types or classes (for example, when looking up the name "ns", which could be misinterpreted as the type NS, or "ch", which could be misinterpreted as class CH)\&.
-.RE
-.PP
+ .RE
+ .PP
\-t \fItype\fR
.RS 4
-Sets the query type to
+ Sets the query type to
\fItype\fR, which can be any valid query type supported in BIND 9 except for zone transfer types AXFR and IXFR\&. As with
\fB\-q\fR, this is useful to distinguish query name type or class when they are ambiguous\&. it is sometimes necessary to disambiguate names from types\&.
.sp
-The default query type is "A", unless the
+ The default query type is "A", unless the
\fB\-x\fR
option is supplied to indicate a reverse lookup, in which case it is "PTR"\&.
-.RE
-.PP
+ .RE
+ .PP
\-v
.RS 4
-Print the
+ Print the
\fBdelv\fR
version and exit\&.
-.RE
-.PP
+ .RE
+ .PP
\-x \fIaddr\fR
.RS 4
-Performs a reverse lookup, mapping an addresses to a name\&.
+ Performs a reverse lookup, mapping an addresses to a name\&.
\fIaddr\fR
is an IPv4 address in dotted\-decimal notation, or a colon\-delimited IPv6 address\&. When
\fB\-x\fR
automatically performs a lookup for a name like
11\&.12\&.13\&.10\&.in\-addr\&.arpa
and sets the query type to PTR\&. IPv6 addresses are looked up using nibble format under the IP6\&.ARPA domain\&.
-.RE
-.PP
+ .RE
+ .PP
\-4
.RS 4
-Forces
+ Forces
\fBdelv\fR
to only use IPv4\&.
-.RE
-.PP
+ .RE
+ .PP
\-6
.RS 4
-Forces
+ Forces
\fBdelv\fR
to only use IPv6\&.
-.RE
-.SH "QUERY OPTIONS"
-.PP
+ .RE
+ .SH "QUERY OPTIONS"
+ .PP
\fBdelv\fR
provides a number of query options which affect the way results are displayed, and in some cases the way lookups are performed\&.
-.PP
+ .PP
Each query option is identified by a keyword preceded by a plus sign (+)\&. Some keywords set or reset an option\&. These may be preceded by the string
no
to negate the meaning of that keyword\&. Other keywords assign values to options like the timeout interval\&. They have the form
\fB+keyword=value\fR\&. The query options are:
-.PP
+ .PP
\fB+[no]cdflag\fR
.RS 4
-Controls whether to set the CD (checking disabled) bit in queries sent by
+ Controls whether to set the CD (checking disabled) bit in queries sent by
\fBdelv\fR\&. This may be useful when troubleshooting DNSSEC problems from behind a validating resolver\&. A validating resolver will block invalid responses, making it difficult to retrieve them for analysis\&. Setting the CD flag on queries will cause the resolver to return invalid responses, which
\fBdelv\fR
can then validate internally and report the errors in detail\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]class\fR
.RS 4
-Controls whether to display the CLASS when printing a record\&. The default is to display the CLASS\&.
-.RE
-.PP
+ Controls whether to display the CLASS when printing a record\&. The default is to display the CLASS\&.
+ .RE
+ .PP
\fB+[no]ttl\fR
.RS 4
-Controls whether to display the TTL when printing a record\&. The default is to display the TTL\&.
-.RE
-.PP
+ Controls whether to display the TTL when printing a record\&. The default is to display the TTL\&.
+ .RE
+ .PP
\fB+[no]rtrace\fR
.RS 4
-Toggle resolver fetch logging\&. This reports the name and type of each query sent by
+ Toggle resolver fetch logging\&. This reports the name and type of each query sent by
\fBdelv\fR
in the process of carrying out the resolution and validation process: this includes including the original query and all subsequent queries to follow CNAMEs and to establish a chain of trust for DNSSEC validation\&.
.sp
-This is equivalent to setting the debug level to 1 in the "resolver" logging category\&. Setting the systemwide debug level to 1 using the
+ This is equivalent to setting the debug level to 1 in the "resolver" logging category\&. Setting the systemwide debug level to 1 using the
\fB\-d\fR
option will product the same output (but will affect other logging categories as well)\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]mtrace\fR
.RS 4
-Toggle message logging\&. This produces a detailed dump of the responses received by
+ Toggle message logging\&. This produces a detailed dump of the responses received by
\fBdelv\fR
in the process of carrying out the resolution and validation process\&.
.sp
-This is equivalent to setting the debug level to 10 for the "packets" module of the "resolver" logging category\&. Setting the systemwide debug level to 10 using the
+ This is equivalent to setting the debug level to 10 for the "packets" module of the "resolver" logging category\&. Setting the systemwide debug level to 10 using the
\fB\-d\fR
option will produce the same output (but will affect other logging categories as well)\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]vtrace\fR
.RS 4
-Toggle validation logging\&. This shows the internal process of the validator as it determines whether an answer is validly signed, unsigned, or invalid\&.
+ Toggle validation logging\&. This shows the internal process of the validator as it determines whether an answer is validly signed, unsigned, or invalid\&.
.sp
-This is equivalent to setting the debug level to 3 for the "validator" module of the "dnssec" logging category\&. Setting the systemwide debug level to 3 using the
+ This is equivalent to setting the debug level to 3 for the "validator" module of the "dnssec" logging category\&. Setting the systemwide debug level to 3 using the
\fB\-d\fR
option will produce the same output (but will affect other logging categories as well)\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]short\fR
.RS 4
-Provide a terse answer\&. The default is to print the answer in a verbose form\&.
-.RE
-.PP
+ Provide a terse answer\&. The default is to print the answer in a verbose form\&.
+ .RE
+ .PP
\fB+[no]comments\fR
.RS 4
-Toggle the display of comment lines in the output\&. The default is to print comments\&.
-.RE
-.PP
+ Toggle the display of comment lines in the output\&. The default is to print comments\&.
+ .RE
+ .PP
\fB+[no]rrcomments\fR
.RS 4
-Toggle the display of per\-record comments in the output (for example, human\-readable key information about DNSKEY records)\&. The default is to print per\-record comments\&.
-.RE
-.PP
+ Toggle the display of per\-record comments in the output (for example, human\-readable key information about DNSKEY records)\&. The default is to print per\-record comments\&.
+ .RE
+ .PP
\fB+[no]crypto\fR
.RS 4
-Toggle the display of cryptographic fields in DNSSEC records\&. The contents of these field are unnecessary to debug most DNSSEC validation failures and removing them makes it easier to see the common failures\&. The default is to display the fields\&. When omitted they are replaced by the string "[omitted]" or in the DNSKEY case the key id is displayed as the replacement, e\&.g\&. "[ key id = value ]"\&.
-.RE
-.PP
+ Toggle the display of cryptographic fields in DNSSEC records\&. The contents of these field are unnecessary to debug most DNSSEC validation failures and removing them makes it easier to see the common failures\&. The default is to display the fields\&. When omitted they are replaced by the string "[omitted]" or in the DNSKEY case the key id is displayed as the replacement, e\&.g\&. "[ key id = value ]"\&.
+ .RE
+ .PP
\fB+[no]trust\fR
.RS 4
-Controls whether to display the trust level when printing a record\&. The default is to display the trust level\&.
-.RE
-.PP
+ Controls whether to display the trust level when printing a record\&. The default is to display the trust level\&.
+ .RE
+ .PP
\fB+[no]split[=W]\fR
.RS 4
-Split long hex\- or base64\-formatted fields in resource records into chunks of
+ Split long hex\- or base64\-formatted fields in resource records into chunks of
\fIW\fR
characters (where
\fIW\fR
or
\fI+split=0\fR
causes fields not to be split at all\&. The default is 56 characters, or 44 characters when multiline mode is active\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]all\fR
.RS 4
-Set or clear the display options
+ Set or clear the display options
\fB+[no]comments\fR,
\fB+[no]rrcomments\fR, and
\fB+[no]trust\fR
as a group\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]multiline\fR
.RS 4
-Print long records (such as RRSIG, DNSKEY, and SOA records) in a verbose multi\-line format with human\-readable comments\&. The default is to print each record on a single line, to facilitate machine parsing of the
+ Print long records (such as RRSIG, DNSKEY, and SOA records) in a verbose multi\-line format with human\-readable comments\&. The default is to print each record on a single line, to facilitate machine parsing of the
\fBdelv\fR
output\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]dnssec\fR
.RS 4
-Indicates whether to display RRSIG records in the
+ Indicates whether to display RRSIG records in the
\fBdelv\fR
output\&. The default is to do so\&. Note that (unlike in
\fBdig\fR) this does
\fB+noroot\fR
and
\fB+nodlv\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]root[=ROOT]\fR
.RS 4
-Indicates whether to perform conventional (non\-lookaside) DNSSEC validation, and if so, specifies the name of a trust anchor\&. The default is to validate using a trust anchor of "\&." (the root zone), for which there is a built\-in key\&. If specifying a different trust anchor, then
+ Indicates whether to perform conventional (non\-lookaside) DNSSEC validation, and if so, specifies the name of a trust anchor\&. The default is to validate using a trust anchor of "\&." (the root zone), for which there is a built\-in key\&. If specifying a different trust anchor, then
\fB\-a\fR
must be used to specify a file containing the key\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]dlv[=DLV]\fR
.RS 4
-Indicates whether to perform DNSSEC lookaside validation, and if so, specifies the name of the DLV trust anchor\&. The
+ Indicates whether to perform DNSSEC lookaside validation, and if so, specifies the name of the DLV trust anchor\&. The
\fB\-a\fR
option must also be used to specify a file containing the DLV key\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]tcp\fR
.RS 4
-Controls whether to use TCP when sending queries\&. The default is to use UDP unless a truncated response has been received\&.
-.RE
-.PP
+ Controls whether to use TCP when sending queries\&. The default is to use UDP unless a truncated response has been received\&.
+ .RE
+ .PP
\fB+[no]unknownformat\fR
.RS 4
-Print all RDATA in unknown RR type presentation format (RFC 3597)\&. The default is to print RDATA for known types in the type\*(Aqs presentation format\&.
-.RE
-.SH "FILES"
-.PP
+ Print all RDATA in unknown RR type presentation format (RFC 3597)\&. The default is to print RDATA for known types in the type\*(Aqs presentation format\&.
+ .RE
+ .SH "FILES"
+ .PP
/etc/bind\&.keys
-.PP
+ .PP
/etc/resolv\&.conf
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBdig\fR(1),
\fBnamed\fR(8),
RFC4034,
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>delv</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.delv"></a><div class="titlepage"></div>
'\" t
.\" Title: dig
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2014-02-19
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
dig \- DNS lookup utility
-.SH "SYNOPSIS"
-.HP \w'\fBdig\fR\ 'u
-\fBdig\fR [@server] [\fB\-b\ \fR\fB\fIaddress\fR\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-f\ \fR\fB\fIfilename\fR\fR] [\fB\-k\ \fR\fB\fIfilename\fR\fR] [\fB\-m\fR] [\fB\-p\ \fR\fB\fIport#\fR\fR] [\fB\-q\ \fR\fB\fIname\fR\fR] [\fB\-t\ \fR\fB\fItype\fR\fR] [\fB\-v\fR] [\fB\-x\ \fR\fB\fIaddr\fR\fR] [\fB\-y\ \fR\fB\fI[hmac:]\fR\fIname:key\fR\fR] [[\fB\-4\fR] | [\fB\-6\fR]] [name] [type] [class] [queryopt...]
-.HP \w'\fBdig\fR\ 'u
-\fBdig\fR [\fB\-h\fR]
-.HP \w'\fBdig\fR\ 'u
-\fBdig\fR [global\-queryopt...] [query...]
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBdig\fR\ 'u
+ \fBdig\fR
+ [@server]
+ [\fB\-b\ \fR\fB\fIaddress\fR\fR]
+ [\fB\-c\ \fR\fB\fIclass\fR\fR]
+ [\fB\-f\ \fR\fB\fIfilename\fR\fR]
+ [\fB\-k\ \fR\fB\fIfilename\fR\fR]
+ [\fB\-m\fR]
+ [\fB\-p\ \fR\fB\fIport#\fR\fR]
+ [\fB\-q\ \fR\fB\fIname\fR\fR]
+ [\fB\-t\ \fR\fB\fItype\fR\fR]
+ [\fB\-v\fR]
+ [\fB\-x\ \fR\fB\fIaddr\fR\fR]
+ [\fB\-y\ \fR\fB\fI[hmac:]\fR\fIname:key\fR\fR]
+ [
+ | [\fB\-4\fR]
+ | [\fB\-6\fR]
+ ]
+ [name]
+ [type]
+ [class]
+ [queryopt...]
+ .HP \w'\fBdig\fR\ 'u
+ \fBdig\fR
+ [\fB\-h\fR]
+ .HP \w'\fBdig\fR\ 'u
+ \fBdig\fR
+ [global\-queryopt...]
+ [query...]
+ .SH "DESCRIPTION"
+ .PP
\fBdig\fR
is a flexible tool for interrogating DNS name servers\&. It performs DNS lookups and displays the answers that are returned from the name server(s) that were queried\&. Most DNS administrators use
\fBdig\fR
to troubleshoot DNS problems because of its flexibility, ease of use and clarity of output\&. Other lookup tools tend to have less functionality than
\fBdig\fR\&.
-.PP
+ .PP
Although
\fBdig\fR
is normally used with command\-line arguments, it also has a batch mode of operation for reading lookup requests from a file\&. A brief summary of its command\-line arguments and options is printed when the
option is given\&. Unlike earlier versions, the BIND 9 implementation of
\fBdig\fR
allows multiple lookups to be issued from the command line\&.
-.PP
+ .PP
Unless it is told to query a specific name server,
\fBdig\fR
will try each of the servers listed in
/etc/resolv\&.conf\&. If no usable server addresses are found,
\fBdig\fR
will send the query to the local host\&.
-.PP
+ .PP
When no command line arguments or options are given,
\fBdig\fR
will perform an NS query for "\&." (the root)\&.
-.PP
+ .PP
It is possible to set per\-user defaults for
\fBdig\fR
via
${HOME}/\&.digrc\&. This file is read and any options in it are applied before the command line arguments\&. The
\fB\-r\fR
option disables this feature, for scripts that need predictable behaviour\&.
-.PP
+ .PP
The IN and CH class names overlap with the IN and CH top level domain names\&. Either use the
\fB\-t\fR
and
options to specify the type and class, use the
\fB\-q\fR
the specify the domain name, or use "IN\&." and "CH\&." when looking up these top level domains\&.
-.SH "SIMPLE USAGE"
-.PP
+ .SH "SIMPLE USAGE"
+ .PP
A typical invocation of
\fBdig\fR
looks like:
.\}
.sp
where:
-.PP
+ .PP
\fBserver\fR
.RS 4
-is the name or IP address of the name server to query\&. This can be an IPv4 address in dotted\-decimal notation or an IPv6 address in colon\-delimited notation\&. When the supplied
+ is the name or IP address of the name server to query\&. This can be an IPv4 address in dotted\-decimal notation or an IPv6 address in colon\-delimited notation\&. When the supplied
\fIserver\fR
argument is a hostname,
\fBdig\fR
resolves that name before querying that name server\&.
.sp
-If no
+ If no
\fIserver\fR
argument is provided,
\fBdig\fR
options are in use, then only addresses for the corresponding transport will be tried\&. If no usable addresses are found,
\fBdig\fR
will send the query to the local host\&. The reply from the name server that responds is displayed\&.
-.RE
-.PP
+ .RE
+ .PP
\fBname\fR
.RS 4
-is the name of the resource record that is to be looked up\&.
-.RE
-.PP
+ is the name of the resource record that is to be looked up\&.
+ .RE
+ .PP
\fBtype\fR
.RS 4
-indicates what type of query is required \(em ANY, A, MX, SIG, etc\&.
+ indicates what type of query is required \(em ANY, A, MX, SIG, etc\&.
\fItype\fR
can be any valid query type\&. If no
\fItype\fR
argument is supplied,
\fBdig\fR
will perform a lookup for an A record\&.
-.RE
-.SH "OPTIONS"
-.PP
+ .RE
+ .SH "OPTIONS"
+ .PP
\-4
.RS 4
-Use IPv4 only\&.
-.RE
-.PP
+ Use IPv4 only\&.
+ .RE
+ .PP
\-6
.RS 4
-Use IPv6 only\&.
-.RE
-.PP
+ Use IPv6 only\&.
+ .RE
+ .PP
\-b \fIaddress\fR\fI[#port]\fR
.RS 4
-Set the source IP address of the query\&. The
+ Set the source IP address of the query\&. The
\fIaddress\fR
must be a valid address on one of the host\*(Aqs network interfaces, or "0\&.0\&.0\&.0" or "::"\&. An optional port may be specified by appending "#<port>"
-.RE
-.PP
+ .RE
+ .PP
\-c \fIclass\fR
.RS 4
-Set the query class\&. The default
+ Set the query class\&. The default
\fIclass\fR
is IN; other classes are HS for Hesiod records or CH for Chaosnet records\&.
-.RE
-.PP
+ .RE
+ .PP
\-f \fIfile\fR
.RS 4
-Batch mode:
+ Batch mode:
\fBdig\fR
reads a list of lookup requests to process from the given
\fIfile\fR\&. Each line in the file should be organized in the same way they would be presented as queries to
\fBdig\fR
using the command\-line interface\&.
-.RE
-.PP
+ .RE
+ .PP
\-i
.RS 4
-Do reverse IPv6 lookups using the obsolete RFC 1886 IP6\&.INT domain, which is no longer in use\&. Obsolete bit string label queries (RFC 2874) are not attempted\&.
-.RE
-.PP
+ Do reverse IPv6 lookups using the obsolete RFC 1886 IP6\&.INT domain, which is no longer in use\&. Obsolete bit string label queries (RFC 2874) are not attempted\&.
+ .RE
+ .PP
\-k \fIkeyfile\fR
.RS 4
-Sign queries using TSIG using a key read from the given file\&. Key files can be generated using
+ Sign queries using TSIG using a key read from the given file\&. Key files can be generated using
\fBtsig-keygen\fR(8)\&. When using TSIG authentication with
\fBdig\fR, the name server that is queried needs to know the key and algorithm that is being used\&. In BIND, this is done by providing appropriate
\fBkey\fR
\fBserver\fR
statements in
named\&.conf\&.
-.RE
-.PP
+ .RE
+ .PP
\-m
.RS 4
-Enable memory usage debugging\&.
-.RE
-.PP
+ Enable memory usage debugging\&.
+ .RE
+ .PP
\-p \fIport\fR
.RS 4
-Send the query to a non\-standard port on the server, instead of the default port 53\&. This option would be used to test a name server that has been configured to listen for queries on a non\-standard port number\&.
-.RE
-.PP
+ Send the query to a non\-standard port on the server, instead of the default port 53\&. This option would be used to test a name server that has been configured to listen for queries on a non\-standard port number\&.
+ .RE
+ .PP
\-q \fIname\fR
.RS 4
-The domain name to query\&. This is useful to distinguish the
+ The domain name to query\&. This is useful to distinguish the
\fIname\fR
from other arguments\&.
-.RE
-.PP
+ .RE
+ .PP
\-r
.RS 4
-Do not read options from
+ Do not read options from
${HOME}/\&.digrc\&. This is useful for scripts that need predictable behaviour\&.
-.RE
-.PP
+ .RE
+ .PP
\-t \fItype\fR
.RS 4
-The resource record type to query\&. It can be any valid query type\&. If it is a resource record type supported in BIND 9, it can be given by the type mnemonic (such as "NS" or "AAAA")\&. The default query type is "A", unless the
+ The resource record type to query\&. It can be any valid query type\&. If it is a resource record type supported in BIND 9, it can be given by the type mnemonic (such as "NS" or "AAAA")\&. The default query type is "A", unless the
\fB\-x\fR
option is supplied to indicate a reverse lookup\&. A zone transfer can be requested by specifying a type of AXFR\&. When an incremental zone transfer (IXFR) is required, set the
\fItype\fR
ixfr=N\&. The incremental zone transfer will contain the changes made to the zone since the serial number in the zone\*(Aqs SOA record was
\fIN\fR\&.
.sp
-All resource record types can be expressed as "TYPEnn", where "nn" is the number of the type\&. If the resource record type is not supported in BIND 9, the result will be displayed as described in RFC 3597\&.
-.RE
-.PP
+ All resource record types can be expressed as "TYPEnn", where "nn" is the number of the type\&. If the resource record type is not supported in BIND 9, the result will be displayed as described in RFC 3597\&.
+ .RE
+ .PP
\-u
.RS 4
-Print query times in microseconds instead of milliseconds\&.
-.RE
-.PP
+ Print query times in microseconds instead of milliseconds\&.
+ .RE
+ .PP
\-v
.RS 4
-Print the version number and exit\&.
-.RE
-.PP
+ Print the version number and exit\&.
+ .RE
+ .PP
\-x \fIaddr\fR
.RS 4
-Simplified reverse lookups, for mapping addresses to names\&. The
+ Simplified reverse lookups, for mapping addresses to names\&. The
\fIaddr\fR
is an IPv4 address in dotted\-decimal notation, or a colon\-delimited IPv6 address\&. When the
\fB\-x\fR
and sets the query type and class to PTR and IN respectively\&. IPv6 addresses are looked up using nibble format under the IP6\&.ARPA domain (but see also the
\fB\-i\fR
option)\&.
-.RE
-.PP
+ .RE
+ .PP
\-y \fI[hmac:]\fR\fIkeyname:secret\fR
.RS 4
-Sign queries using TSIG with the given authentication key\&.
+ Sign queries using TSIG with the given authentication key\&.
\fIkeyname\fR
is the name of the key, and
\fIsecret\fR
or if MD5 was disabled
hmac\-sha256\&.
.sp
-NOTE: You should use the
+ NOTE: You should use the
\fB\-k\fR
option and avoid the
\fB\-y\fR
the shared secret is supplied as a command line argument in clear text\&. This may be visible in the output from
\fBps\fR(1)
or in a history file maintained by the user\*(Aqs shell\&.
-.RE
-.SH "QUERY OPTIONS"
-.PP
+ .RE
+ .SH "QUERY OPTIONS"
+ .PP
\fBdig\fR
provides a number of query options which affect the way in which lookups are made and the results displayed\&. Some of these set or reset flag bits in the query header, some determine which sections of the answer get printed, and others determine the timeout and retry strategies\&.
-.PP
+ .PP
Each query option is identified by a keyword preceded by a plus sign (+)\&. Some keywords set or reset an option\&. These may be preceded by the string
no
to negate the meaning of that keyword\&. Other keywords assign values to options like the timeout interval\&. They have the form
+cd
is equivalent to
+cdflag\&. The query options are:
-.PP
+ .PP
\fB+[no]aaflag\fR
.RS 4
-A synonym for
+ A synonym for
\fI+[no]aaonly\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]aaonly\fR
.RS 4
-Sets the "aa" flag in the query\&.
-.RE
-.PP
+ Sets the "aa" flag in the query\&.
+ .RE
+ .PP
\fB+[no]additional\fR
.RS 4
-Display [do not display] the additional section of a reply\&. The default is to display it\&.
-.RE
-.PP
+ Display [do not display] the additional section of a reply\&. The default is to display it\&.
+ .RE
+ .PP
\fB+[no]adflag\fR
.RS 4
-Set [do not set] the AD (authentic data) bit in the query\&. This requests the server to return whether all of the answer and authority sections have all been validated as secure according to the security policy of the server\&. AD=1 indicates that all records have been validated as secure and the answer is not from a OPT\-OUT range\&. AD=0 indicate that some part of the answer was insecure or not validated\&. This bit is set by default\&.
-.RE
-.PP
+ Set [do not set] the AD (authentic data) bit in the query\&. This requests the server to return whether all of the answer and authority sections have all been validated as secure according to the security policy of the server\&. AD=1 indicates that all records have been validated as secure and the answer is not from a OPT\-OUT range\&. AD=0 indicate that some part of the answer was insecure or not validated\&. This bit is set by default\&.
+ .RE
+ .PP
\fB+[no]all\fR
.RS 4
-Set or clear all display flags\&.
-.RE
-.PP
+ Set or clear all display flags\&.
+ .RE
+ .PP
\fB+[no]answer\fR
.RS 4
-Display [do not display] the answer section of a reply\&. The default is to display it\&.
-.RE
-.PP
+ Display [do not display] the answer section of a reply\&. The default is to display it\&.
+ .RE
+ .PP
\fB+[no]authority\fR
.RS 4
-Display [do not display] the authority section of a reply\&. The default is to display it\&.
-.RE
-.PP
+ Display [do not display] the authority section of a reply\&. The default is to display it\&.
+ .RE
+ .PP
\fB+[no]badcookie\fR
.RS 4
-Retry lookup with the new server cookie if a BADCOOKIE response is received\&.
-.RE
-.PP
+ Retry lookup with the new server cookie if a BADCOOKIE response is received\&.
+ .RE
+ .PP
\fB+[no]besteffort\fR
.RS 4
-Attempt to display the contents of messages which are malformed\&. The default is to not display malformed answers\&.
-.RE
-.PP
+ Attempt to display the contents of messages which are malformed\&. The default is to not display malformed answers\&.
+ .RE
+ .PP
\fB+bufsize=B\fR
.RS 4
-This option sets the UDP message buffer size advertised using EDNS0 to
+ This option sets the UDP message buffer size advertised using EDNS0 to
\fIB\fR
bytes\&. The maximum and minimum sizes of this buffer are 65535 and 0, respectively\&.
+bufsize=0
to send a EDNS messages with a advertised size of 0 bytes)\&.
+bufsize
restores the default buffer size\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]cdflag\fR
.RS 4
-Set [do not set] the CD (checking disabled) bit in the query\&. This requests the server to not perform DNSSEC validation of responses\&.
-.RE
-.PP
+ Set [do not set] the CD (checking disabled) bit in the query\&. This requests the server to not perform DNSSEC validation of responses\&.
+ .RE
+ .PP
\fB+[no]class\fR
.RS 4
-Display [do not display] the CLASS when printing the record\&.
-.RE
-.PP
+ Display [do not display] the CLASS when printing the record\&.
+ .RE
+ .PP
\fB+[no]cmd\fR
.RS 4
-Toggles the printing of the initial comment in the output, identifying the version of
+ Toggles the printing of the initial comment in the output, identifying the version of
\fBdig\fR
and the query options that have been applied\&. This option always has global effect; it cannot be set globally and then overridden on a per\-lookup basis\&. The default is to print this comment\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]comments\fR
.RS 4
-Toggles the display of some comment lines in the output, containing information about the packet header and OPT pseudosection, and the names of the response section\&. The default is to print these comments\&.
+ Toggles the display of some comment lines in the output, containing information about the packet header and OPT pseudosection, and the names of the response section\&. The default is to print these comments\&.
.sp
-Other types of comments in the output are not affected by this option, but can be controlled using other command line switches\&. These include
+ Other types of comments in the output are not affected by this option, but can be controlled using other command line switches\&. These include
\fB+[no]cmd\fR,
\fB+[no]question\fR,
\fB+[no]stats\fR, and
\fB+[no]rrcomments\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]cookie\fR\fB[=####]\fR
.RS 4
-Send a COOKIE EDNS option, with optional value\&. Replaying a COOKIE from a previous response will allow the server to identify a previous client\&. The default is
+ Send a COOKIE EDNS option, with optional value\&. Replaying a COOKIE from a previous response will allow the server to identify a previous client\&. The default is
\fB+cookie\fR\&.
.sp
-\fB+cookie\fR
+ \fB+cookie\fR
is also set when +trace is set to better emulate the default queries from a nameserver\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]crypto\fR
.RS 4
-Toggle the display of cryptographic fields in DNSSEC records\&. The contents of these field are unnecessary to debug most DNSSEC validation failures and removing them makes it easier to see the common failures\&. The default is to display the fields\&. When omitted they are replaced by the string "[omitted]" or in the DNSKEY case the key id is displayed as the replacement, e\&.g\&. "[ key id = value ]"\&.
-.RE
-.PP
+ Toggle the display of cryptographic fields in DNSSEC records\&. The contents of these field are unnecessary to debug most DNSSEC validation failures and removing them makes it easier to see the common failures\&. The default is to display the fields\&. When omitted they are replaced by the string "[omitted]" or in the DNSKEY case the key id is displayed as the replacement, e\&.g\&. "[ key id = value ]"\&.
+ .RE
+ .PP
\fB+[no]defname\fR
.RS 4
-Deprecated, treated as a synonym for
+ Deprecated, treated as a synonym for
\fI+[no]search\fR
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]dnssec\fR
.RS 4
-Requests DNSSEC records be sent by setting the DNSSEC OK bit (DO) in the OPT record in the additional section of the query\&.
-.RE
-.PP
+ Requests DNSSEC records be sent by setting the DNSSEC OK bit (DO) in the OPT record in the additional section of the query\&.
+ .RE
+ .PP
\fB+domain=somename\fR
.RS 4
-Set the search list to contain the single domain
+ Set the search list to contain the single domain
\fIsomename\fR, as if specified in a
\fBdomain\fR
directive in
/etc/resolv\&.conf, and enable search list processing as if the
\fI+search\fR
option were given\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+dscp=value\fR
.RS 4
-Set the DSCP code point to be used when sending the query\&. Valid DSCP code points are in the range [0\&.\&.63]\&. By default no code point is explicitly set\&.
-.RE
-.PP
+ Set the DSCP code point to be used when sending the query\&. Valid DSCP code points are in the range [0\&.\&.63]\&. By default no code point is explicitly set\&.
+ .RE
+ .PP
\fB+[no]edns[=#]\fR
.RS 4
-Specify the EDNS version to query with\&. Valid values are 0 to 255\&. Setting the EDNS version will cause a EDNS query to be sent\&.
+ Specify the EDNS version to query with\&. Valid values are 0 to 255\&. Setting the EDNS version will cause a EDNS query to be sent\&.
\fB+noedns\fR
clears the remembered EDNS version\&. EDNS is set to 0 by default\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]ednsflags[=#]\fR
.RS 4
-Set the must\-be\-zero EDNS flags bits (Z bits) to the specified value\&. Decimal, hex and octal encodings are accepted\&. Setting a named flag (e\&.g\&. DO) will silently be ignored\&. By default, no Z bits are set\&.
-.RE
-.PP
+ Set the must\-be\-zero EDNS flags bits (Z bits) to the specified value\&. Decimal, hex and octal encodings are accepted\&. Setting a named flag (e\&.g\&. DO) will silently be ignored\&. By default, no Z bits are set\&.
+ .RE
+ .PP
\fB+[no]ednsnegotiation\fR
.RS 4
-Enable / disable EDNS version negotiation\&. By default EDNS version negotiation is enabled\&.
-.RE
-.PP
+ Enable / disable EDNS version negotiation\&. By default EDNS version negotiation is enabled\&.
+ .RE
+ .PP
\fB+[no]ednsopt[=code[:value]]\fR
.RS 4
-Specify EDNS option with code point
+ Specify EDNS option with code point
\fBcode\fR
and optionally payload of
\fBvalue\fR
ECS), or an arbitrary numeric value\&.
\fB+noednsopt\fR
clears the EDNS options to be sent\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]expire\fR
.RS 4
-Send an EDNS Expire option\&.
-.RE
-.PP
+ Send an EDNS Expire option\&.
+ .RE
+ .PP
\fB+[no]fail\fR
.RS 4
-Do not try the next server if you receive a SERVFAIL\&. The default is to not try the next server which is the reverse of normal stub resolver behavior\&.
-.RE
-.PP
+ Do not try the next server if you receive a SERVFAIL\&. The default is to not try the next server which is the reverse of normal stub resolver behavior\&.
+ .RE
+ .PP
\fB+[no]header\-only\fR
.RS 4
-Send a query with a DNS header without a question section\&. The default is to add a question section\&. The query type and query name are ignored when this is set\&.
-.RE
-.PP
+ Send a query with a DNS header without a question section\&. The default is to add a question section\&. The query type and query name are ignored when this is set\&.
+ .RE
+ .PP
\fB+[no]identify\fR
.RS 4
-Show [or do not show] the IP address and port number that supplied the answer when the
+ Show [or do not show] the IP address and port number that supplied the answer when the
\fI+short\fR
option is enabled\&. If short form answers are requested, the default is not to show the source address and port number of the server that provided the answer\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]idnin\fR
.RS 4
-Process [do not process] IDN domain names on input\&. This requires IDN SUPPORT to have been enabled at compile time\&.
+ Process [do not process] IDN domain names on input\&. This requires IDN SUPPORT to have been enabled at compile time\&.
.sp
-The default is to process IDN input when standard output is a tty\&. The IDN processing on input is disabled when dig output is redirected to files, pipes, and other non\-tty file descriptors\&.
-.RE
-.PP
+ The default is to process IDN input when standard output is a tty\&. The IDN processing on input is disabled when dig output is redirected to files, pipes, and other non\-tty file descriptors\&.
+ .RE
+ .PP
\fB+[no]idnout\fR
.RS 4
-Convert [do not convert] puny code on output\&. This requires IDN SUPPORT to have been enabled at compile time\&.
+ Convert [do not convert] puny code on output\&. This requires IDN SUPPORT to have been enabled at compile time\&.
.sp
-The default is to process puny code on output when standard output is a tty\&. The puny code processing on output is disabled when dig output is redirected to files, pipes, and other non\-tty file descriptors\&.
-.RE
-.PP
+ The default is to process puny code on output when standard output is a tty\&. The puny code processing on output is disabled when dig output is redirected to files, pipes, and other non\-tty file descriptors\&.
+ .RE
+ .PP
\fB+[no]ignore\fR
.RS 4
-Ignore truncation in UDP responses instead of retrying with TCP\&. By default, TCP retries are performed\&.
-.RE
-.PP
+ Ignore truncation in UDP responses instead of retrying with TCP\&. By default, TCP retries are performed\&.
+ .RE
+ .PP
\fB+[no]keepopen\fR
.RS 4
-Keep the TCP socket open between queries and reuse it rather than creating a new TCP socket for each lookup\&. The default is
+ Keep the TCP socket open between queries and reuse it rather than creating a new TCP socket for each lookup\&. The default is
\fB+nokeepopen\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]mapped\fR
.RS 4
-Allow mapped IPv4 over IPv6 addresses to be used\&. The default is
+ Allow mapped IPv4 over IPv6 addresses to be used\&. The default is
\fB+mapped\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]multiline\fR
.RS 4
-Print records like the SOA records in a verbose multi\-line format with human\-readable comments\&. The default is to print each record on a single line, to facilitate machine parsing of the
+ Print records like the SOA records in a verbose multi\-line format with human\-readable comments\&. The default is to print each record on a single line, to facilitate machine parsing of the
\fBdig\fR
output\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+ndots=D\fR
.RS 4
-Set the number of dots that have to appear in
+ Set the number of dots that have to appear in
\fIname\fR
to
\fID\fR
if
\fB+search\fR
is set\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]nsid\fR
.RS 4
-Include an EDNS name server ID request when sending a query\&.
-.RE
-.PP
+ Include an EDNS name server ID request when sending a query\&.
+ .RE
+ .PP
\fB+[no]nssearch\fR
.RS 4
-When this option is set,
+ When this option is set,
\fBdig\fR
attempts to find the authoritative name servers for the zone containing the name being looked up and display the SOA record that each name server has for the zone\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]onesoa\fR
.RS 4
-Print only one (starting) SOA record when performing an AXFR\&. The default is to print both the starting and ending SOA records\&.
-.RE
-.PP
+ Print only one (starting) SOA record when performing an AXFR\&. The default is to print both the starting and ending SOA records\&.
+ .RE
+ .PP
\fB+[no]opcode=value\fR
.RS 4
-Set [restore] the DNS message opcode to the specified value\&. The default value is QUERY (0)\&.
-.RE
-.PP
+ Set [restore] the DNS message opcode to the specified value\&. The default value is QUERY (0)\&.
+ .RE
+ .PP
\fB+[no]qr\fR
.RS 4
-Toggles the display of the query message as it is sent\&. By default, the query is not printed\&.
-.RE
-.PP
+ Toggles the display of the query message as it is sent\&. By default, the query is not printed\&.
+ .RE
+ .PP
\fB+[no]question\fR
.RS 4
-Toggles the display of the question section of a query when an answer is returned\&. The default is to print the question section as a comment\&.
-.RE
-.PP
+ Toggles the display of the question section of a query when an answer is returned\&. The default is to print the question section as a comment\&.
+ .RE
+ .PP
\fB+[no]rdflag\fR
.RS 4
-A synonym for
+ A synonym for
\fI+[no]recurse\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]recurse\fR
.RS 4
-Toggle the setting of the RD (recursion desired) bit in the query\&. This bit is set by default, which means
+ Toggle the setting of the RD (recursion desired) bit in the query\&. This bit is set by default, which means
\fBdig\fR
normally sends recursive queries\&. Recursion is automatically disabled when using the
\fI+nssearch\fR
option, and when using
\fI+trace\fR
except for an initial recursive query to get the list of root servers\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+retry=T\fR
.RS 4
-Sets the number of times to retry UDP queries to server to
+ Sets the number of times to retry UDP queries to server to
\fIT\fR
instead of the default, 2\&. Unlike
\fI+tries\fR, this does not include the initial query\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]rrcomments\fR
.RS 4
-Toggle the display of per\-record comments in the output (for example, human\-readable key information about DNSKEY records)\&. The default is not to print record comments unless multiline mode is active\&.
-.RE
-.PP
+ Toggle the display of per\-record comments in the output (for example, human\-readable key information about DNSKEY records)\&. The default is not to print record comments unless multiline mode is active\&.
+ .RE
+ .PP
\fB+[no]search\fR
.RS 4
-Use [do not use] the search list defined by the searchlist or domain directive in
+ Use [do not use] the search list defined by the searchlist or domain directive in
resolv\&.conf
(if any)\&. The search list is not used by default\&.
.sp
-\*(Aqndots\*(Aq from
+ \*(Aqndots\*(Aq from
resolv\&.conf
(default 1) which may be overridden by
\fI+ndots\fR
determines if the name will be treated as relative or not and hence whether a search is eventually performed or not\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]short\fR
.RS 4
-Provide a terse answer\&. The default is to print the answer in a verbose form\&. This option always has global effect; it cannot be set globally and then overridden on a per\-lookup basis\&.
-.RE
-.PP
+ Provide a terse answer\&. The default is to print the answer in a verbose form\&. This option always has global effect; it cannot be set globally and then overridden on a per\-lookup basis\&.
+ .RE
+ .PP
\fB+[no]showsearch\fR
.RS 4
-Perform [do not perform] a search showing intermediate results\&.
-.RE
-.PP
+ Perform [do not perform] a search showing intermediate results\&.
+ .RE
+ .PP
\fB+[no]sigchase\fR
.RS 4
-Chase DNSSEC signature chains\&. Requires dig be compiled with \-DDIG_SIGCHASE\&. This feature is deprecated\&. Use
+ Chase DNSSEC signature chains\&. Requires dig be compiled with \-DDIG_SIGCHASE\&. This feature is deprecated\&. Use
\fBdelv\fR
instead\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+split=W\fR
.RS 4
-Split long hex\- or base64\-formatted fields in resource records into chunks of
+ Split long hex\- or base64\-formatted fields in resource records into chunks of
\fIW\fR
characters (where
\fIW\fR
or
\fI+split=0\fR
causes fields not to be split at all\&. The default is 56 characters, or 44 characters when multiline mode is active\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]stats\fR
.RS 4
-Toggles the printing of statistics: when the query was made, the size of the reply and so on\&. The default behavior is to print the query statistics as a comment after each lookup\&.
-.RE
-.PP
+ Toggles the printing of statistics: when the query was made, the size of the reply and so on\&. The default behavior is to print the query statistics as a comment after each lookup\&.
+ .RE
+ .PP
\fB+[no]subnet=addr[/prefix\-length]\fR
.RS 4
-Send (don\*(Aqt send) an EDNS Client Subnet option with the specified IP address or network prefix\&.
+ Send (don\*(Aqt send) an EDNS Client Subnet option with the specified IP address or network prefix\&.
.sp
-\fBdig +subnet=0\&.0\&.0\&.0/0\fR, or simply
+ \fBdig +subnet=0\&.0\&.0\&.0/0\fR, or simply
\fBdig +subnet=0\fR
for short, sends an EDNS CLIENT\-SUBNET option with an empty address and a source prefix\-length of zero, which signals a resolver that the client\*(Aqs address information must
\fInot\fR
be used when resolving this query\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]tcp\fR
.RS 4
-Use [do not use] TCP when querying name servers\&. The default behavior is to use UDP unless a type
+ Use [do not use] TCP when querying name servers\&. The default behavior is to use UDP unless a type
any
or
ixfr=N
query is requested, in which case the default is TCP\&. AXFR queries always use TCP\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+timeout=T\fR
.RS 4
-Sets the timeout for a query to
+ Sets the timeout for a query to
\fIT\fR
seconds\&. The default timeout is 5 seconds\&. An attempt to set
\fIT\fR
to less than 1 will result in a query timeout of 1 second being applied\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]topdown\fR
.RS 4
-When chasing DNSSEC signature chains perform a top\-down validation\&. Requires dig be compiled with \-DDIG_SIGCHASE\&. This feature is deprecated\&. Use
+ When chasing DNSSEC signature chains perform a top\-down validation\&. Requires dig be compiled with \-DDIG_SIGCHASE\&. This feature is deprecated\&. Use
\fBdelv\fR
instead\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]trace\fR
.RS 4
-Toggle tracing of the delegation path from the root name servers for the name being looked up\&. Tracing is disabled by default\&. When tracing is enabled,
+ Toggle tracing of the delegation path from the root name servers for the name being looked up\&. Tracing is disabled by default\&. When tracing is enabled,
\fBdig\fR
makes iterative queries to resolve the name being looked up\&. It will follow referrals from the root servers, showing the answer from each server that was used to resolve the lookup\&.
.sp
-If @server is also specified, it affects only the initial query for the root zone name servers\&.
+ If @server is also specified, it affects only the initial query for the root zone name servers\&.
.sp
-\fB+dnssec\fR
+ \fB+dnssec\fR
is also set when +trace is set to better emulate the default queries from a nameserver\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+tries=T\fR
.RS 4
-Sets the number of times to try UDP queries to server to
+ Sets the number of times to try UDP queries to server to
\fIT\fR
instead of the default, 3\&. If
\fIT\fR
is less than or equal to zero, the number of tries is silently rounded up to 1\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+trusted\-key=####\fR
.RS 4
-Specifies a file containing trusted keys to be used with
+ Specifies a file containing trusted keys to be used with
\fB+sigchase\fR\&. Each DNSKEY record must be on its own line\&.
.sp
-If not specified,
+ If not specified,
\fBdig\fR
will look for
/etc/trusted\-key\&.key
trusted\-key\&.key
in the current directory\&.
.sp
-Requires dig be compiled with \-DDIG_SIGCHASE\&. This feature is deprecated\&. Use
+ Requires dig be compiled with \-DDIG_SIGCHASE\&. This feature is deprecated\&. Use
\fBdelv\fR
instead\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]ttlid\fR
.RS 4
-Display [do not display] the TTL when printing the record\&.
-.RE
-.PP
+ Display [do not display] the TTL when printing the record\&.
+ .RE
+ .PP
\fB+[no]ttlunits\fR
.RS 4
-Display [do not display] the TTL in friendly human\-readable time units of "s", "m", "h", "d", and "w", representing seconds, minutes, hours, days and weeks\&. Implies +ttlid\&.
-.RE
-.PP
+ Display [do not display] the TTL in friendly human\-readable time units of "s", "m", "h", "d", and "w", representing seconds, minutes, hours, days and weeks\&. Implies +ttlid\&.
+ .RE
+ .PP
\fB+[no]unknownformat\fR
.RS 4
-Print all RDATA in unknown RR type presentation format (RFC 3597)\&. The default is to print RDATA for known types in the type\*(Aqs presentation format\&.
-.RE
-.PP
+ Print all RDATA in unknown RR type presentation format (RFC 3597)\&. The default is to print RDATA for known types in the type\*(Aqs presentation format\&.
+ .RE
+ .PP
\fB+[no]vc\fR
.RS 4
-Use [do not use] TCP when querying name servers\&. This alternate syntax to
+ Use [do not use] TCP when querying name servers\&. This alternate syntax to
\fI+[no]tcp\fR
is provided for backwards compatibility\&. The "vc" stands for "virtual circuit"\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]zflag\fR
.RS 4
-Set [do not set] the last unassigned DNS header flag in a DNS query\&. This flag is off by default\&.
-.RE
-.SH "MULTIPLE QUERIES"
-.PP
+ Set [do not set] the last unassigned DNS header flag in a DNS query\&. This flag is off by default\&.
+ .RE
+ .SH "MULTIPLE QUERIES"
+ .PP
The BIND 9 implementation of
\fBdig \fR
supports specifying multiple queries on the command line (in addition to supporting the
\fB\-f\fR
batch file option)\&. Each of those queries can be supplied with its own set of flags, options and query options\&.
-.PP
+ .PP
In this case, each
\fIquery\fR
argument represent an individual query in the command\-line syntax described above\&. Each consists of any of the standard options and flags, the name to be looked up, an optional query type and class and any query options that should be applied to that query\&.
-.PP
+ .PP
A global set of query options, which should be applied to all queries, can also be supplied\&. These global query options must precede the first tuple of name, class, type, options, flags, and query options supplied on the command line\&. Any global query options (except the
\fB+[no]cmd\fR
option) can be overridden by a query\-specific set of query options\&. For example:
\fBdig\fR
will not print the initial query when it looks up the NS records for
isc\&.org\&.
-.SH "IDN SUPPORT"
-.PP
+ .SH "IDN SUPPORT"
+ .PP
If
\fBdig\fR
has been built with IDN (internationalized domain name) support, it can accept and display non\-ASCII domain names\&.
\fI+noidnin\fR
and
\fI+noidnout\fR\&.
-.SH "FILES"
-.PP
+ .SH "FILES"
+ .PP
/etc/resolv\&.conf
-.PP
+ .PP
${HOME}/\&.digrc
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBdelv\fR(1),
\fBhost\fR(1),
\fBnamed\fR(8),
\fBdnssec-keygen\fR(8),
RFC 1035\&.
-.SH "BUGS"
-.PP
+ .SH "BUGS"
+ .PP
There are probably too many query options\&.
.SH "AUTHOR"
.PP
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dig</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.dig"></a><div class="titlepage"></div>
'\" t
.\" Title: host
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2009-01-20
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
host \- DNS lookup utility
-.SH "SYNOPSIS"
-.HP \w'\fBhost\fR\ 'u
-\fBhost\fR [\fB\-aCdlnrsTUwv\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-N\ \fR\fB\fIndots\fR\fR] [\fB\-p\ \fR\fB\fIport\fR\fR] [\fB\-R\ \fR\fB\fInumber\fR\fR] [\fB\-t\ \fR\fB\fItype\fR\fR] [\fB\-W\ \fR\fB\fIwait\fR\fR] [\fB\-m\ \fR\fB\fIflag\fR\fR] [[\fB\-4\fR] | [\fB\-6\fR]] [\fB\-v\fR] [\fB\-V\fR] {name} [server]
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBhost\fR\ 'u
+ \fBhost\fR
+ [\fB\-aCdlnrsTUwv\fR]
+ [\fB\-c\ \fR\fB\fIclass\fR\fR]
+ [\fB\-N\ \fR\fB\fIndots\fR\fR]
+ [\fB\-p\ \fR\fB\fIport\fR\fR]
+ [\fB\-R\ \fR\fB\fInumber\fR\fR]
+ [\fB\-t\ \fR\fB\fItype\fR\fR]
+ [\fB\-W\ \fR\fB\fIwait\fR\fR]
+ [\fB\-m\ \fR\fB\fIflag\fR\fR]
+ [
+ | [\fB\-4\fR]
+ | [\fB\-6\fR]
+ ]
+ [\fB\-v\fR]
+ [\fB\-V\fR]
+ {name}
+ [server]
+ .SH "DESCRIPTION"
+ .PP
\fBhost\fR
is a simple utility for performing DNS lookups\&. It is normally used to convert names to IP addresses and vice versa\&. When no arguments or options are given,
\fBhost\fR
prints a short summary of its command line arguments and options\&.
-.PP
+ .PP
\fIname\fR
is the domain name that is to be looked up\&. It can also be a dotted\-decimal IPv4 address or a colon\-delimited IPv6 address, in which case
\fBhost\fR
\fBhost\fR
should query instead of the server or servers listed in
/etc/resolv\&.conf\&.
-.SH "OPTIONS"
-.PP
+ .SH "OPTIONS"
+ .PP
\-4
.RS 4
-Use IPv4 only for query transport\&. See also the
+ Use IPv4 only for query transport\&. See also the
\fB\-6\fR
option\&.
-.RE
-.PP
+ .RE
+ .PP
\-6
.RS 4
-Use IPv6 only for query transport\&. See also the
+ Use IPv6 only for query transport\&. See also the
\fB\-4\fR
option\&.
-.RE
-.PP
+ .RE
+ .PP
\-a
.RS 4
-"All"\&. The
+ "All"\&. The
\fB\-a\fR
option is normally equivalent to
\fB\-v \-t \fR\fBANY\fR\&. It also affects the behaviour of the
\fB\-l\fR
list zone option\&.
-.RE
-.PP
+ .RE
+ .PP
\-c \fIclass\fR
.RS 4
-Query class: This can be used to lookup HS (Hesiod) or CH (Chaosnet) class resource records\&. The default class is IN (Internet)\&.
-.RE
-.PP
+ Query class: This can be used to lookup HS (Hesiod) or CH (Chaosnet) class resource records\&. The default class is IN (Internet)\&.
+ .RE
+ .PP
\-C
.RS 4
-Check consistency:
+ Check consistency:
\fBhost\fR
will query the SOA records for zone
\fIname\fR
from all the listed authoritative name servers for that zone\&. The list of name servers is defined by the NS records that are found for the zone\&.
-.RE
-.PP
+ .RE
+ .PP
\-d
.RS 4
-Print debugging traces\&. Equivalent to the
+ Print debugging traces\&. Equivalent to the
\fB\-v\fR
verbose option\&.
-.RE
-.PP
+ .RE
+ .PP
\-i
.RS 4
-Obsolete\&. Use the IP6\&.INT domain for reverse lookups of IPv6 addresses as defined in RFC1886 and deprecated in RFC4159\&. The default is to use IP6\&.ARPA as specified in RFC3596\&.
-.RE
-.PP
+ Obsolete\&. Use the IP6\&.INT domain for reverse lookups of IPv6 addresses as defined in RFC1886 and deprecated in RFC4159\&. The default is to use IP6\&.ARPA as specified in RFC3596\&.
+ .RE
+ .PP
\-l
.RS 4
-List zone: The
+ List zone: The
\fBhost\fR
command performs a zone transfer of zone
\fIname\fR
and prints out the NS, PTR and address records (A/AAAA)\&.
.sp
-Together, the
+ Together, the
\fB\-l \-a\fR
options print all records in the zone\&.
-.RE
-.PP
+ .RE
+ .PP
\-N \fIndots\fR
.RS 4
-The number of dots that have to be in
+ The number of dots that have to be in
\fIname\fR
for it to be considered absolute\&. The default value is that defined using the ndots statement in
/etc/resolv\&.conf, or 1 if no ndots statement is present\&. Names with fewer dots are interpreted as relative names and will be searched for in the domains listed in the
\fBdomain\fR
directive in
/etc/resolv\&.conf\&.
-.RE
-.PP
+ .RE
+ .PP
\-p \fIport\fR
.RS 4
-Specify the port on the server to query\&. The default is 53\&.
-.RE
-.PP
+ Specify the port on the server to query\&. The default is 53\&.
+ .RE
+ .PP
\-r
.RS 4
-Non\-recursive query: Setting this option clears the RD (recursion desired) bit in the query\&. This should mean that the name server receiving the query will not attempt to resolve
+ Non\-recursive query: Setting this option clears the RD (recursion desired) bit in the query\&. This should mean that the name server receiving the query will not attempt to resolve
\fIname\fR\&. The
\fB\-r\fR
option enables
\fBhost\fR
to mimic the behavior of a name server by making non\-recursive queries and expecting to receive answers to those queries that can be referrals to other name servers\&.
-.RE
-.PP
+ .RE
+ .PP
\-R \fInumber\fR
.RS 4
-Number of retries for UDP queries: If
+ Number of retries for UDP queries: If
\fInumber\fR
is negative or zero, the number of retries will default to 1\&. The default value is 1, or the value of the
\fIattempts\fR
option in
/etc/resolv\&.conf, if set\&.
-.RE
-.PP
+ .RE
+ .PP
\-s
.RS 4
-Do
+ Do
\fInot\fR
send the query to the next nameserver if any server responds with a SERVFAIL response, which is the reverse of normal stub resolver behavior\&.
-.RE
-.PP
+ .RE
+ .PP
\-t \fItype\fR
.RS 4
-Query type: The
+ Query type: The
\fItype\fR
argument can be any recognized query type: CNAME, NS, SOA, TXT, DNSKEY, AXFR, etc\&.
.sp
-When no query type is specified,
+ When no query type is specified,
\fBhost\fR
automatically selects an appropriate query type\&. By default, it looks for A, AAAA, and MX records\&. If the
\fB\-C\fR
\fBhost\fR
will query for PTR records\&.
.sp
-If a query type of IXFR is chosen the starting serial number can be specified by appending an equal followed by the starting serial number (like
+ If a query type of IXFR is chosen the starting serial number can be specified by appending an equal followed by the starting serial number (like
\fB\-t \fR\fBIXFR=12345678\fR)\&.
-.RE
-.PP
+ .RE
+ .PP
\-T, \-U
.RS 4
-TCP/UDP: By default,
+ TCP/UDP: By default,
\fBhost\fR
uses UDP when making queries\&. The
\fB\-T\fR
option makes it use a TCP connection when querying the name server\&. TCP will be automatically selected for queries that require it, such as zone transfer (AXFR) requests\&. Type ANY queries default to TCP but can be forced to UDP initially using
\fB\-U\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-m \fIflag\fR
.RS 4
-Memory usage debugging: the flag can be
+ Memory usage debugging: the flag can be
\fIrecord\fR,
\fIusage\fR, or
\fItrace\fR\&. You can specify the
\fB\-m\fR
option more than once to set multiple flags\&.
-.RE
-.PP
+ .RE
+ .PP
\-v
.RS 4
-Verbose output\&. Equivalent to the
+ Verbose output\&. Equivalent to the
\fB\-d\fR
debug option\&. Verbose output can also be enabled by setting the
\fIdebug\fR
option in
/etc/resolv\&.conf\&.
-.RE
-.PP
+ .RE
+ .PP
\-V
.RS 4
-Print the version number and exit\&.
-.RE
-.PP
+ Print the version number and exit\&.
+ .RE
+ .PP
\-w
.RS 4
-Wait forever: The query timeout is set to the maximum possible\&. See also the
+ Wait forever: The query timeout is set to the maximum possible\&. See also the
\fB\-W\fR
option\&.
-.RE
-.PP
+ .RE
+ .PP
\-W \fIwait\fR
.RS 4
-Timeout: Wait for up to
+ Timeout: Wait for up to
\fIwait\fR
seconds for a reply\&. If
\fIwait\fR
is less than one, the wait interval is set to one second\&.
.sp
-By default,
+ By default,
\fBhost\fR
will wait for 5 seconds for UDP responses and 10 seconds for TCP connections\&. These defaults can be overridden by the
\fItimeout\fR
option in
/etc/resolv\&.conf\&.
.sp
-See also the
+ See also the
\fB\-w\fR
option\&.
-.RE
-.SH "IDN SUPPORT"
-.PP
+ .RE
+ .SH "IDN SUPPORT"
+ .PP
If
\fBhost\fR
has been built with IDN (internationalized domain name) support, it can accept and display non\-ASCII domain names\&.
environment variable\&. The IDN support is disabled if the variable is set when
\fBhost\fR
runs\&.
-.SH "FILES"
-.PP
+ .SH "FILES"
+ .PP
/etc/resolv\&.conf
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBdig\fR(1),
\fBnamed\fR(8)\&.
.SH "AUTHOR"
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>host</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.host"></a><div class="titlepage"></div>
'\" t
.\" Title: nslookup
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2014-01-24
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
nslookup \- query Internet name servers interactively
-.SH "SYNOPSIS"
-.HP \w'\fBnslookup\fR\ 'u
-\fBnslookup\fR [\fB\-option\fR] [name\ |\ \-] [server]
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBnslookup\fR\ 'u
+ \fBnslookup\fR
+ [\fB\-option\fR]
+ [name\ |\ \-]
+ [server]
+ .SH "DESCRIPTION"
+ .PP
\fBNslookup\fR
is a program to query Internet domain name servers\&.
\fBNslookup\fR
has two modes: interactive and non\-interactive\&. Interactive mode allows the user to query name servers for information about various hosts and domains or to print a list of hosts in a domain\&. Non\-interactive mode is used to print just the name and requested information for a host or domain\&.
-.SH "ARGUMENTS"
-.PP
+ .SH "ARGUMENTS"
+ .PP
Interactive mode is entered in the following cases:
.sp
.RS 4
.sp -1
.IP " 1." 4.2
.\}
-when no arguments are given (the default name server will be used)
-.RE
+ when no arguments are given (the default name server will be used)
+ .RE
.sp
.RS 4
.ie n \{\
.sp -1
.IP " 2." 4.2
.\}
-when the first argument is a hyphen (\-) and the second argument is the host name or Internet address of a name server\&.
-.RE
-.PP
+ when the first argument is a hyphen (\-) and the second argument is the host name or Internet address of a name server\&.
+ .RE
+.sp
+ .PP
Non\-interactive mode is used when the name or Internet address of the host to be looked up is given as the first argument\&. The optional second argument specifies the host name or address of a name server\&.
-.PP
+ .PP
Options can also be specified on the command line if they precede the arguments and are prefixed with a hyphen\&. For example, to change the default query type to host information, and the initial timeout to 10 seconds, type:
.sp
.if n \{\
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
The
\fB\-version\fR
option causes
\fBnslookup\fR
to print the version number and immediately exits\&.
-.SH "INTERACTIVE COMMANDS"
-.PP
+ .SH "INTERACTIVE COMMANDS"
+ .PP
\fBhost\fR [server]
.RS 4
-Look up information for host using the current default server or using server, if specified\&. If host is an Internet address and the query type is A or PTR, the name of the host is returned\&. If host is a name and does not have a trailing period, the search list is used to qualify the name\&.
+ Look up information for host using the current default server or using server, if specified\&. If host is an Internet address and the query type is A or PTR, the name of the host is returned\&. If host is a name and does not have a trailing period, the search list is used to qualify the name\&.
.sp
-To look up a host not in the current domain, append a period to the name\&.
-.RE
-.PP
+ To look up a host not in the current domain, append a period to the name\&.
+ .RE
+ .PP
\fBserver\fR \fIdomain\fR
.RS 4
-.RE
-.PP
+ .RE
+ .PP
\fBlserver\fR \fIdomain\fR
.RS 4
-Change the default server to
+ Change the default server to
\fIdomain\fR;
\fBlserver\fR
uses the initial server to look up information about
\fIdomain\fR, while
\fBserver\fR
uses the current default server\&. If an authoritative answer can\*(Aqt be found, the names of servers that might have the answer are returned\&.
-.RE
-.PP
+ .RE
+ .PP
\fBroot\fR
.RS 4
-not implemented
-.RE
-.PP
+ not implemented
+ .RE
+ .PP
\fBfinger\fR
.RS 4
-not implemented
-.RE
-.PP
+ not implemented
+ .RE
+ .PP
\fBls\fR
.RS 4
-not implemented
-.RE
-.PP
+ not implemented
+ .RE
+ .PP
\fBview\fR
.RS 4
-not implemented
-.RE
-.PP
+ not implemented
+ .RE
+ .PP
\fBhelp\fR
.RS 4
-not implemented
-.RE
-.PP
+ not implemented
+ .RE
+ .PP
\fB?\fR
.RS 4
-not implemented
-.RE
-.PP
+ not implemented
+ .RE
+ .PP
\fBexit\fR
.RS 4
-Exits the program\&.
-.RE
-.PP
+ Exits the program\&.
+ .RE
+ .PP
\fBset\fR \fIkeyword\fR\fI[=value]\fR
.RS 4
-This command is used to change state information that affects the lookups\&. Valid keywords are:
-.PP
+ This command is used to change state information that affects the lookups\&. Valid keywords are:
+ .PP
\fBall\fR
.RS 4
-Prints the current values of the frequently used options to
+ Prints the current values of the frequently used options to
\fBset\fR\&. Information about the current default server and host is also printed\&.
-.RE
-.PP
+ .RE
+ .PP
\fBclass=\fR\fIvalue\fR
.RS 4
-Change the query class to one of:
-.PP
+ Change the query class to one of:
+ .PP
\fBIN\fR
.RS 4
-the Internet class
-.RE
-.PP
+ the Internet class
+ .RE
+ .PP
\fBCH\fR
.RS 4
-the Chaos class
-.RE
-.PP
+ the Chaos class
+ .RE
+ .PP
\fBHS\fR
.RS 4
-the Hesiod class
-.RE
-.PP
+ the Hesiod class
+ .RE
+ .PP
\fBANY\fR
.RS 4
-wildcard
-.RE
-.sp
+ wildcard
+ .RE
+ .sp
The class specifies the protocol group of the information\&.
.sp
-(Default = IN; abbreviation = cl)
-.RE
-.PP
+ (Default = IN; abbreviation = cl)
+ .RE
+ .PP
\fB\fI[no]\fR\fR\fBdebug\fR
.RS 4
-Turn on or off the display of the full response packet and any intermediate response packets when searching\&.
+ Turn on or off the display of the full response packet and any intermediate response packets when searching\&.
.sp
-(Default = nodebug; abbreviation =
+ (Default = nodebug; abbreviation =
[no]deb)
-.RE
-.PP
+ .RE
+ .PP
\fB\fI[no]\fR\fR\fBd2\fR
.RS 4
-Turn debugging mode on or off\&. This displays more about what nslookup is doing\&.
+ Turn debugging mode on or off\&. This displays more about what nslookup is doing\&.
.sp
-(Default = nod2)
-.RE
-.PP
+ (Default = nod2)
+ .RE
+ .PP
\fBdomain=\fR\fIname\fR
.RS 4
-Sets the search list to
+ Sets the search list to
\fIname\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\fB\fI[no]\fR\fR\fBsearch\fR
.RS 4
-If the lookup request contains at least one period but doesn\*(Aqt end with a trailing period, append the domain names in the domain search list to the request until an answer is received\&.
+ If the lookup request contains at least one period but doesn\*(Aqt end with a trailing period, append the domain names in the domain search list to the request until an answer is received\&.
.sp
-(Default = search)
-.RE
-.PP
+ (Default = search)
+ .RE
+ .PP
\fBport=\fR\fIvalue\fR
.RS 4
-Change the default TCP/UDP name server port to
+ Change the default TCP/UDP name server port to
\fIvalue\fR\&.
.sp
-(Default = 53; abbreviation = po)
-.RE
-.PP
+ (Default = 53; abbreviation = po)
+ .RE
+ .PP
\fBquerytype=\fR\fIvalue\fR
.RS 4
-.RE
-.PP
+ .RE
+ .PP
\fBtype=\fR\fIvalue\fR
.RS 4
-Change the type of the information query\&.
+ Change the type of the information query\&.
.sp
-(Default = A and then AAAA; abbreviations = q, ty)
+ (Default = A and then AAAA; abbreviations = q, ty)
.sp
-\fBNote:\fR
+ \fBNote:\fR
It is only possible to specify one query type, only the default behavior looks up both when an alternative is not specified\&.
-.RE
-.PP
+ .RE
+ .PP
\fB\fI[no]\fR\fR\fBrecurse\fR
.RS 4
-Tell the name server to query other servers if it does not have the information\&.
+ Tell the name server to query other servers if it does not have the information\&.
.sp
-(Default = recurse; abbreviation = [no]rec)
-.RE
-.PP
+ (Default = recurse; abbreviation = [no]rec)
+ .RE
+ .PP
\fBndots=\fR\fInumber\fR
.RS 4
-Set the number of dots (label separators) in a domain that will disable searching\&. Absolute names always stop searching\&.
-.RE
-.PP
+ Set the number of dots (label separators) in a domain that will disable searching\&. Absolute names always stop searching\&.
+ .RE
+ .PP
\fBretry=\fR\fInumber\fR
.RS 4
-Set the number of retries to number\&.
-.RE
-.PP
+ Set the number of retries to number\&.
+ .RE
+ .PP
\fBtimeout=\fR\fInumber\fR
.RS 4
-Change the initial timeout interval for waiting for a reply to number seconds\&.
-.RE
-.PP
+ Change the initial timeout interval for waiting for a reply to number seconds\&.
+ .RE
+ .PP
\fB\fI[no]\fR\fR\fBvc\fR
.RS 4
-Always use a virtual circuit when sending requests to the server\&.
+ Always use a virtual circuit when sending requests to the server\&.
.sp
-(Default = novc)
-.RE
-.PP
+ (Default = novc)
+ .RE
+ .PP
\fB\fI[no]\fR\fR\fBfail\fR
.RS 4
-Try the next nameserver if a nameserver responds with SERVFAIL or a referral (nofail) or terminate query (fail) on such a response\&.
+ Try the next nameserver if a nameserver responds with SERVFAIL or a referral (nofail) or terminate query (fail) on such a response\&.
.sp
-(Default = nofail)
-.RE
-.sp
-.RE
-.SH "RETURN VALUES"
-.PP
+ (Default = nofail)
+ .RE
+ .sp
+ .RE
+ .SH "RETURN VALUES"
+ .PP
\fBnslookup\fR
returns with an exit status of 1 if any query failed, and 0 otherwise\&.
-.SH "IDN SUPPORT"
-.PP
+ .SH "IDN SUPPORT"
+ .PP
If
\fBnslookup\fR
has been built with IDN (internationalized domain name) support, it can accept and display non\-ASCII domain names\&.
environment variable\&. The IDN support is disabled if the variable is set when
\fBnslookup\fR
runs or when the standard output is not a tty\&.
-.SH "FILES"
-.PP
+ .SH "FILES"
+ .PP
/etc/resolv\&.conf
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBdig\fR(1),
\fBhost\fR(1),
\fBnamed\fR(8)\&.
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>nslookup</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.nslookup"></a><div class="titlepage"></div>
'\" t
.\" Title: dnssec-dsfromkey
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2012-05-02
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
dnssec-dsfromkey \- DNSSEC DS RR generation tool
-.SH "SYNOPSIS"
-.HP \w'\fBdnssec\-dsfromkey\fR\ 'u
-\fBdnssec\-dsfromkey\fR [\fB\-1\fR | \fB\-2\fR | \fB\-a\ \fR\fB\fIalg\fR\fR] [\fB\-C\fR | \fB\-l\ \fR\fB\fIdomain\fR\fR] [\fB\-T\ \fR\fB\fITTL\fR\fR] [\fB\-v\ \fR\fB\fIlevel\fR\fR] [\fB\-K\ \fR\fB\fIdirectory\fR\fR] {keyfile}
-.HP \w'\fBdnssec\-dsfromkey\fR\ 'u
-\fBdnssec\-dsfromkey\fR [\fB\-1\fR | \fB\-2\fR | \fB\-a\ \fR\fB\fIalg\fR\fR] [\fB\-C\fR | \fB\-l\ \fR\fB\fIdomain\fR\fR] [\fB\-T\ \fR\fB\fITTL\fR\fR] [\fB\-v\ \fR\fB\fIlevel\fR\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-A\fR] {\fB\-f\ \fR\fB\fIfile\fR\fR} [dnsname]
-.HP \w'\fBdnssec\-dsfromkey\fR\ 'u
-\fBdnssec\-dsfromkey\fR [\fB\-1\fR | \fB\-2\fR | \fB\-a\ \fR\fB\fIalg\fR\fR] [\fB\-C\fR | \fB\-l\ \fR\fB\fIdomain\fR\fR] [\fB\-T\ \fR\fB\fITTL\fR\fR] [\fB\-v\ \fR\fB\fIlevel\fR\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-K\ \fR\fB\fIdirectory\fR\fR] {\-s} {dnsname}
-.HP \w'\fBdnssec\-dsfromkey\fR\ 'u
-\fBdnssec\-dsfromkey\fR [\fB\-h\fR | \fB\-V\fR]
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBdnssec\-dsfromkey\fR\ 'u
+ \fBdnssec\-dsfromkey\fR
+ [
+ | \fB\-1\fR
+ | \fB\-2\fR
+ | \fB\-a\ \fR\fB\fIalg\fR\fR
+ ]
+ [
+ | \fB\-C\fR
+ | \fB\-l\ \fR\fB\fIdomain\fR\fR
+ ]
+ [\fB\-T\ \fR\fB\fITTL\fR\fR]
+ [\fB\-v\ \fR\fB\fIlevel\fR\fR]
+ [\fB\-K\ \fR\fB\fIdirectory\fR\fR]
+ {keyfile}
+ .HP \w'\fBdnssec\-dsfromkey\fR\ 'u
+ \fBdnssec\-dsfromkey\fR
+ [
+ | \fB\-1\fR
+ | \fB\-2\fR
+ | \fB\-a\ \fR\fB\fIalg\fR\fR
+ ]
+ [
+ | \fB\-C\fR
+ | \fB\-l\ \fR\fB\fIdomain\fR\fR
+ ]
+ [\fB\-T\ \fR\fB\fITTL\fR\fR]
+ [\fB\-v\ \fR\fB\fIlevel\fR\fR]
+ [\fB\-c\ \fR\fB\fIclass\fR\fR]
+ [\fB\-A\fR]
+ {\fB\-f\ \fR\fB\fIfile\fR\fR}
+ [dnsname]
+ .HP \w'\fBdnssec\-dsfromkey\fR\ 'u
+ \fBdnssec\-dsfromkey\fR
+ [
+ | \fB\-1\fR
+ | \fB\-2\fR
+ | \fB\-a\ \fR\fB\fIalg\fR\fR
+ ]
+ [
+ | \fB\-C\fR
+ | \fB\-l\ \fR\fB\fIdomain\fR\fR
+ ]
+ [\fB\-T\ \fR\fB\fITTL\fR\fR]
+ [\fB\-v\ \fR\fB\fIlevel\fR\fR]
+ [\fB\-c\ \fR\fB\fIclass\fR\fR]
+ [\fB\-K\ \fR\fB\fIdirectory\fR\fR]
+ {\-s}
+ {dnsname}
+ .HP \w'\fBdnssec\-dsfromkey\fR\ 'u
+ \fBdnssec\-dsfromkey\fR
+ [
+ | \fB\-h\fR
+ | \fB\-V\fR
+ ]
+ .SH "DESCRIPTION"
+ .PP
The
\fBdnssec\-dsfromkey\fR
command outputs DS (Delegation Signer) resource records (RRs) and other similarly\-constructed RRs: with the
option it outputs DLV (DNSSEC Lookaside Validation) RRs; or with the
\fB\-C\fR
it outputs CDS (Child DS) RRs\&.
-.PP
+ .PP
The input keys can be specified in a number of ways:
-.PP
+ .PP
By default,
\fBdnssec\-dsfromkey\fR
reads a key file named like
Knnnn\&.+aaa+iiiii\&.key, as generated by
\fBdnssec\-keygen\fR\&.
-.PP
+ .PP
With the
\fB\-f \fR\fB\fIfile\fR\fR
option,
\fBdnssec\-dsfromkey\fR
reads keys from a zone file or partial zone file (which can contain just the DNSKEY records)\&.
-.PP
+ .PP
With the
\fB\-s\fR
option,
reads a
keyset\-
file, as generated by
-\fBdnssec\-keygen\fR\fB\-C\fR\&.
-.SH "OPTIONS"
-.PP
+\fBdnssec\-keygen\fR
+\fB\-C\fR\&.
+ .SH "OPTIONS"
+ .PP
\-1
.RS 4
-An abbreviation for
+ An abbreviation for
\fB\-a SHA1\fR
-.RE
-.PP
+ .RE
+ .PP
\-2
.RS 4
-An abbreviation for
+ An abbreviation for
\fB\-a SHA\-256\fR
-.RE
-.PP
+ .RE
+ .PP
\-a \fIalgorithm\fR
.RS 4
-Specify a digest algorithm to use when converting DNSKEY records to DS records\&. This option can be repeated, so that multiple DS records are created for each DNSKEY record\&.
+ Specify a digest algorithm to use when converting DNSKEY records to DS records\&. This option can be repeated, so that multiple DS records are created for each DNSKEY record\&.
.sp
-The
+ The
\fIalgorithm\fR
must be one of SHA\-1, SHA\-256, or SHA\-384\&. These values are case insensitive, and the hyphen may be omitted\&. If no algorithm is specified, the default is to use both SHA\-1 and SHA\-256\&.
-.RE
-.PP
+ .RE
+ .PP
\-A
.RS 4
-Include ZSKs when generating DS records\&. Without this option, only keys which have the KSK flag set will be converted to DS records and printed\&. Useful only in
+ Include ZSKs when generating DS records\&. Without this option, only keys which have the KSK flag set will be converted to DS records and printed\&. Useful only in
\fB\-f\fR
zone file mode\&.
-.RE
-.PP
+ .RE
+ .PP
\-c \fIclass\fR
.RS 4
-Specifies the DNS class (default is IN)\&. Useful only in
+ Specifies the DNS class (default is IN)\&. Useful only in
\fB\-s\fR
keyset or
\fB\-f\fR
zone file mode\&.
-.RE
-.PP
+ .RE
+ .PP
\-C
.RS 4
-Generate CDS records rather than DS records\&. This is mutually exclusive with the
+ Generate CDS records rather than DS records\&. This is mutually exclusive with the
\fB\-l\fR
option for generating DLV records\&.
-.RE
-.PP
+ .RE
+ .PP
\-f \fIfile\fR
.RS 4
-Zone file mode:
+ Zone file mode:
\fBdnssec\-dsfromkey\fR\*(Aqs final
\fIdnsname\fR
argument is the DNS domain name of a zone whose master file can be read from
\fBfile\fR\&. If the zone name is the same as
\fBfile\fR, then it may be omitted\&.
.sp
-If
+ If
\fIfile\fR
is
"\-", then the zone data is read from the standard input\&. This makes it possible to use the output of the
\fBdig\fR
command as input, as in:
.sp
-\fBdig dnskey example\&.com | dnssec\-dsfromkey \-f \- example\&.com\fR
-.RE
-.PP
+ \fBdig dnskey example\&.com | dnssec\-dsfromkey \-f \- example\&.com\fR
+ .RE
+ .PP
\-h
.RS 4
-Prints usage information\&.
-.RE
-.PP
+ Prints usage information\&.
+ .RE
+ .PP
\-K \fIdirectory\fR
.RS 4
-Look for key files or
+ Look for key files or
keyset\-
files in
\fBdirectory\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-l \fIdomain\fR
.RS 4
-Generate a DLV set instead of a DS set\&. The specified
+ Generate a DLV set instead of a DS set\&. The specified
\fIdomain\fR
is appended to the name for each record in the set\&. This is mutually exclusive with the
\fB\-C\fR
option for generating CDS records\&.
-.RE
-.PP
+ .RE
+ .PP
\-s
.RS 4
-Keyset mode:
+ Keyset mode:
\fBdnssec\-dsfromkey\fR\*(Aqs final
\fIdnsname\fR
argument is the DNS domain name used to locate a
keyset\-
file\&.
-.RE
-.PP
+ .RE
+ .PP
\-T \fITTL\fR
.RS 4
-Specifies the TTL of the DS records\&. By default the TTL is omitted\&.
-.RE
-.PP
+ Specifies the TTL of the DS records\&. By default the TTL is omitted\&.
+ .RE
+ .PP
\-v \fIlevel\fR
.RS 4
-Sets the debugging level\&.
-.RE
-.PP
+ Sets the debugging level\&.
+ .RE
+ .PP
\-V
.RS 4
-Prints version information\&.
-.RE
-.SH "EXAMPLE"
-.PP
+ Prints version information\&.
+ .RE
+ .SH "EXAMPLE"
+ .PP
To build the SHA\-256 DS RR from the
\fBKexample\&.com\&.+003+26160\fR
keyfile name, you can issue the following command:
-.PP
+ .PP
\fBdnssec\-dsfromkey \-2 Kexample\&.com\&.+003+26160\fR
-.PP
+ .PP
The command would print something like:
-.PP
+ .PP
\fBexample\&.com\&. IN DS 26160 5 2 3A1EADA7A74B8D0BA86726B0C227AA85AB8BBD2B2004F41A868A54F0C5EA0B94\fR
-.SH "FILES"
-.PP
+ .SH "FILES"
+ .PP
The keyfile can be designated by the key identification
Knnnn\&.+aaa+iiiii
or the full file name
Knnnn\&.+aaa+iiiii\&.key
as generated by
dnssec\-keygen(8)\&.
-.PP
+ .PP
The keyset file name is built from the
\fBdirectory\fR, the string
keyset\-
and the
\fBdnsname\fR\&.
-.SH "CAVEAT"
-.PP
+ .SH "CAVEAT"
+ .PP
A keyfile error can give a "file not found" even if the file exists\&.
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBdnssec-keygen\fR(8),
\fBdnssec-signzone\fR(8),
BIND 9 Administrator Reference Manual,
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-dsfromkey</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.dnssec-dsfromkey"></a><div class="titlepage"></div>
'\" t
.\" Title: dnssec-importkey
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: August 21, 2015
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
dnssec-importkey \- import DNSKEY records from external systems so they can be managed
-.SH "SYNOPSIS"
-.HP \w'\fBdnssec\-importkey\fR\ 'u
-\fBdnssec\-importkey\fR [\fB\-K\ \fR\fB\fIdirectory\fR\fR] [\fB\-L\ \fR\fB\fIttl\fR\fR] [\fB\-P\ \fR\fB\fIdate/offset\fR\fR] [\fB\-P\ sync\ \fR\fB\fIdate/offset\fR\fR] [\fB\-D\ \fR\fB\fIdate/offset\fR\fR] [\fB\-D\ sync\ \fR\fB\fIdate/offset\fR\fR] [\fB\-h\fR] [\fB\-v\ \fR\fB\fIlevel\fR\fR] [\fB\-V\fR] {\fBkeyfile\fR}
-.HP \w'\fBdnssec\-importkey\fR\ 'u
-\fBdnssec\-importkey\fR {\fB\-f\ \fR\fB\fIfilename\fR\fR} [\fB\-K\ \fR\fB\fIdirectory\fR\fR] [\fB\-L\ \fR\fB\fIttl\fR\fR] [\fB\-P\ \fR\fB\fIdate/offset\fR\fR] [\fB\-P\ sync\ \fR\fB\fIdate/offset\fR\fR] [\fB\-D\ \fR\fB\fIdate/offset\fR\fR] [\fB\-D\ sync\ \fR\fB\fIdate/offset\fR\fR] [\fB\-h\fR] [\fB\-v\ \fR\fB\fIlevel\fR\fR] [\fB\-V\fR] [\fBdnsname\fR]
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBdnssec\-importkey\fR\ 'u
+ \fBdnssec\-importkey\fR
+ [\fB\-K\ \fR\fB\fIdirectory\fR\fR]
+ [\fB\-L\ \fR\fB\fIttl\fR\fR]
+ [\fB\-P\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-P\ sync\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-D\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-D\ sync\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-h\fR]
+ [\fB\-v\ \fR\fB\fIlevel\fR\fR]
+ [\fB\-V\fR]
+ {\fBkeyfile\fR}
+ .HP \w'\fBdnssec\-importkey\fR\ 'u
+ \fBdnssec\-importkey\fR
+ {\fB\-f\ \fR\fB\fIfilename\fR\fR}
+ [\fB\-K\ \fR\fB\fIdirectory\fR\fR]
+ [\fB\-L\ \fR\fB\fIttl\fR\fR]
+ [\fB\-P\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-P\ sync\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-D\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-D\ sync\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-h\fR]
+ [\fB\-v\ \fR\fB\fIlevel\fR\fR]
+ [\fB\-V\fR]
+ [\fBdnsname\fR]
+ .SH "DESCRIPTION"
+ .PP
\fBdnssec\-importkey\fR
reads a public DNSKEY record and generates a pair of \&.key/\&.private files\&. The DNSKEY record may be read from an existing \&.key file, in which case a corresponding \&.private file will be generated, or it may be read from any other file or from the standard input, in which case both \&.key and \&.private files will be generated\&.
-.PP
+ .PP
The newly\-created \&.private file does
\fInot\fR
contain private key data, and cannot be used for signing\&. However, having a \&.private file makes it possible to set publication (\fB\-P\fR) and deletion (\fB\-D\fR) times for the key, which means the public key can be added to and removed from the DNSKEY RRset on schedule even if the true private key is stored offline\&.
-.SH "OPTIONS"
-.PP
+ .SH "OPTIONS"
+ .PP
\-f \fIfilename\fR
.RS 4
-Zone file mode: instead of a public keyfile name, the argument is the DNS domain name of a zone master file, which can be read from
+ Zone file mode: instead of a public keyfile name, the argument is the DNS domain name of a zone master file, which can be read from
\fBfile\fR\&. If the domain name is the same as
\fBfile\fR, then it may be omitted\&.
.sp
-If
+ If
\fBfile\fR
is set to
"\-", then the zone data is read from the standard input\&.
-.RE
-.PP
+ .RE
+ .PP
\-K \fIdirectory\fR
.RS 4
-Sets the directory in which the key files are to reside\&.
-.RE
-.PP
+ Sets the directory in which the key files are to reside\&.
+ .RE
+ .PP
\-L \fIttl\fR
.RS 4
-Sets the default TTL to use for this key when it is converted into a DNSKEY RR\&. If the key is imported into a zone, this is the TTL that will be used for it, unless there was already a DNSKEY RRset in place, in which case the existing TTL would take precedence\&. Setting the default TTL to
+ Sets the default TTL to use for this key when it is converted into a DNSKEY RR\&. If the key is imported into a zone, this is the TTL that will be used for it, unless there was already a DNSKEY RRset in place, in which case the existing TTL would take precedence\&. Setting the default TTL to
0
or
none
removes it\&.
-.RE
-.PP
+ .RE
+ .PP
\-h
.RS 4
-Emit usage message and exit\&.
-.RE
-.PP
+ Emit usage message and exit\&.
+ .RE
+ .PP
\-v \fIlevel\fR
.RS 4
-Sets the debugging level\&.
-.RE
-.PP
+ Sets the debugging level\&.
+ .RE
+ .PP
\-V
.RS 4
-Prints version information\&.
-.RE
-.SH "TIMING OPTIONS"
-.PP
+ Prints version information\&.
+ .RE
+ .SH "TIMING OPTIONS"
+ .PP
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS\&. If the argument begins with a \*(Aq+\*(Aq or \*(Aq\-\*(Aq, it is interpreted as an offset from the present time\&. For convenience, if such an offset is followed by one of the suffixes \*(Aqy\*(Aq, \*(Aqmo\*(Aq, \*(Aqw\*(Aq, \*(Aqd\*(Aq, \*(Aqh\*(Aq, or \*(Aqmi\*(Aq, then the offset is computed in years (defined as 365 24\-hour days, ignoring leap years), months (defined as 30 24\-hour days), weeks, days, hours, or minutes, respectively\&. Without a suffix, the offset is computed in seconds\&. To explicitly prevent a date from being set, use \*(Aqnone\*(Aq or \*(Aqnever\*(Aq\&.
-.PP
+ .PP
\-P \fIdate/offset\fR
.RS 4
-Sets the date on which a key is to be published to the zone\&. After that date, the key will be included in the zone but will not be used to sign it\&.
-.RE
-.PP
+ Sets the date on which a key is to be published to the zone\&. After that date, the key will be included in the zone but will not be used to sign it\&.
+ .RE
+ .PP
\-P sync \fIdate/offset\fR
.RS 4
-Sets the date on which CDS and CDNSKEY records that match this key are to be published to the zone\&.
-.RE
-.PP
+ Sets the date on which CDS and CDNSKEY records that match this key are to be published to the zone\&.
+ .RE
+ .PP
\-D \fIdate/offset\fR
.RS 4
-Sets the date on which the key is to be deleted\&. After that date, the key will no longer be included in the zone\&. (It may remain in the key repository, however\&.)
-.RE
-.PP
+ Sets the date on which the key is to be deleted\&. After that date, the key will no longer be included in the zone\&. (It may remain in the key repository, however\&.)
+ .RE
+ .PP
\-D sync \fIdate/offset\fR
.RS 4
-Sets the date on which the CDS and CDNSKEY records that match this key are to be deleted\&.
-.RE
-.SH "FILES"
-.PP
+ Sets the date on which the CDS and CDNSKEY records that match this key are to be deleted\&.
+ .RE
+ .SH "FILES"
+ .PP
A keyfile can be designed by the key identification
Knnnn\&.+aaa+iiiii
or the full file name
Knnnn\&.+aaa+iiiii\&.key
as generated by
dnssec\-keygen(8)\&.
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBdnssec-keygen\fR(8),
\fBdnssec-signzone\fR(8),
BIND 9 Administrator Reference Manual,
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-importkey</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.dnssec-importkey"></a><div class="titlepage"></div>
'\" t
.\" Title: dnssec-keyfromlabel
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: August 27, 2015
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
dnssec-keyfromlabel \- DNSSEC key generation tool
-.SH "SYNOPSIS"
-.HP \w'\fBdnssec\-keyfromlabel\fR\ 'u
-\fBdnssec\-keyfromlabel\fR {\-l\ \fIlabel\fR} [\fB\-3\fR] [\fB\-a\ \fR\fB\fIalgorithm\fR\fR] [\fB\-A\ \fR\fB\fIdate/offset\fR\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-D\ \fR\fB\fIdate/offset\fR\fR] [\fB\-D\ sync\ \fR\fB\fIdate/offset\fR\fR] [\fB\-E\ \fR\fB\fIengine\fR\fR] [\fB\-f\ \fR\fB\fIflag\fR\fR] [\fB\-G\fR] [\fB\-I\ \fR\fB\fIdate/offset\fR\fR] [\fB\-i\ \fR\fB\fIinterval\fR\fR] [\fB\-k\fR] [\fB\-K\ \fR\fB\fIdirectory\fR\fR] [\fB\-L\ \fR\fB\fIttl\fR\fR] [\fB\-n\ \fR\fB\fInametype\fR\fR] [\fB\-P\ \fR\fB\fIdate/offset\fR\fR] [\fB\-P\ sync\ \fR\fB\fIdate/offset\fR\fR] [\fB\-p\ \fR\fB\fIprotocol\fR\fR] [\fB\-R\ \fR\fB\fIdate/offset\fR\fR] [\fB\-S\ \fR\fB\fIkey\fR\fR] [\fB\-t\ \fR\fB\fItype\fR\fR] [\fB\-v\ \fR\fB\fIlevel\fR\fR] [\fB\-V\fR] [\fB\-y\fR] {name}
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBdnssec\-keyfromlabel\fR\ 'u
+ \fBdnssec\-keyfromlabel\fR
+ {\-l\ \fIlabel\fR}
+ [\fB\-3\fR]
+ [\fB\-a\ \fR\fB\fIalgorithm\fR\fR]
+ [\fB\-A\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-c\ \fR\fB\fIclass\fR\fR]
+ [\fB\-D\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-D\ sync\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-E\ \fR\fB\fIengine\fR\fR]
+ [\fB\-f\ \fR\fB\fIflag\fR\fR]
+ [\fB\-G\fR]
+ [\fB\-I\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-i\ \fR\fB\fIinterval\fR\fR]
+ [\fB\-k\fR]
+ [\fB\-K\ \fR\fB\fIdirectory\fR\fR]
+ [\fB\-L\ \fR\fB\fIttl\fR\fR]
+ [\fB\-n\ \fR\fB\fInametype\fR\fR]
+ [\fB\-P\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-P\ sync\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-p\ \fR\fB\fIprotocol\fR\fR]
+ [\fB\-R\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-S\ \fR\fB\fIkey\fR\fR]
+ [\fB\-t\ \fR\fB\fItype\fR\fR]
+ [\fB\-v\ \fR\fB\fIlevel\fR\fR]
+ [\fB\-V\fR]
+ [\fB\-y\fR]
+ {name}
+ .SH "DESCRIPTION"
+ .PP
\fBdnssec\-keyfromlabel\fR
generates a key pair of files that referencing a key object stored in a cryptographic hardware service module (HSM)\&. The private key file can be used for DNSSEC signing of zone data as if it were a conventional signing key created by
\fBdnssec\-keygen\fR, but the key material is stored within the HSM, and the actual signing takes place there\&.
-.PP
+ .PP
The
\fBname\fR
of the key is specified on the command line\&. This must match the name of the zone for which the key is being generated\&.
-.SH "OPTIONS"
-.PP
+ .SH "OPTIONS"
+ .PP
\-a \fIalgorithm\fR
.RS 4
-Selects the cryptographic algorithm\&. The value of
+ Selects the cryptographic algorithm\&. The value of
\fBalgorithm\fR
must be one of RSAMD5, RSASHA1, DSA, NSEC3RSASHA1, NSEC3DSA, RSASHA256, RSASHA512, ECCGOST, ECDSAP256SHA256, ECDSAP384SHA384, ED25519 or ED448\&. These values are case insensitive\&.
.sp
-If no algorithm is specified, then RSASHA1 will be used by default, unless the
+ If no algorithm is specified, then RSASHA1 will be used by default, unless the
\fB\-3\fR
option is specified, in which case NSEC3RSASHA1 will be used instead\&. (If
\fB\-3\fR
is used and an algorithm is specified, that algorithm will be checked for compatibility with NSEC3\&.)
.sp
-Note 1: that for DNSSEC, RSASHA1 is a mandatory to implement algorithm, and DSA is recommended\&.
+ Note 1: that for DNSSEC, RSASHA1 is a mandatory to implement algorithm, and DSA is recommended\&.
.sp
-Note 2: DH automatically sets the \-k flag\&.
-.RE
-.PP
+ Note 2: DH automatically sets the \-k flag\&.
+ .RE
+ .PP
\-3
.RS 4
-Use an NSEC3\-capable algorithm to generate a DNSSEC key\&. If this option is used and no algorithm is explicitly set on the command line, NSEC3RSASHA1 will be used by default\&.
-.RE
-.PP
+ Use an NSEC3\-capable algorithm to generate a DNSSEC key\&. If this option is used and no algorithm is explicitly set on the command line, NSEC3RSASHA1 will be used by default\&.
+ .RE
+ .PP
\-E \fIengine\fR
.RS 4
-Specifies the cryptographic hardware to use\&.
+ Specifies the cryptographic hardware to use\&.
.sp
-When BIND is built with OpenSSL PKCS#11 support, this defaults to the string "pkcs11", which identifies an OpenSSL engine that can drive a cryptographic accelerator or hardware service module\&. When BIND is built with native PKCS#11 cryptography (\-\-enable\-native\-pkcs11), it defaults to the path of the PKCS#11 provider library specified via "\-\-with\-pkcs11"\&.
-.RE
-.PP
+ When BIND is built with OpenSSL PKCS#11 support, this defaults to the string "pkcs11", which identifies an OpenSSL engine that can drive a cryptographic accelerator or hardware service module\&. When BIND is built with native PKCS#11 cryptography (\-\-enable\-native\-pkcs11), it defaults to the path of the PKCS#11 provider library specified via "\-\-with\-pkcs11"\&.
+ .RE
+ .PP
\-l \fIlabel\fR
.RS 4
-Specifies the label for a key pair in the crypto hardware\&.
+ Specifies the label for a key pair in the crypto hardware\&.
.sp
-When
+ When
BIND
9 is built with OpenSSL\-based PKCS#11 support, the label is an arbitrary string that identifies a particular key\&.
.sp
-When
+ When
BIND
9 is built with native PKCS#11 support, the label is a PKCS#11 URI string in the format "pkcs11:\fBkeyword\fR=\fIvalue\fR[;\fBkeyword\fR=\fIvalue\fR;\&.\&.\&.]" Keywords include "token", which identifies the HSM; "object", which identifies the key; and "pin\-source", which identifies a file from which the HSM\*(Aqs PIN code can be obtained\&. The label will be stored in the on\-disk "private" file\&.
.sp
-If the label contains a
+ If the label contains a
\fBpin\-source\fR
field, tools using the generated key files will be able to use the HSM for signing and other operations without any need for an operator to manually enter a PIN\&. Note: Making the HSM\*(Aqs PIN accessible in this manner may reduce the security advantage of using an HSM; be sure this is what you want to do before making use of this feature\&.
-.RE
-.PP
+ .RE
+ .PP
\-n \fInametype\fR
.RS 4
-Specifies the owner type of the key\&. The value of
+ Specifies the owner type of the key\&. The value of
\fBnametype\fR
must either be ZONE (for a DNSSEC zone key (KEY/DNSKEY)), HOST or ENTITY (for a key associated with a host (KEY)), USER (for a key associated with a user(KEY)) or OTHER (DNSKEY)\&. These values are case insensitive\&.
-.RE
-.PP
+ .RE
+ .PP
\-C
.RS 4
-Compatibility mode: generates an old\-style key, without any metadata\&. By default,
+ Compatibility mode: generates an old\-style key, without any metadata\&. By default,
\fBdnssec\-keyfromlabel\fR
will include the key\*(Aqs creation date in the metadata stored with the private key, and other dates may be set there as well (publication date, activation date, etc)\&. Keys that include this data may be incompatible with older versions of BIND; the
\fB\-C\fR
option suppresses them\&.
-.RE
-.PP
+ .RE
+ .PP
\-c \fIclass\fR
.RS 4
-Indicates that the DNS record containing the key should have the specified class\&. If not specified, class IN is used\&.
-.RE
-.PP
+ Indicates that the DNS record containing the key should have the specified class\&. If not specified, class IN is used\&.
+ .RE
+ .PP
\-f \fIflag\fR
.RS 4
-Set the specified flag in the flag field of the KEY/DNSKEY record\&. The only recognized flags are KSK (Key Signing Key) and REVOKE\&.
-.RE
-.PP
+ Set the specified flag in the flag field of the KEY/DNSKEY record\&. The only recognized flags are KSK (Key Signing Key) and REVOKE\&.
+ .RE
+ .PP
\-G
.RS 4
-Generate a key, but do not publish it or sign with it\&. This option is incompatible with \-P and \-A\&.
-.RE
-.PP
+ Generate a key, but do not publish it or sign with it\&. This option is incompatible with \-P and \-A\&.
+ .RE
+ .PP
\-h
.RS 4
-Prints a short summary of the options and arguments to
+ Prints a short summary of the options and arguments to
\fBdnssec\-keyfromlabel\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-K \fIdirectory\fR
.RS 4
-Sets the directory in which the key files are to be written\&.
-.RE
-.PP
+ Sets the directory in which the key files are to be written\&.
+ .RE
+ .PP
\-k
.RS 4
-Generate KEY records rather than DNSKEY records\&.
-.RE
-.PP
+ Generate KEY records rather than DNSKEY records\&.
+ .RE
+ .PP
\-L \fIttl\fR
.RS 4
-Sets the default TTL to use for this key when it is converted into a DNSKEY RR\&. If the key is imported into a zone, this is the TTL that will be used for it, unless there was already a DNSKEY RRset in place, in which case the existing TTL would take precedence\&. Setting the default TTL to
+ Sets the default TTL to use for this key when it is converted into a DNSKEY RR\&. If the key is imported into a zone, this is the TTL that will be used for it, unless there was already a DNSKEY RRset in place, in which case the existing TTL would take precedence\&. Setting the default TTL to
0
or
none
removes it\&.
-.RE
-.PP
+ .RE
+ .PP
\-p \fIprotocol\fR
.RS 4
-Sets the protocol value for the key\&. The protocol is a number between 0 and 255\&. The default is 3 (DNSSEC)\&. Other possible values for this argument are listed in RFC 2535 and its successors\&.
-.RE
-.PP
+ Sets the protocol value for the key\&. The protocol is a number between 0 and 255\&. The default is 3 (DNSSEC)\&. Other possible values for this argument are listed in RFC 2535 and its successors\&.
+ .RE
+ .PP
\-S \fIkey\fR
.RS 4
-Generate a key as an explicit successor to an existing key\&. The name, algorithm, size, and type of the key will be set to match the predecessor\&. The activation date of the new key will be set to the inactivation date of the existing one\&. The publication date will be set to the activation date minus the prepublication interval, which defaults to 30 days\&.
-.RE
-.PP
+ Generate a key as an explicit successor to an existing key\&. The name, algorithm, size, and type of the key will be set to match the predecessor\&. The activation date of the new key will be set to the inactivation date of the existing one\&. The publication date will be set to the activation date minus the prepublication interval, which defaults to 30 days\&.
+ .RE
+ .PP
\-t \fItype\fR
.RS 4
-Indicates the use of the key\&.
+ Indicates the use of the key\&.
\fBtype\fR
must be one of AUTHCONF, NOAUTHCONF, NOAUTH, or NOCONF\&. The default is AUTHCONF\&. AUTH refers to the ability to authenticate data, and CONF the ability to encrypt data\&.
-.RE
-.PP
+ .RE
+ .PP
\-v \fIlevel\fR
.RS 4
-Sets the debugging level\&.
-.RE
-.PP
+ Sets the debugging level\&.
+ .RE
+ .PP
\-V
.RS 4
-Prints version information\&.
-.RE
-.PP
+ Prints version information\&.
+ .RE
+ .PP
\-y
.RS 4
-Allows DNSSEC key files to be generated even if the key ID would collide with that of an existing key, in the event of either key being revoked\&. (This is only safe to use if you are sure you won\*(Aqt be using RFC 5011 trust anchor maintenance with either of the keys involved\&.)
-.RE
-.SH "TIMING OPTIONS"
-.PP
+ Allows DNSSEC key files to be generated even if the key ID would collide with that of an existing key, in the event of either key being revoked\&. (This is only safe to use if you are sure you won\*(Aqt be using RFC 5011 trust anchor maintenance with either of the keys involved\&.)
+ .RE
+ .SH "TIMING OPTIONS"
+ .PP
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS\&. If the argument begins with a \*(Aq+\*(Aq or \*(Aq\-\*(Aq, it is interpreted as an offset from the present time\&. For convenience, if such an offset is followed by one of the suffixes \*(Aqy\*(Aq, \*(Aqmo\*(Aq, \*(Aqw\*(Aq, \*(Aqd\*(Aq, \*(Aqh\*(Aq, or \*(Aqmi\*(Aq, then the offset is computed in years (defined as 365 24\-hour days, ignoring leap years), months (defined as 30 24\-hour days), weeks, days, hours, or minutes, respectively\&. Without a suffix, the offset is computed in seconds\&. To explicitly prevent a date from being set, use \*(Aqnone\*(Aq or \*(Aqnever\*(Aq\&.
-.PP
+ .PP
\-P \fIdate/offset\fR
.RS 4
-Sets the date on which a key is to be published to the zone\&. After that date, the key will be included in the zone but will not be used to sign it\&. If not set, and if the \-G option has not been used, the default is "now"\&.
-.RE
-.PP
+ Sets the date on which a key is to be published to the zone\&. After that date, the key will be included in the zone but will not be used to sign it\&. If not set, and if the \-G option has not been used, the default is "now"\&.
+ .RE
+ .PP
\-P sync \fIdate/offset\fR
.RS 4
-Sets the date on which the CDS and CDNSKEY records which match this key are to be published to the zone\&.
-.RE
-.PP
+ Sets the date on which the CDS and CDNSKEY records which match this key are to be published to the zone\&.
+ .RE
+ .PP
\-A \fIdate/offset\fR
.RS 4
-Sets the date on which the key is to be activated\&. After that date, the key will be included in the zone and used to sign it\&. If not set, and if the \-G option has not been used, the default is "now"\&.
-.RE
-.PP
+ Sets the date on which the key is to be activated\&. After that date, the key will be included in the zone and used to sign it\&. If not set, and if the \-G option has not been used, the default is "now"\&.
+ .RE
+ .PP
\-R \fIdate/offset\fR
.RS 4
-Sets the date on which the key is to be revoked\&. After that date, the key will be flagged as revoked\&. It will be included in the zone and will be used to sign it\&.
-.RE
-.PP
+ Sets the date on which the key is to be revoked\&. After that date, the key will be flagged as revoked\&. It will be included in the zone and will be used to sign it\&.
+ .RE
+ .PP
\-I \fIdate/offset\fR
.RS 4
-Sets the date on which the key is to be retired\&. After that date, the key will still be included in the zone, but it will not be used to sign it\&.
-.RE
-.PP
+ Sets the date on which the key is to be retired\&. After that date, the key will still be included in the zone, but it will not be used to sign it\&.
+ .RE
+ .PP
\-D \fIdate/offset\fR
.RS 4
-Sets the date on which the key is to be deleted\&. After that date, the key will no longer be included in the zone\&. (It may remain in the key repository, however\&.)
-.RE
-.PP
+ Sets the date on which the key is to be deleted\&. After that date, the key will no longer be included in the zone\&. (It may remain in the key repository, however\&.)
+ .RE
+ .PP
\-D sync \fIdate/offset\fR
.RS 4
-Sets the date on which the CDS and CDNSKEY records which match this key are to be deleted\&.
-.RE
-.PP
+ Sets the date on which the CDS and CDNSKEY records which match this key are to be deleted\&.
+ .RE
+ .PP
\-i \fIinterval\fR
.RS 4
-Sets the prepublication interval for a key\&. If set, then the publication and activation dates must be separated by at least this much time\&. If the activation date is specified but the publication date isn\*(Aqt, then the publication date will default to this much time before the activation date; conversely, if the publication date is specified but activation date isn\*(Aqt, then activation will be set to this much time after publication\&.
+ Sets the prepublication interval for a key\&. If set, then the publication and activation dates must be separated by at least this much time\&. If the activation date is specified but the publication date isn\*(Aqt, then the publication date will default to this much time before the activation date; conversely, if the publication date is specified but activation date isn\*(Aqt, then activation will be set to this much time after publication\&.
.sp
-If the key is being created as an explicit successor to another key, then the default prepublication interval is 30 days; otherwise it is zero\&.
+ If the key is being created as an explicit successor to another key, then the default prepublication interval is 30 days; otherwise it is zero\&.
.sp
-As with date offsets, if the argument is followed by one of the suffixes \*(Aqy\*(Aq, \*(Aqmo\*(Aq, \*(Aqw\*(Aq, \*(Aqd\*(Aq, \*(Aqh\*(Aq, or \*(Aqmi\*(Aq, then the interval is measured in years, months, weeks, days, hours, or minutes, respectively\&. Without a suffix, the interval is measured in seconds\&.
-.RE
-.SH "GENERATED KEY FILES"
-.PP
+ As with date offsets, if the argument is followed by one of the suffixes \*(Aqy\*(Aq, \*(Aqmo\*(Aq, \*(Aqw\*(Aq, \*(Aqd\*(Aq, \*(Aqh\*(Aq, or \*(Aqmi\*(Aq, then the interval is measured in years, months, weeks, days, hours, or minutes, respectively\&. Without a suffix, the interval is measured in seconds\&.
+ .RE
+ .SH "GENERATED KEY FILES"
+ .PP
When
\fBdnssec\-keyfromlabel\fR
completes successfully, it prints a string of the form
.sp -1
.IP \(bu 2.3
.\}
-nnnn
+ nnnn
is the key name\&.
-.RE
+ .RE
.sp
.RS 4
.ie n \{\
.sp -1
.IP \(bu 2.3
.\}
-aaa
+ aaa
is the numeric representation of the algorithm\&.
-.RE
+ .RE
.sp
.RS 4
.ie n \{\
.sp -1
.IP \(bu 2.3
.\}
-iiiii
+ iiiii
is the key identifier (or footprint)\&.
-.RE
-.PP
+ .RE
+ .PP
\fBdnssec\-keyfromlabel\fR
creates two files, with names based on the printed string\&.
Knnnn\&.+aaa+iiiii\&.key
contains the public key, and
Knnnn\&.+aaa+iiiii\&.private
contains the private key\&.
-.PP
+ .PP
The
\&.key
file contains a DNS KEY record that can be inserted into a zone file (directly or with a $INCLUDE statement)\&.
-.PP
+ .PP
The
\&.private
file contains algorithm\-specific fields\&. For obvious security reasons, this file does not have general read permission\&.
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBdnssec-keygen\fR(8),
\fBdnssec-signzone\fR(8),
BIND 9 Administrator Reference Manual,
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-keyfromlabel</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.dnssec-keyfromlabel"></a><div class="titlepage"></div>
'\" t
.\" Title: dnssec-keygen
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: August 21, 2015
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
dnssec-keygen \- DNSSEC key generation tool
-.SH "SYNOPSIS"
-.HP \w'\fBdnssec\-keygen\fR\ 'u
-\fBdnssec\-keygen\fR [\fB\-3\fR] [\fB\-A\ \fR\fB\fIdate/offset\fR\fR] [\fB\-a\ \fR\fB\fIalgorithm\fR\fR] [\fB\-b\ \fR\fB\fIkeysize\fR\fR] [\fB\-C\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-D\ \fR\fB\fIdate/offset\fR\fR] [\fB\-D\ sync\ \fR\fB\fIdate/offset\fR\fR] [\fB\-E\ \fR\fB\fIengine\fR\fR] [\fB\-f\ \fR\fB\fIflag\fR\fR] [\fB\-G\fR] [\fB\-g\ \fR\fB\fIgenerator\fR\fR] [\fB\-h\fR] [\fB\-I\ \fR\fB\fIdate/offset\fR\fR] [\fB\-i\ \fR\fB\fIinterval\fR\fR] [\fB\-K\ \fR\fB\fIdirectory\fR\fR] [\fB\-k\fR] [\fB\-L\ \fR\fB\fIttl\fR\fR] [\fB\-n\ \fR\fB\fInametype\fR\fR] [\fB\-P\ \fR\fB\fIdate/offset\fR\fR] [\fB\-P\ sync\ \fR\fB\fIdate/offset\fR\fR] [\fB\-p\ \fR\fB\fIprotocol\fR\fR] [\fB\-q\fR] [\fB\-R\ \fR\fB\fIdate/offset\fR\fR] [\fB\-r\ \fR\fB\fIrandomdev\fR\fR] [\fB\-S\ \fR\fB\fIkey\fR\fR] [\fB\-s\ \fR\fB\fIstrength\fR\fR] [\fB\-t\ \fR\fB\fItype\fR\fR] [\fB\-V\fR] [\fB\-v\ \fR\fB\fIlevel\fR\fR] {name}
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBdnssec\-keygen\fR\ 'u
+ \fBdnssec\-keygen\fR
+ [\fB\-3\fR]
+ [\fB\-A\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-a\ \fR\fB\fIalgorithm\fR\fR]
+ [\fB\-b\ \fR\fB\fIkeysize\fR\fR]
+ [\fB\-C\fR]
+ [\fB\-c\ \fR\fB\fIclass\fR\fR]
+ [\fB\-D\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-D\ sync\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-E\ \fR\fB\fIengine\fR\fR]
+ [\fB\-f\ \fR\fB\fIflag\fR\fR]
+ [\fB\-G\fR]
+ [\fB\-g\ \fR\fB\fIgenerator\fR\fR]
+ [\fB\-h\fR]
+ [\fB\-I\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-i\ \fR\fB\fIinterval\fR\fR]
+ [\fB\-K\ \fR\fB\fIdirectory\fR\fR]
+ [\fB\-k\fR]
+ [\fB\-L\ \fR\fB\fIttl\fR\fR]
+ [\fB\-n\ \fR\fB\fInametype\fR\fR]
+ [\fB\-P\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-P\ sync\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-p\ \fR\fB\fIprotocol\fR\fR]
+ [\fB\-q\fR]
+ [\fB\-R\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-r\ \fR\fB\fIrandomdev\fR\fR]
+ [\fB\-S\ \fR\fB\fIkey\fR\fR]
+ [\fB\-s\ \fR\fB\fIstrength\fR\fR]
+ [\fB\-t\ \fR\fB\fItype\fR\fR]
+ [\fB\-V\fR]
+ [\fB\-v\ \fR\fB\fIlevel\fR\fR]
+ {name}
+ .SH "DESCRIPTION"
+ .PP
\fBdnssec\-keygen\fR
generates keys for DNSSEC (Secure DNS), as defined in RFC 2535 and RFC 4034\&. It can also generate keys for use with TSIG (Transaction Signatures) as defined in RFC 2845, or TKEY (Transaction Key) as defined in RFC 2930\&.
-.PP
+ .PP
The
\fBname\fR
of the key is specified on the command line\&. For DNSSEC keys, this must match the name of the zone for which the key is being generated\&.
-.SH "OPTIONS"
-.PP
+ .SH "OPTIONS"
+ .PP
\-3
.RS 4
-Use an NSEC3\-capable algorithm to generate a DNSSEC key\&. If this option is used with an algorithm that has both NSEC and NSEC3 versions, then the NSEC3 version will be used; for example,
+ Use an NSEC3\-capable algorithm to generate a DNSSEC key\&. If this option is used with an algorithm that has both NSEC and NSEC3 versions, then the NSEC3 version will be used; for example,
\fBdnssec\-keygen \-3a RSASHA1\fR
specifies the NSEC3RSASHA1 algorithm\&.
-.RE
-.PP
+ .RE
+ .PP
\-a \fIalgorithm\fR
.RS 4
-Selects the cryptographic algorithm\&. For DNSSEC keys, the value of
+ Selects the cryptographic algorithm\&. For DNSSEC keys, the value of
\fBalgorithm\fR
must be one of RSAMD5, RSASHA1, DSA, NSEC3RSASHA1, NSEC3DSA, RSASHA256, RSASHA512, ECCGOST, ECDSAP256SHA256, ECDSAP384SHA384, ED25519 or ED448\&. For TSIG/TKEY, the value must be DH (Diffie Hellman), HMAC\-MD5, HMAC\-SHA1, HMAC\-SHA224, HMAC\-SHA256, HMAC\-SHA384, or HMAC\-SHA512\&. These values are case insensitive\&.
.sp
-If no algorithm is specified, then RSASHA1 will be used by default, unless the
+ If no algorithm is specified, then RSASHA1 will be used by default, unless the
\fB\-3\fR
option is specified, in which case NSEC3RSASHA1 will be used instead\&. (If
\fB\-3\fR
is used and an algorithm is specified, that algorithm will be checked for compatibility with NSEC3\&.)
.sp
-Note 1: that for DNSSEC, RSASHA1 is a mandatory to implement algorithm, and DSA is recommended\&. For TSIG, HMAC\-MD5 is mandatory\&.
+ Note 1: that for DNSSEC, RSASHA1 is a mandatory to implement algorithm, and DSA is recommended\&. For TSIG, HMAC\-MD5 is mandatory\&.
.sp
-Note 2: DH, HMAC\-MD5, and HMAC\-SHA1 through HMAC\-SHA512 automatically set the \-T KEY option\&.
-.RE
-.PP
+ Note 2: DH, HMAC\-MD5, and HMAC\-SHA1 through HMAC\-SHA512 automatically set the \-T KEY option\&.
+ .RE
+ .PP
\-b \fIkeysize\fR
.RS 4
-Specifies the number of bits in the key\&. The choice of key size depends on the algorithm used\&. RSA keys must be between 512 and 2048 bits\&. Diffie Hellman keys must be between 128 and 4096 bits\&. DSA keys must be between 512 and 1024 bits and an exact multiple of 64\&. HMAC keys must be between 1 and 512 bits\&. Elliptic curve algorithms don\*(Aqt need this parameter\&.
+ Specifies the number of bits in the key\&. The choice of key size depends on the algorithm used\&. RSA keys must be between 512 and 2048 bits\&. Diffie Hellman keys must be between 128 and 4096 bits\&. DSA keys must be between 512 and 1024 bits and an exact multiple of 64\&. HMAC keys must be between 1 and 512 bits\&. Elliptic curve algorithms don\*(Aqt need this parameter\&.
.sp
-The key size does not need to be specified if using a default algorithm\&. The default key size is 1024 bits for zone signing keys (ZSKs) and 2048 bits for key signing keys (KSKs, generated with
+ The key size does not need to be specified if using a default algorithm\&. The default key size is 1024 bits for zone signing keys (ZSKs) and 2048 bits for key signing keys (KSKs, generated with
\fB\-f KSK\fR)\&. However, if an algorithm is explicitly specified with the
\fB\-a\fR, then there is no default key size, and the
\fB\-b\fR
must be used\&.
-.RE
-.PP
+ .RE
+ .PP
\-C
.RS 4
-Compatibility mode: generates an old\-style key, without any timing metadata\&. By default,
+ Compatibility mode: generates an old\-style key, without any timing metadata\&. By default,
\fBdnssec\-keygen\fR
will include the key\*(Aqs creation date in the metadata stored with the private key, and other dates may be set there as well (publication date, activation date, etc)\&. Keys that include this data may be incompatible with older versions of BIND; the
\fB\-C\fR
option suppresses them\&.
-.RE
-.PP
+ .RE
+ .PP
\-c \fIclass\fR
.RS 4
-Indicates that the DNS record containing the key should have the specified class\&. If not specified, class IN is used\&.
-.RE
-.PP
+ Indicates that the DNS record containing the key should have the specified class\&. If not specified, class IN is used\&.
+ .RE
+ .PP
\-E \fIengine\fR
.RS 4
-Specifies the cryptographic hardware to use, when applicable\&.
+ Specifies the cryptographic hardware to use, when applicable\&.
.sp
-When BIND is built with OpenSSL PKCS#11 support, this defaults to the string "pkcs11", which identifies an OpenSSL engine that can drive a cryptographic accelerator or hardware service module\&. When BIND is built with native PKCS#11 cryptography (\-\-enable\-native\-pkcs11), it defaults to the path of the PKCS#11 provider library specified via "\-\-with\-pkcs11"\&.
-.RE
-.PP
+ When BIND is built with OpenSSL PKCS#11 support, this defaults to the string "pkcs11", which identifies an OpenSSL engine that can drive a cryptographic accelerator or hardware service module\&. When BIND is built with native PKCS#11 cryptography (\-\-enable\-native\-pkcs11), it defaults to the path of the PKCS#11 provider library specified via "\-\-with\-pkcs11"\&.
+ .RE
+ .PP
\-f \fIflag\fR
.RS 4
-Set the specified flag in the flag field of the KEY/DNSKEY record\&. The only recognized flags are KSK (Key Signing Key) and REVOKE\&.
-.RE
-.PP
+ Set the specified flag in the flag field of the KEY/DNSKEY record\&. The only recognized flags are KSK (Key Signing Key) and REVOKE\&.
+ .RE
+ .PP
\-G
.RS 4
-Generate a key, but do not publish it or sign with it\&. This option is incompatible with \-P and \-A\&.
-.RE
-.PP
+ Generate a key, but do not publish it or sign with it\&. This option is incompatible with \-P and \-A\&.
+ .RE
+ .PP
\-g \fIgenerator\fR
.RS 4
-If generating a Diffie Hellman key, use this generator\&. Allowed values are 2 and 5\&. If no generator is specified, a known prime from RFC 2539 will be used if possible; otherwise the default is 2\&.
-.RE
-.PP
+ If generating a Diffie Hellman key, use this generator\&. Allowed values are 2 and 5\&. If no generator is specified, a known prime from RFC 2539 will be used if possible; otherwise the default is 2\&.
+ .RE
+ .PP
\-h
.RS 4
-Prints a short summary of the options and arguments to
+ Prints a short summary of the options and arguments to
\fBdnssec\-keygen\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-K \fIdirectory\fR
.RS 4
-Sets the directory in which the key files are to be written\&.
-.RE
-.PP
+ Sets the directory in which the key files are to be written\&.
+ .RE
+ .PP
\-k
.RS 4
-Deprecated in favor of \-T KEY\&.
-.RE
-.PP
+ Deprecated in favor of \-T KEY\&.
+ .RE
+ .PP
\-L \fIttl\fR
.RS 4
-Sets the default TTL to use for this key when it is converted into a DNSKEY RR\&. If the key is imported into a zone, this is the TTL that will be used for it, unless there was already a DNSKEY RRset in place, in which case the existing TTL would take precedence\&. If this value is not set and there is no existing DNSKEY RRset, the TTL will default to the SOA TTL\&. Setting the default TTL to
+ Sets the default TTL to use for this key when it is converted into a DNSKEY RR\&. If the key is imported into a zone, this is the TTL that will be used for it, unless there was already a DNSKEY RRset in place, in which case the existing TTL would take precedence\&. If this value is not set and there is no existing DNSKEY RRset, the TTL will default to the SOA TTL\&. Setting the default TTL to
0
or
none
is the same as leaving it unset\&.
-.RE
-.PP
+ .RE
+ .PP
\-n \fInametype\fR
.RS 4
-Specifies the owner type of the key\&. The value of
+ Specifies the owner type of the key\&. The value of
\fBnametype\fR
must either be ZONE (for a DNSSEC zone key (KEY/DNSKEY)), HOST or ENTITY (for a key associated with a host (KEY)), USER (for a key associated with a user(KEY)) or OTHER (DNSKEY)\&. These values are case insensitive\&. Defaults to ZONE for DNSKEY generation\&.
-.RE
-.PP
+ .RE
+ .PP
\-p \fIprotocol\fR
.RS 4
-Sets the protocol value for the generated key, for use with
+ Sets the protocol value for the generated key, for use with
\fB\-T KEY\fR\&. The protocol is a number between 0 and 255\&. The default is 3 (DNSSEC)\&. Other possible values for this argument are listed in RFC 2535 and its successors\&.
-.RE
-.PP
+ .RE
+ .PP
\-q
.RS 4
-Quiet mode: Suppresses unnecessary output, including progress indication\&. Without this option, when
+ Quiet mode: Suppresses unnecessary output, including progress indication\&. Without this option, when
\fBdnssec\-keygen\fR
is run interactively to generate an RSA or DSA key pair, it will print a string of symbols to
stderr
indicating the progress of the key generation\&. A \*(Aq\&.\*(Aq indicates that a random number has been found which passed an initial sieve test; \*(Aq+\*(Aq means a number has passed a single round of the Miller\-Rabin primality test; a space means that the number has passed all the tests and is a satisfactory key\&.
-.RE
-.PP
+ .RE
+ .PP
\-r \fIrandomdev\fR
.RS 4
-Specifies the source of randomness\&. If the operating system does not provide a
+ Specifies the source of randomness\&. If the operating system does not provide a
/dev/random
or equivalent device, the default source of randomness is keyboard input\&.
randomdev
specifies the name of a character device or file containing random data to be used instead of the default\&. The special value
keyboard
indicates that keyboard input should be used\&.
-.RE
-.PP
+ .RE
+ .PP
\-S \fIkey\fR
.RS 4
-Create a new key which is an explicit successor to an existing key\&. The name, algorithm, size, and type of the key will be set to match the existing key\&. The activation date of the new key will be set to the inactivation date of the existing one\&. The publication date will be set to the activation date minus the prepublication interval, which defaults to 30 days\&.
-.RE
-.PP
+ Create a new key which is an explicit successor to an existing key\&. The name, algorithm, size, and type of the key will be set to match the existing key\&. The activation date of the new key will be set to the inactivation date of the existing one\&. The publication date will be set to the activation date minus the prepublication interval, which defaults to 30 days\&.
+ .RE
+ .PP
\-s \fIstrength\fR
.RS 4
-Specifies the strength value of the key\&. The strength is a number between 0 and 15, and currently has no defined purpose in DNSSEC\&.
-.RE
-.PP
+ Specifies the strength value of the key\&. The strength is a number between 0 and 15, and currently has no defined purpose in DNSSEC\&.
+ .RE
+ .PP
\-T \fIrrtype\fR
.RS 4
-Specifies the resource record type to use for the key\&.
+ Specifies the resource record type to use for the key\&.
\fBrrtype\fR
must be either DNSKEY or KEY\&. The default is DNSKEY when using a DNSSEC algorithm, but it can be overridden to KEY for use with SIG(0)\&.
Using any TSIG algorithm (HMAC\-* or DH) forces this option to KEY\&.
-.RE
-.PP
+ .RE
+ .PP
\-t \fItype\fR
.RS 4
-Indicates the use of the key, for use with
+ Indicates the use of the key, for use with
\fB\-T KEY\fR\&.
\fBtype\fR
must be one of AUTHCONF, NOAUTHCONF, NOAUTH, or NOCONF\&. The default is AUTHCONF\&. AUTH refers to the ability to authenticate data, and CONF the ability to encrypt data\&.
-.RE
-.PP
+ .RE
+ .PP
\-V
.RS 4
-Prints version information\&.
-.RE
-.PP
+ Prints version information\&.
+ .RE
+ .PP
\-v \fIlevel\fR
.RS 4
-Sets the debugging level\&.
-.RE
-.SH "TIMING OPTIONS"
-.PP
+ Sets the debugging level\&.
+ .RE
+ .SH "TIMING OPTIONS"
+ .PP
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS\&. If the argument begins with a \*(Aq+\*(Aq or \*(Aq\-\*(Aq, it is interpreted as an offset from the present time\&. For convenience, if such an offset is followed by one of the suffixes \*(Aqy\*(Aq, \*(Aqmo\*(Aq, \*(Aqw\*(Aq, \*(Aqd\*(Aq, \*(Aqh\*(Aq, or \*(Aqmi\*(Aq, then the offset is computed in years (defined as 365 24\-hour days, ignoring leap years), months (defined as 30 24\-hour days), weeks, days, hours, or minutes, respectively\&. Without a suffix, the offset is computed in seconds\&. To explicitly prevent a date from being set, use \*(Aqnone\*(Aq or \*(Aqnever\*(Aq\&.
-.PP
+ .PP
\-P \fIdate/offset\fR
.RS 4
-Sets the date on which a key is to be published to the zone\&. After that date, the key will be included in the zone but will not be used to sign it\&. If not set, and if the \-G option has not been used, the default is "now"\&.
-.RE
-.PP
+ Sets the date on which a key is to be published to the zone\&. After that date, the key will be included in the zone but will not be used to sign it\&. If not set, and if the \-G option has not been used, the default is "now"\&.
+ .RE
+ .PP
\-P sync \fIdate/offset\fR
.RS 4
-Sets the date on which CDS and CDNSKEY records that match this key are to be published to the zone\&.
-.RE
-.PP
+ Sets the date on which CDS and CDNSKEY records that match this key are to be published to the zone\&.
+ .RE
+ .PP
\-A \fIdate/offset\fR
.RS 4
-Sets the date on which the key is to be activated\&. After that date, the key will be included in the zone and used to sign it\&. If not set, and if the \-G option has not been used, the default is "now"\&. If set, if and \-P is not set, then the publication date will be set to the activation date minus the prepublication interval\&.
-.RE
-.PP
+ Sets the date on which the key is to be activated\&. After that date, the key will be included in the zone and used to sign it\&. If not set, and if the \-G option has not been used, the default is "now"\&. If set, if and \-P is not set, then the publication date will be set to the activation date minus the prepublication interval\&.
+ .RE
+ .PP
\-R \fIdate/offset\fR
.RS 4
-Sets the date on which the key is to be revoked\&. After that date, the key will be flagged as revoked\&. It will be included in the zone and will be used to sign it\&.
-.RE
-.PP
+ Sets the date on which the key is to be revoked\&. After that date, the key will be flagged as revoked\&. It will be included in the zone and will be used to sign it\&.
+ .RE
+ .PP
\-I \fIdate/offset\fR
.RS 4
-Sets the date on which the key is to be retired\&. After that date, the key will still be included in the zone, but it will not be used to sign it\&.
-.RE
-.PP
+ Sets the date on which the key is to be retired\&. After that date, the key will still be included in the zone, but it will not be used to sign it\&.
+ .RE
+ .PP
\-D \fIdate/offset\fR
.RS 4
-Sets the date on which the key is to be deleted\&. After that date, the key will no longer be included in the zone\&. (It may remain in the key repository, however\&.)
-.RE
-.PP
+ Sets the date on which the key is to be deleted\&. After that date, the key will no longer be included in the zone\&. (It may remain in the key repository, however\&.)
+ .RE
+ .PP
\-D sync \fIdate/offset\fR
.RS 4
-Sets the date on which the CDS and CDNSKEY records that match this key are to be deleted\&.
-.RE
-.PP
+ Sets the date on which the CDS and CDNSKEY records that match this key are to be deleted\&.
+ .RE
+ .PP
\-i \fIinterval\fR
.RS 4
-Sets the prepublication interval for a key\&. If set, then the publication and activation dates must be separated by at least this much time\&. If the activation date is specified but the publication date isn\*(Aqt, then the publication date will default to this much time before the activation date; conversely, if the publication date is specified but activation date isn\*(Aqt, then activation will be set to this much time after publication\&.
+ Sets the prepublication interval for a key\&. If set, then the publication and activation dates must be separated by at least this much time\&. If the activation date is specified but the publication date isn\*(Aqt, then the publication date will default to this much time before the activation date; conversely, if the publication date is specified but activation date isn\*(Aqt, then activation will be set to this much time after publication\&.
.sp
-If the key is being created as an explicit successor to another key, then the default prepublication interval is 30 days; otherwise it is zero\&.
+ If the key is being created as an explicit successor to another key, then the default prepublication interval is 30 days; otherwise it is zero\&.
.sp
-As with date offsets, if the argument is followed by one of the suffixes \*(Aqy\*(Aq, \*(Aqmo\*(Aq, \*(Aqw\*(Aq, \*(Aqd\*(Aq, \*(Aqh\*(Aq, or \*(Aqmi\*(Aq, then the interval is measured in years, months, weeks, days, hours, or minutes, respectively\&. Without a suffix, the interval is measured in seconds\&.
-.RE
-.SH "GENERATED KEYS"
-.PP
+ As with date offsets, if the argument is followed by one of the suffixes \*(Aqy\*(Aq, \*(Aqmo\*(Aq, \*(Aqw\*(Aq, \*(Aqd\*(Aq, \*(Aqh\*(Aq, or \*(Aqmi\*(Aq, then the interval is measured in years, months, weeks, days, hours, or minutes, respectively\&. Without a suffix, the interval is measured in seconds\&.
+ .RE
+ .SH "GENERATED KEYS"
+ .PP
When
\fBdnssec\-keygen\fR
completes successfully, it prints a string of the form
.sp -1
.IP \(bu 2.3
.\}
-nnnn
+ nnnn
is the key name\&.
-.RE
+ .RE
.sp
.RS 4
.ie n \{\
.sp -1
.IP \(bu 2.3
.\}
-aaa
+ aaa
is the numeric representation of the algorithm\&.
-.RE
+ .RE
.sp
.RS 4
.ie n \{\
.sp -1
.IP \(bu 2.3
.\}
-iiiii
+ iiiii
is the key identifier (or footprint)\&.
-.RE
-.PP
+ .RE
+ .PP
\fBdnssec\-keygen\fR
creates two files, with names based on the printed string\&.
Knnnn\&.+aaa+iiiii\&.key
contains the public key, and
Knnnn\&.+aaa+iiiii\&.private
contains the private key\&.
-.PP
+ .PP
The
\&.key
file contains a DNS KEY record that can be inserted into a zone file (directly or with a $INCLUDE statement)\&.
-.PP
+ .PP
The
\&.private
file contains algorithm\-specific fields\&. For obvious security reasons, this file does not have general read permission\&.
-.PP
+ .PP
Both
\&.key
and
\&.private
files are generated for symmetric cryptography algorithms such as HMAC\-MD5, even though the public and private key are equivalent\&.
-.SH "EXAMPLE"
-.PP
+ .SH "EXAMPLE"
+ .PP
To generate a 768\-bit DSA key for the domain
\fBexample\&.com\fR, the following command would be issued:
-.PP
+ .PP
\fBdnssec\-keygen \-a DSA \-b 768 \-n ZONE example\&.com\fR
-.PP
+ .PP
The command would print a string of the form:
-.PP
+ .PP
\fBKexample\&.com\&.+003+26160\fR
-.PP
+ .PP
In this example,
\fBdnssec\-keygen\fR
creates the files
Kexample\&.com\&.+003+26160\&.key
and
Kexample\&.com\&.+003+26160\&.private\&.
-.PP
+ .PP
To generate a matching key\-signing key, issue the command:
-.PP
+ .PP
\fBdnssec\-keygen \-a DSA \-b 768 \-n ZONE \-f KSK example\&.com\fR
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBdnssec-signzone\fR(8),
BIND 9 Administrator Reference Manual,
RFC 2539,
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-keygen</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.dnssec-keygen"></a><div class="titlepage"></div>
'\" t
.\" Title: dnssec-revoke
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2014-01-15
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
dnssec-revoke \- set the REVOKED bit on a DNSSEC key
-.SH "SYNOPSIS"
-.HP \w'\fBdnssec\-revoke\fR\ 'u
-\fBdnssec\-revoke\fR [\fB\-hr\fR] [\fB\-v\ \fR\fB\fIlevel\fR\fR] [\fB\-V\fR] [\fB\-K\ \fR\fB\fIdirectory\fR\fR] [\fB\-E\ \fR\fB\fIengine\fR\fR] [\fB\-f\fR] [\fB\-R\fR] {keyfile}
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBdnssec\-revoke\fR\ 'u
+ \fBdnssec\-revoke\fR
+ [\fB\-hr\fR]
+ [\fB\-v\ \fR\fB\fIlevel\fR\fR]
+ [\fB\-V\fR]
+ [\fB\-K\ \fR\fB\fIdirectory\fR\fR]
+ [\fB\-E\ \fR\fB\fIengine\fR\fR]
+ [\fB\-f\fR]
+ [\fB\-R\fR]
+ {keyfile}
+ .SH "DESCRIPTION"
+ .PP
\fBdnssec\-revoke\fR
reads a DNSSEC key file, sets the REVOKED bit on the key as defined in RFC 5011, and creates a new pair of key files containing the now\-revoked key\&.
-.SH "OPTIONS"
-.PP
+ .SH "OPTIONS"
+ .PP
\-h
.RS 4
-Emit usage message and exit\&.
-.RE
-.PP
+ Emit usage message and exit\&.
+ .RE
+ .PP
\-K \fIdirectory\fR
.RS 4
-Sets the directory in which the key files are to reside\&.
-.RE
-.PP
+ Sets the directory in which the key files are to reside\&.
+ .RE
+ .PP
\-r
.RS 4
-After writing the new keyset files remove the original keyset files\&.
-.RE
-.PP
+ After writing the new keyset files remove the original keyset files\&.
+ .RE
+ .PP
\-v \fIlevel\fR
.RS 4
-Sets the debugging level\&.
-.RE
-.PP
+ Sets the debugging level\&.
+ .RE
+ .PP
\-V
.RS 4
-Prints version information\&.
-.RE
-.PP
+ Prints version information\&.
+ .RE
+ .PP
\-E \fIengine\fR
.RS 4
-Specifies the cryptographic hardware to use, when applicable\&.
+ Specifies the cryptographic hardware to use, when applicable\&.
.sp
-When BIND is built with OpenSSL PKCS#11 support, this defaults to the string "pkcs11", which identifies an OpenSSL engine that can drive a cryptographic accelerator or hardware service module\&. When BIND is built with native PKCS#11 cryptography (\-\-enable\-native\-pkcs11), it defaults to the path of the PKCS#11 provider library specified via "\-\-with\-pkcs11"\&.
-.RE
-.PP
+ When BIND is built with OpenSSL PKCS#11 support, this defaults to the string "pkcs11", which identifies an OpenSSL engine that can drive a cryptographic accelerator or hardware service module\&. When BIND is built with native PKCS#11 cryptography (\-\-enable\-native\-pkcs11), it defaults to the path of the PKCS#11 provider library specified via "\-\-with\-pkcs11"\&.
+ .RE
+ .PP
\-f
.RS 4
-Force overwrite: Causes
+ Force overwrite: Causes
\fBdnssec\-revoke\fR
to write the new key pair even if a file already exists matching the algorithm and key ID of the revoked key\&.
-.RE
-.PP
+ .RE
+ .PP
\-R
.RS 4
-Print the key tag of the key with the REVOKE bit set but do not revoke the key\&.
-.RE
-.SH "SEE ALSO"
-.PP
+ Print the key tag of the key with the REVOKE bit set but do not revoke the key\&.
+ .RE
+ .SH "SEE ALSO"
+ .PP
\fBdnssec-keygen\fR(8),
BIND 9 Administrator Reference Manual,
RFC 5011\&.
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-revoke</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.dnssec-revoke"></a><div class="titlepage"></div>
'\" t
.\" Title: dnssec-settime
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2015-08-21
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
dnssec-settime \- set the key timing metadata for a DNSSEC key
-.SH "SYNOPSIS"
-.HP \w'\fBdnssec\-settime\fR\ 'u
-\fBdnssec\-settime\fR [\fB\-f\fR] [\fB\-K\ \fR\fB\fIdirectory\fR\fR] [\fB\-L\ \fR\fB\fIttl\fR\fR] [\fB\-P\ \fR\fB\fIdate/offset\fR\fR] [\fB\-P\ sync\ \fR\fB\fIdate/offset\fR\fR] [\fB\-A\ \fR\fB\fIdate/offset\fR\fR] [\fB\-R\ \fR\fB\fIdate/offset\fR\fR] [\fB\-I\ \fR\fB\fIdate/offset\fR\fR] [\fB\-D\ \fR\fB\fIdate/offset\fR\fR] [\fB\-D\ sync\ \fR\fB\fIdate/offset\fR\fR] [\fB\-S\ \fR\fB\fIkey\fR\fR] [\fB\-i\ \fR\fB\fIinterval\fR\fR] [\fB\-h\fR] [\fB\-V\fR] [\fB\-v\ \fR\fB\fIlevel\fR\fR] [\fB\-E\ \fR\fB\fIengine\fR\fR] {keyfile}
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBdnssec\-settime\fR\ 'u
+ \fBdnssec\-settime\fR
+ [\fB\-f\fR]
+ [\fB\-K\ \fR\fB\fIdirectory\fR\fR]
+ [\fB\-L\ \fR\fB\fIttl\fR\fR]
+ [\fB\-P\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-P\ sync\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-A\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-R\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-I\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-D\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-D\ sync\ \fR\fB\fIdate/offset\fR\fR]
+ [\fB\-S\ \fR\fB\fIkey\fR\fR]
+ [\fB\-i\ \fR\fB\fIinterval\fR\fR]
+ [\fB\-h\fR]
+ [\fB\-V\fR]
+ [\fB\-v\ \fR\fB\fIlevel\fR\fR]
+ [\fB\-E\ \fR\fB\fIengine\fR\fR]
+ {keyfile}
+ .SH "DESCRIPTION"
+ .PP
\fBdnssec\-settime\fR
reads a DNSSEC private key file and sets the key timing metadata as specified by the
\fB\-P\fR,
options\&. The metadata can then be used by
\fBdnssec\-signzone\fR
or other signing software to determine when a key is to be published, whether it should be used for signing a zone, etc\&.
-.PP
+ .PP
If none of these options is set on the command line, then
\fBdnssec\-settime\fR
simply prints the key timing metadata already stored in the key\&.
-.PP
+ .PP
When key metadata fields are changed, both files of a key pair (Knnnn\&.+aaa+iiiii\&.key
and
Knnnn\&.+aaa+iiiii\&.private) are regenerated\&. Metadata fields are stored in the private file\&. A human\-readable description of the metadata is also placed in comments in the key file\&. The private file\*(Aqs permissions are always set to be inaccessible to anyone other than the owner (mode 0600)\&.
-.SH "OPTIONS"
-.PP
+ .SH "OPTIONS"
+ .PP
\-f
.RS 4
-Force an update of an old\-format key with no metadata fields\&. Without this option,
+ Force an update of an old\-format key with no metadata fields\&. Without this option,
\fBdnssec\-settime\fR
will fail when attempting to update a legacy key\&. With this option, the key will be recreated in the new format, but with the original key data retained\&. The key\*(Aqs creation date will be set to the present time\&. If no other values are specified, then the key\*(Aqs publication and activation dates will also be set to the present time\&.
-.RE
-.PP
+ .RE
+ .PP
\-K \fIdirectory\fR
.RS 4
-Sets the directory in which the key files are to reside\&.
-.RE
-.PP
+ Sets the directory in which the key files are to reside\&.
+ .RE
+ .PP
\-L \fIttl\fR
.RS 4
-Sets the default TTL to use for this key when it is converted into a DNSKEY RR\&. If the key is imported into a zone, this is the TTL that will be used for it, unless there was already a DNSKEY RRset in place, in which case the existing TTL would take precedence\&. If this value is not set and there is no existing DNSKEY RRset, the TTL will default to the SOA TTL\&. Setting the default TTL to
+ Sets the default TTL to use for this key when it is converted into a DNSKEY RR\&. If the key is imported into a zone, this is the TTL that will be used for it, unless there was already a DNSKEY RRset in place, in which case the existing TTL would take precedence\&. If this value is not set and there is no existing DNSKEY RRset, the TTL will default to the SOA TTL\&. Setting the default TTL to
0
or
none
removes it from the key\&.
-.RE
-.PP
+ .RE
+ .PP
\-h
.RS 4
-Emit usage message and exit\&.
-.RE
-.PP
+ Emit usage message and exit\&.
+ .RE
+ .PP
\-V
.RS 4
-Prints version information\&.
-.RE
-.PP
+ Prints version information\&.
+ .RE
+ .PP
\-v \fIlevel\fR
.RS 4
-Sets the debugging level\&.
-.RE
-.PP
+ Sets the debugging level\&.
+ .RE
+ .PP
\-E \fIengine\fR
.RS 4
-Specifies the cryptographic hardware to use, when applicable\&.
+ Specifies the cryptographic hardware to use, when applicable\&.
.sp
-When BIND is built with OpenSSL PKCS#11 support, this defaults to the string "pkcs11", which identifies an OpenSSL engine that can drive a cryptographic accelerator or hardware service module\&. When BIND is built with native PKCS#11 cryptography (\-\-enable\-native\-pkcs11), it defaults to the path of the PKCS#11 provider library specified via "\-\-with\-pkcs11"\&.
-.RE
-.SH "TIMING OPTIONS"
-.PP
+ When BIND is built with OpenSSL PKCS#11 support, this defaults to the string "pkcs11", which identifies an OpenSSL engine that can drive a cryptographic accelerator or hardware service module\&. When BIND is built with native PKCS#11 cryptography (\-\-enable\-native\-pkcs11), it defaults to the path of the PKCS#11 provider library specified via "\-\-with\-pkcs11"\&.
+ .RE
+ .SH "TIMING OPTIONS"
+ .PP
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS\&. If the argument begins with a \*(Aq+\*(Aq or \*(Aq\-\*(Aq, it is interpreted as an offset from the present time\&. For convenience, if such an offset is followed by one of the suffixes \*(Aqy\*(Aq, \*(Aqmo\*(Aq, \*(Aqw\*(Aq, \*(Aqd\*(Aq, \*(Aqh\*(Aq, or \*(Aqmi\*(Aq, then the offset is computed in years (defined as 365 24\-hour days, ignoring leap years), months (defined as 30 24\-hour days), weeks, days, hours, or minutes, respectively\&. Without a suffix, the offset is computed in seconds\&. To unset a date, use \*(Aqnone\*(Aq or \*(Aqnever\*(Aq\&.
-.PP
+ .PP
\-P \fIdate/offset\fR
.RS 4
-Sets the date on which a key is to be published to the zone\&. After that date, the key will be included in the zone but will not be used to sign it\&.
-.RE
-.PP
+ Sets the date on which a key is to be published to the zone\&. After that date, the key will be included in the zone but will not be used to sign it\&.
+ .RE
+ .PP
\-P sync \fIdate/offset\fR
.RS 4
-Sets the date on which CDS and CDNSKEY records that match this key are to be published to the zone\&.
-.RE
-.PP
+ Sets the date on which CDS and CDNSKEY records that match this key are to be published to the zone\&.
+ .RE
+ .PP
\-A \fIdate/offset\fR
.RS 4
-Sets the date on which the key is to be activated\&. After that date, the key will be included in the zone and used to sign it\&.
-.RE
-.PP
+ Sets the date on which the key is to be activated\&. After that date, the key will be included in the zone and used to sign it\&.
+ .RE
+ .PP
\-R \fIdate/offset\fR
.RS 4
-Sets the date on which the key is to be revoked\&. After that date, the key will be flagged as revoked\&. It will be included in the zone and will be used to sign it\&.
-.RE
-.PP
+ Sets the date on which the key is to be revoked\&. After that date, the key will be flagged as revoked\&. It will be included in the zone and will be used to sign it\&.
+ .RE
+ .PP
\-I \fIdate/offset\fR
.RS 4
-Sets the date on which the key is to be retired\&. After that date, the key will still be included in the zone, but it will not be used to sign it\&.
-.RE
-.PP
+ Sets the date on which the key is to be retired\&. After that date, the key will still be included in the zone, but it will not be used to sign it\&.
+ .RE
+ .PP
\-D \fIdate/offset\fR
.RS 4
-Sets the date on which the key is to be deleted\&. After that date, the key will no longer be included in the zone\&. (It may remain in the key repository, however\&.)
-.RE
-.PP
+ Sets the date on which the key is to be deleted\&. After that date, the key will no longer be included in the zone\&. (It may remain in the key repository, however\&.)
+ .RE
+ .PP
\-D sync \fIdate/offset\fR
.RS 4
-Sets the date on which the CDS and CDNSKEY records that match this key are to be deleted\&.
-.RE
-.PP
+ Sets the date on which the CDS and CDNSKEY records that match this key are to be deleted\&.
+ .RE
+ .PP
\-S \fIpredecessor key\fR
.RS 4
-Select a key for which the key being modified will be an explicit successor\&. The name, algorithm, size, and type of the predecessor key must exactly match those of the key being modified\&. The activation date of the successor key will be set to the inactivation date of the predecessor\&. The publication date will be set to the activation date minus the prepublication interval, which defaults to 30 days\&.
-.RE
-.PP
+ Select a key for which the key being modified will be an explicit successor\&. The name, algorithm, size, and type of the predecessor key must exactly match those of the key being modified\&. The activation date of the successor key will be set to the inactivation date of the predecessor\&. The publication date will be set to the activation date minus the prepublication interval, which defaults to 30 days\&.
+ .RE
+ .PP
\-i \fIinterval\fR
.RS 4
-Sets the prepublication interval for a key\&. If set, then the publication and activation dates must be separated by at least this much time\&. If the activation date is specified but the publication date isn\*(Aqt, then the publication date will default to this much time before the activation date; conversely, if the publication date is specified but activation date isn\*(Aqt, then activation will be set to this much time after publication\&.
+ Sets the prepublication interval for a key\&. If set, then the publication and activation dates must be separated by at least this much time\&. If the activation date is specified but the publication date isn\*(Aqt, then the publication date will default to this much time before the activation date; conversely, if the publication date is specified but activation date isn\*(Aqt, then activation will be set to this much time after publication\&.
.sp
-If the key is being set to be an explicit successor to another key, then the default prepublication interval is 30 days; otherwise it is zero\&.
+ If the key is being set to be an explicit successor to another key, then the default prepublication interval is 30 days; otherwise it is zero\&.
.sp
-As with date offsets, if the argument is followed by one of the suffixes \*(Aqy\*(Aq, \*(Aqmo\*(Aq, \*(Aqw\*(Aq, \*(Aqd\*(Aq, \*(Aqh\*(Aq, or \*(Aqmi\*(Aq, then the interval is measured in years, months, weeks, days, hours, or minutes, respectively\&. Without a suffix, the interval is measured in seconds\&.
-.RE
-.SH "PRINTING OPTIONS"
-.PP
+ As with date offsets, if the argument is followed by one of the suffixes \*(Aqy\*(Aq, \*(Aqmo\*(Aq, \*(Aqw\*(Aq, \*(Aqd\*(Aq, \*(Aqh\*(Aq, or \*(Aqmi\*(Aq, then the interval is measured in years, months, weeks, days, hours, or minutes, respectively\&. Without a suffix, the interval is measured in seconds\&.
+ .RE
+ .SH "PRINTING OPTIONS"
+ .PP
\fBdnssec\-settime\fR
can also be used to print the timing metadata associated with a key\&.
-.PP
+ .PP
\-u
.RS 4
-Print times in UNIX epoch format\&.
-.RE
-.PP
+ Print times in UNIX epoch format\&.
+ .RE
+ .PP
\-p \fIC/P/Psync/A/R/I/D/Dsync/all\fR
.RS 4
-Print a specific metadata value or set of metadata values\&. The
+ Print a specific metadata value or set of metadata values\&. The
\fB\-p\fR
option may be followed by one or more of the following letters or strings to indicate which value or values to print:
\fBC\fR
\fBDsync\fR
for the CDS and CDNSKEY deletion date To print all of the metadata, use
\fB\-p all\fR\&.
-.RE
-.SH "SEE ALSO"
-.PP
+ .RE
+ .SH "SEE ALSO"
+ .PP
\fBdnssec-keygen\fR(8),
\fBdnssec-signzone\fR(8),
BIND 9 Administrator Reference Manual,
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-settime</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.dnssec-settime"></a><div class="titlepage"></div>
'\" t
.\" Title: dnssec-signzone
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2014-02-18
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
dnssec-signzone \- DNSSEC zone signing tool
-.SH "SYNOPSIS"
-.HP \w'\fBdnssec\-signzone\fR\ 'u
-\fBdnssec\-signzone\fR [\fB\-a\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-d\ \fR\fB\fIdirectory\fR\fR] [\fB\-D\fR] [\fB\-E\ \fR\fB\fIengine\fR\fR] [\fB\-e\ \fR\fB\fIend\-time\fR\fR] [\fB\-f\ \fR\fB\fIoutput\-file\fR\fR] [\fB\-g\fR] [\fB\-h\fR] [\fB\-i\ \fR\fB\fIinterval\fR\fR] [\fB\-I\ \fR\fB\fIinput\-format\fR\fR] [\fB\-j\ \fR\fB\fIjitter\fR\fR] [\fB\-K\ \fR\fB\fIdirectory\fR\fR] [\fB\-k\ \fR\fB\fIkey\fR\fR] [\fB\-L\ \fR\fB\fIserial\fR\fR] [\fB\-l\ \fR\fB\fIdomain\fR\fR] [\fB\-M\ \fR\fB\fImaxttl\fR\fR] [\fB\-N\ \fR\fB\fIsoa\-serial\-format\fR\fR] [\fB\-o\ \fR\fB\fIorigin\fR\fR] [\fB\-O\ \fR\fB\fIoutput\-format\fR\fR] [\fB\-P\fR] [\fB\-p\fR] [\fB\-Q\fR] [\fB\-R\fR] [\fB\-r\ \fR\fB\fIrandomdev\fR\fR] [\fB\-S\fR] [\fB\-s\ \fR\fB\fIstart\-time\fR\fR] [\fB\-T\ \fR\fB\fIttl\fR\fR] [\fB\-t\fR] [\fB\-u\fR] [\fB\-v\ \fR\fB\fIlevel\fR\fR] [\fB\-V\fR] [\fB\-X\ \fR\fB\fIextended\ end\-time\fR\fR] [\fB\-x\fR] [\fB\-z\fR] [\fB\-3\ \fR\fB\fIsalt\fR\fR] [\fB\-H\ \fR\fB\fIiterations\fR\fR] [\fB\-A\fR] {zonefile} [key...]
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBdnssec\-signzone\fR\ 'u
+ \fBdnssec\-signzone\fR
+ [\fB\-a\fR]
+ [\fB\-c\ \fR\fB\fIclass\fR\fR]
+ [\fB\-d\ \fR\fB\fIdirectory\fR\fR]
+ [\fB\-D\fR]
+ [\fB\-E\ \fR\fB\fIengine\fR\fR]
+ [\fB\-e\ \fR\fB\fIend\-time\fR\fR]
+ [\fB\-f\ \fR\fB\fIoutput\-file\fR\fR]
+ [\fB\-g\fR]
+ [\fB\-h\fR]
+ [\fB\-i\ \fR\fB\fIinterval\fR\fR]
+ [\fB\-I\ \fR\fB\fIinput\-format\fR\fR]
+ [\fB\-j\ \fR\fB\fIjitter\fR\fR]
+ [\fB\-K\ \fR\fB\fIdirectory\fR\fR]
+ [\fB\-k\ \fR\fB\fIkey\fR\fR]
+ [\fB\-L\ \fR\fB\fIserial\fR\fR]
+ [\fB\-l\ \fR\fB\fIdomain\fR\fR]
+ [\fB\-M\ \fR\fB\fImaxttl\fR\fR]
+ [\fB\-N\ \fR\fB\fIsoa\-serial\-format\fR\fR]
+ [\fB\-o\ \fR\fB\fIorigin\fR\fR]
+ [\fB\-O\ \fR\fB\fIoutput\-format\fR\fR]
+ [\fB\-P\fR]
+ [\fB\-p\fR]
+ [\fB\-Q\fR]
+ [\fB\-R\fR]
+ [\fB\-r\ \fR\fB\fIrandomdev\fR\fR]
+ [\fB\-S\fR]
+ [\fB\-s\ \fR\fB\fIstart\-time\fR\fR]
+ [\fB\-T\ \fR\fB\fIttl\fR\fR]
+ [\fB\-t\fR]
+ [\fB\-u\fR]
+ [\fB\-v\ \fR\fB\fIlevel\fR\fR]
+ [\fB\-V\fR]
+ [\fB\-X\ \fR\fB\fIextended\ end\-time\fR\fR]
+ [\fB\-x\fR]
+ [\fB\-z\fR]
+ [\fB\-3\ \fR\fB\fIsalt\fR\fR]
+ [\fB\-H\ \fR\fB\fIiterations\fR\fR]
+ [\fB\-A\fR]
+ {zonefile}
+ [key...]
+ .SH "DESCRIPTION"
+ .PP
\fBdnssec\-signzone\fR
signs a zone\&. It generates NSEC and RRSIG records and produces a signed version of the zone\&. The security status of delegations from the signed zone (that is, whether the child zones are secure or not) is determined by the presence or absence of a
keyset
file for each child zone\&.
-.SH "OPTIONS"
-.PP
+ .SH "OPTIONS"
+ .PP
\-a
.RS 4
-Verify all generated signatures\&.
-.RE
-.PP
+ Verify all generated signatures\&.
+ .RE
+ .PP
\-c \fIclass\fR
.RS 4
-Specifies the DNS class of the zone\&.
-.RE
-.PP
+ Specifies the DNS class of the zone\&.
+ .RE
+ .PP
\-C
.RS 4
-Compatibility mode: Generate a
+ Compatibility mode: Generate a
keyset\-\fIzonename\fR
file in addition to
dsset\-\fIzonename\fR
when signing a zone, for use by older versions of
\fBdnssec\-signzone\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-d \fIdirectory\fR
.RS 4
-Look for
+ Look for
dsset\-
or
keyset\-
files in
\fBdirectory\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-D
.RS 4
-Output only those record types automatically managed by
+ Output only those record types automatically managed by
\fBdnssec\-signzone\fR, i\&.e\&. RRSIG, NSEC, NSEC3 and NSEC3PARAM records\&. If smart signing (\fB\-S\fR) is used, DNSKEY records are also included\&. The resulting file can be included in the original zone file with
\fB$INCLUDE\fR\&. This option cannot be combined with
\fB\-O raw\fR,
\fB\-O map\fR, or serial number updating\&.
-.RE
-.PP
+ .RE
+ .PP
\-E \fIengine\fR
.RS 4
-When applicable, specifies the hardware to use for cryptographic operations, such as a secure key store used for signing\&.
+ When applicable, specifies the hardware to use for cryptographic operations, such as a secure key store used for signing\&.
.sp
-When BIND is built with OpenSSL PKCS#11 support, this defaults to the string "pkcs11", which identifies an OpenSSL engine that can drive a cryptographic accelerator or hardware service module\&. When BIND is built with native PKCS#11 cryptography (\-\-enable\-native\-pkcs11), it defaults to the path of the PKCS#11 provider library specified via "\-\-with\-pkcs11"\&.
-.RE
-.PP
+ When BIND is built with OpenSSL PKCS#11 support, this defaults to the string "pkcs11", which identifies an OpenSSL engine that can drive a cryptographic accelerator or hardware service module\&. When BIND is built with native PKCS#11 cryptography (\-\-enable\-native\-pkcs11), it defaults to the path of the PKCS#11 provider library specified via "\-\-with\-pkcs11"\&.
+ .RE
+ .PP
\-g
.RS 4
-Generate DS records for child zones from
+ Generate DS records for child zones from
dsset\-
or
keyset\-
file\&. Existing DS records will be removed\&.
-.RE
-.PP
+ .RE
+ .PP
\-K \fIdirectory\fR
.RS 4
-Key repository: Specify a directory to search for DNSSEC keys\&. If not specified, defaults to the current directory\&.
-.RE
-.PP
+ Key repository: Specify a directory to search for DNSSEC keys\&. If not specified, defaults to the current directory\&.
+ .RE
+ .PP
\-k \fIkey\fR
.RS 4
-Treat specified key as a key signing key ignoring any key flags\&. This option may be specified multiple times\&.
-.RE
-.PP
+ Treat specified key as a key signing key ignoring any key flags\&. This option may be specified multiple times\&.
+ .RE
+ .PP
\-l \fIdomain\fR
.RS 4
-Generate a DLV set in addition to the key (DNSKEY) and DS sets\&. The domain is appended to the name of the records\&.
-.RE
-.PP
+ Generate a DLV set in addition to the key (DNSKEY) and DS sets\&. The domain is appended to the name of the records\&.
+ .RE
+ .PP
\-M \fImaxttl\fR
.RS 4
-Sets the maximum TTL for the signed zone\&. Any TTL higher than
+ Sets the maximum TTL for the signed zone\&. Any TTL higher than
\fImaxttl\fR
in the input zone will be reduced to
\fImaxttl\fR
in
named\&.conf\&. (Note: This option is incompatible with
\fB\-D\fR, because it modifies non\-DNSSEC data in the output zone\&.)
-.RE
-.PP
+ .RE
+ .PP
\-s \fIstart\-time\fR
.RS 4
-Specify the date and time when the generated RRSIG records become valid\&. This can be either an absolute or relative time\&. An absolute start time is indicated by a number in YYYYMMDDHHMMSS notation; 20000530144500 denotes 14:45:00 UTC on May 30th, 2000\&. A relative start time is indicated by +N, which is N seconds from the current time\&. If no
+ Specify the date and time when the generated RRSIG records become valid\&. This can be either an absolute or relative time\&. An absolute start time is indicated by a number in YYYYMMDDHHMMSS notation; 20000530144500 denotes 14:45:00 UTC on May 30th, 2000\&. A relative start time is indicated by +N, which is N seconds from the current time\&. If no
\fBstart\-time\fR
is specified, the current time minus 1 hour (to allow for clock skew) is used\&.
-.RE
-.PP
+ .RE
+ .PP
\-e \fIend\-time\fR
.RS 4
-Specify the date and time when the generated RRSIG records expire\&. As with
+ Specify the date and time when the generated RRSIG records expire\&. As with
\fBstart\-time\fR, an absolute time is indicated in YYYYMMDDHHMMSS notation\&. A time relative to the start time is indicated with +N, which is N seconds from the start time\&. A time relative to the current time is indicated with now+N\&. If no
\fBend\-time\fR
is specified, 30 days from the start time is used as a default\&.
\fBend\-time\fR
must be later than
\fBstart\-time\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-X \fIextended end\-time\fR
.RS 4
-Specify the date and time when the generated RRSIG records for the DNSKEY RRset will expire\&. This is to be used in cases when the DNSKEY signatures need to persist longer than signatures on other records; e\&.g\&., when the private component of the KSK is kept offline and the KSK signature is to be refreshed manually\&.
+ Specify the date and time when the generated RRSIG records for the DNSKEY RRset will expire\&. This is to be used in cases when the DNSKEY signatures need to persist longer than signatures on other records; e\&.g\&., when the private component of the KSK is kept offline and the KSK signature is to be refreshed manually\&.
.sp
-As with
+ As with
\fBstart\-time\fR, an absolute time is indicated in YYYYMMDDHHMMSS notation\&. A time relative to the start time is indicated with +N, which is N seconds from the start time\&. A time relative to the current time is indicated with now+N\&. If no
\fBextended end\-time\fR
is specified, the value of
\fBextended end\-time\fR
must be later than
\fBstart\-time\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-f \fIoutput\-file\fR
.RS 4
-The name of the output file containing the signed zone\&. The default is to append
+ The name of the output file containing the signed zone\&. The default is to append
\&.signed
to the input filename\&. If
\fBoutput\-file\fR
is set to
"\-", then the signed zone is written to the standard output, with a default output format of "full"\&.
-.RE
-.PP
+ .RE
+ .PP
\-h
.RS 4
-Prints a short summary of the options and arguments to
+ Prints a short summary of the options and arguments to
\fBdnssec\-signzone\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-V
.RS 4
-Prints version information\&.
-.RE
-.PP
+ Prints version information\&.
+ .RE
+ .PP
\-i \fIinterval\fR
.RS 4
-When a previously\-signed zone is passed as input, records may be resigned\&. The
+ When a previously\-signed zone is passed as input, records may be resigned\&. The
\fBinterval\fR
option specifies the cycle interval as an offset from the current time (in seconds)\&. If a RRSIG record expires after the cycle interval, it is retained\&. Otherwise, it is considered to be expiring soon, and it will be replaced\&.
.sp
-The default cycle interval is one quarter of the difference between the signature end and start times\&. So if neither
+ The default cycle interval is one quarter of the difference between the signature end and start times\&. So if neither
\fBend\-time\fR
or
\fBstart\-time\fR
are specified,
\fBdnssec\-signzone\fR
generates signatures that are valid for 30 days, with a cycle interval of 7\&.5 days\&. Therefore, if any existing RRSIG records are due to expire in less than 7\&.5 days, they would be replaced\&.
-.RE
-.PP
+ .RE
+ .PP
\-I \fIinput\-format\fR
.RS 4
-The format of the input zone file\&. Possible formats are
+ The format of the input zone file\&. Possible formats are
\fB"text"\fR
(default),
\fB"raw"\fR, and
\fB"map"\fR\&. This option is primarily intended to be used for dynamic signed zones so that the dumped zone file in a non\-text format containing updates can be signed directly\&. The use of this option does not make much sense for non\-dynamic zones\&.
-.RE
-.PP
+ .RE
+ .PP
\-j \fIjitter\fR
.RS 4
-When signing a zone with a fixed signature lifetime, all RRSIG records issued at the time of signing expires simultaneously\&. If the zone is incrementally signed, i\&.e\&. a previously\-signed zone is passed as input to the signer, all expired signatures have to be regenerated at about the same time\&. The
+ When signing a zone with a fixed signature lifetime, all RRSIG records issued at the time of signing expires simultaneously\&. If the zone is incrementally signed, i\&.e\&. a previously\-signed zone is passed as input to the signer, all expired signatures have to be regenerated at about the same time\&. The
\fBjitter\fR
option specifies a jitter window that will be used to randomize the signature expire time, thus spreading incremental signature regeneration over time\&.
.sp
-Signature lifetime jitter also to some extent benefits validators and servers by spreading out cache expiration, i\&.e\&. if large numbers of RRSIGs don\*(Aqt expire at the same time from all caches there will be less congestion than if all validators need to refetch at mostly the same time\&.
-.RE
-.PP
+ Signature lifetime jitter also to some extent benefits validators and servers by spreading out cache expiration, i\&.e\&. if large numbers of RRSIGs don\*(Aqt expire at the same time from all caches there will be less congestion than if all validators need to refetch at mostly the same time\&.
+ .RE
+ .PP
\-L \fIserial\fR
.RS 4
-When writing a signed zone to "raw" or "map" format, set the "source serial" value in the header to the specified serial number\&. (This is expected to be used primarily for testing purposes\&.)
-.RE
-.PP
+ When writing a signed zone to "raw" or "map" format, set the "source serial" value in the header to the specified serial number\&. (This is expected to be used primarily for testing purposes\&.)
+ .RE
+ .PP
\-n \fIncpus\fR
.RS 4
-Specifies the number of threads to use\&. By default, one thread is started for each detected CPU\&.
-.RE
-.PP
+ Specifies the number of threads to use\&. By default, one thread is started for each detected CPU\&.
+ .RE
+ .PP
\-N \fIsoa\-serial\-format\fR
.RS 4
-The SOA serial number format of the signed zone\&. Possible formats are
+ The SOA serial number format of the signed zone\&. Possible formats are
\fB"keep"\fR
(default),
\fB"increment"\fR,
\fB"unixtime"\fR, and
\fB"date"\fR\&.
-.PP
+ .PP
\fB"keep"\fR
.RS 4
-Do not modify the SOA serial number\&.
-.RE
-.PP
+ Do not modify the SOA serial number\&.
+ .RE
+ .PP
\fB"increment"\fR
.RS 4
-Increment the SOA serial number using RFC 1982 arithmetics\&.
-.RE
-.PP
+ Increment the SOA serial number using RFC 1982 arithmetics\&.
+ .RE
+ .PP
\fB"unixtime"\fR
.RS 4
-Set the SOA serial number to the number of seconds since epoch\&.
-.RE
-.PP
+ Set the SOA serial number to the number of seconds since epoch\&.
+ .RE
+ .PP
\fB"date"\fR
.RS 4
-Set the SOA serial number to today\*(Aqs date in YYYYMMDDNN format\&.
-.RE
-.RE
-.PP
+ Set the SOA serial number to today\*(Aqs date in YYYYMMDDNN format\&.
+ .RE
+ .sp
+ .RE
+ .PP
\-o \fIorigin\fR
.RS 4
-The zone origin\&. If not specified, the name of the zone file is assumed to be the origin\&.
-.RE
-.PP
+ The zone origin\&. If not specified, the name of the zone file is assumed to be the origin\&.
+ .RE
+ .PP
\-O \fIoutput\-format\fR
.RS 4
-The format of the output file containing the signed zone\&. Possible formats are
+ The format of the output file containing the signed zone\&. Possible formats are
\fB"text"\fR
(default), which is the standard textual representation of the zone;
\fB"full"\fR, which is text output in a format suitable for processing by external scripts; and
\fB"raw=N"\fR
specifies the format version of the raw zone file: if N is 0, the raw file can be read by any version of
\fBnamed\fR; if N is 1, the file can be read by release 9\&.9\&.0 or higher; the default is 1\&.
-.RE
-.PP
+ .RE
+ .PP
\-p
.RS 4
-Use pseudo\-random data when signing the zone\&. This is faster, but less secure, than using real random data\&. This option may be useful when signing large zones or when the entropy source is limited\&.
-.RE
-.PP
+ Use pseudo\-random data when signing the zone\&. This is faster, but less secure, than using real random data\&. This option may be useful when signing large zones or when the entropy source is limited\&.
+ .RE
+ .PP
\-P
.RS 4
-Disable post sign verification tests\&.
+ Disable post sign verification tests\&.
.sp
-The post sign verification test ensures that for each algorithm in use there is at least one non revoked self signed KSK key, that all revoked KSK keys are self signed, and that all records in the zone are signed by the algorithm\&. This option skips these tests\&.
-.RE
-.PP
+ The post sign verification test ensures that for each algorithm in use there is at least one non revoked self signed KSK key, that all revoked KSK keys are self signed, and that all records in the zone are signed by the algorithm\&. This option skips these tests\&.
+ .RE
+ .PP
\-Q
.RS 4
-Remove signatures from keys that are no longer active\&.
+ Remove signatures from keys that are no longer active\&.
.sp
-Normally, when a previously\-signed zone is passed as input to the signer, and a DNSKEY record has been removed and replaced with a new one, signatures from the old key that are still within their validity period are retained\&. This allows the zone to continue to validate with cached copies of the old DNSKEY RRset\&. The
+ Normally, when a previously\-signed zone is passed as input to the signer, and a DNSKEY record has been removed and replaced with a new one, signatures from the old key that are still within their validity period are retained\&. This allows the zone to continue to validate with cached copies of the old DNSKEY RRset\&. The
\fB\-Q\fR
forces
\fBdnssec\-signzone\fR
to remove signatures from keys that are no longer active\&. This enables ZSK rollover using the procedure described in RFC 4641, section 4\&.2\&.1\&.1 ("Pre\-Publish Key Rollover")\&.
-.RE
-.PP
+ .RE
+ .PP
\-R
.RS 4
-Remove signatures from keys that are no longer published\&.
+ Remove signatures from keys that are no longer published\&.
.sp
-This option is similar to
+ This option is similar to
\fB\-Q\fR, except it forces
\fBdnssec\-signzone\fR
to signatures from keys that are no longer published\&. This enables ZSK rollover using the procedure described in RFC 4641, section 4\&.2\&.1\&.2 ("Double Signature Zone Signing Key Rollover")\&.
-.RE
-.PP
+ .RE
+ .PP
\-r \fIrandomdev\fR
.RS 4
-Specifies the source of randomness\&. If the operating system does not provide a
+ Specifies the source of randomness\&. If the operating system does not provide a
/dev/random
or equivalent device, the default source of randomness is keyboard input\&.
randomdev
specifies the name of a character device or file containing random data to be used instead of the default\&. The special value
keyboard
indicates that keyboard input should be used\&.
-.RE
-.PP
+ .RE
+ .PP
\-S
.RS 4
-Smart signing: Instructs
+ Smart signing: Instructs
\fBdnssec\-signzone\fR
to search the key repository for keys that match the zone being signed, and to include them in the zone if appropriate\&.
.sp
-When a key is found, its timing metadata is examined to determine how it should be used, according to the following rules\&. Each successive rule takes priority over the prior ones:
-.PP
-.RS 4
-If no timing metadata has been set for the key, the key is published in the zone and used to sign the zone\&.
-.RE
-.PP
-.RS 4
-If the key\*(Aqs publication date is set and is in the past, the key is published in the zone\&.
-.RE
-.PP
-.RS 4
-If the key\*(Aqs activation date is set and in the past, the key is published (regardless of publication date) and used to sign the zone\&.
-.RE
-.PP
-.RS 4
-If the key\*(Aqs revocation date is set and in the past, and the key is published, then the key is revoked, and the revoked key is used to sign the zone\&.
-.RE
-.PP
-.RS 4
-If either of the key\*(Aqs unpublication or deletion dates are set and in the past, the key is NOT published or used to sign the zone, regardless of any other metadata\&.
-.RE
-.RE
-.PP
+ When a key is found, its timing metadata is examined to determine how it should be used, according to the following rules\&. Each successive rule takes priority over the prior ones:
+ .PP
+.RS 4
+ If no timing metadata has been set for the key, the key is published in the zone and used to sign the zone\&.
+ .RE
+ .PP
+.RS 4
+ If the key\*(Aqs publication date is set and is in the past, the key is published in the zone\&.
+ .RE
+ .PP
+.RS 4
+ If the key\*(Aqs activation date is set and in the past, the key is published (regardless of publication date) and used to sign the zone\&.
+ .RE
+ .PP
+.RS 4
+ If the key\*(Aqs revocation date is set and in the past, and the key is published, then the key is revoked, and the revoked key is used to sign the zone\&.
+ .RE
+ .PP
+.RS 4
+ If either of the key\*(Aqs unpublication or deletion dates are set and in the past, the key is NOT published or used to sign the zone, regardless of any other metadata\&.
+ .RE
+ .sp
+ .RE
+ .PP
\-T \fIttl\fR
.RS 4
-Specifies a TTL to be used for new DNSKEY records imported into the zone from the key repository\&. If not specified, the default is the TTL value from the zone\*(Aqs SOA record\&. This option is ignored when signing without
+ Specifies a TTL to be used for new DNSKEY records imported into the zone from the key repository\&. If not specified, the default is the TTL value from the zone\*(Aqs SOA record\&. This option is ignored when signing without
\fB\-S\fR, since DNSKEY records are not imported from the key repository in that case\&. It is also ignored if there are any pre\-existing DNSKEY records at the zone apex, in which case new records\*(Aq TTL values will be set to match them, or if any of the imported DNSKEY records had a default TTL value\&. In the event of a a conflict between TTL values in imported keys, the shortest one is used\&.
-.RE
-.PP
+ .RE
+ .PP
\-t
.RS 4
-Print statistics at completion\&.
-.RE
-.PP
+ Print statistics at completion\&.
+ .RE
+ .PP
\-u
.RS 4
-Update NSEC/NSEC3 chain when re\-signing a previously signed zone\&. With this option, a zone signed with NSEC can be switched to NSEC3, or a zone signed with NSEC3 can be switch to NSEC or to NSEC3 with different parameters\&. Without this option,
+ Update NSEC/NSEC3 chain when re\-signing a previously signed zone\&. With this option, a zone signed with NSEC can be switched to NSEC3, or a zone signed with NSEC3 can be switch to NSEC or to NSEC3 with different parameters\&. Without this option,
\fBdnssec\-signzone\fR
will retain the existing chain when re\-signing\&.
-.RE
-.PP
+ .RE
+ .PP
\-v \fIlevel\fR
.RS 4
-Sets the debugging level\&.
-.RE
-.PP
+ Sets the debugging level\&.
+ .RE
+ .PP
\-x
.RS 4
-Only sign the DNSKEY RRset with key\-signing keys, and omit signatures from zone\-signing keys\&. (This is similar to the
+ Only sign the DNSKEY RRset with key\-signing keys, and omit signatures from zone\-signing keys\&. (This is similar to the
\fBdnssec\-dnskey\-kskonly yes;\fR
zone option in
\fBnamed\fR\&.)
-.RE
-.PP
+ .RE
+ .PP
\-z
.RS 4
-Ignore KSK flag on key when determining what to sign\&. This causes KSK\-flagged keys to sign all records, not just the DNSKEY RRset\&. (This is similar to the
+ Ignore KSK flag on key when determining what to sign\&. This causes KSK\-flagged keys to sign all records, not just the DNSKEY RRset\&. (This is similar to the
\fBupdate\-check\-ksk no;\fR
zone option in
\fBnamed\fR\&.)
-.RE
-.PP
+ .RE
+ .PP
\-3 \fIsalt\fR
.RS 4
-Generate an NSEC3 chain with the given hex encoded salt\&. A dash (\fIsalt\fR) can be used to indicate that no salt is to be used when generating the NSEC3 chain\&.
-.RE
-.PP
+ Generate an NSEC3 chain with the given hex encoded salt\&. A dash (\fIsalt\fR) can be used to indicate that no salt is to be used when generating the NSEC3 chain\&.
+ .RE
+ .PP
\-H \fIiterations\fR
.RS 4
-When generating an NSEC3 chain, use this many iterations\&. The default is 10\&.
-.RE
-.PP
+ When generating an NSEC3 chain, use this many iterations\&. The default is 10\&.
+ .RE
+ .PP
\-A
.RS 4
-When generating an NSEC3 chain set the OPTOUT flag on all NSEC3 records and do not generate NSEC3 records for insecure delegations\&.
+ When generating an NSEC3 chain set the OPTOUT flag on all NSEC3 records and do not generate NSEC3 records for insecure delegations\&.
.sp
-Using this option twice (i\&.e\&.,
+ Using this option twice (i\&.e\&.,
\fB\-AA\fR) turns the OPTOUT flag off for all records\&. This is useful when using the
\fB\-u\fR
option to modify an NSEC3 chain which previously had OPTOUT set\&.
-.RE
-.PP
+ .RE
+ .PP
zonefile
.RS 4
-The file containing the zone to be signed\&.
-.RE
-.PP
+ The file containing the zone to be signed\&.
+ .RE
+ .PP
key
.RS 4
-Specify which keys should be used to sign the zone\&. If no keys are specified, then the zone will be examined for DNSKEY records at the zone apex\&. If these are found and there are matching private keys, in the current directory, then these will be used for signing\&.
-.RE
-.SH "EXAMPLE"
-.PP
+ Specify which keys should be used to sign the zone\&. If no keys are specified, then the zone will be examined for DNSKEY records at the zone apex\&. If these are found and there are matching private keys, in the current directory, then these will be used for signing\&.
+ .RE
+ .SH "EXAMPLE"
+ .PP
The following command signs the
\fBexample\&.com\fR
zone with the DSA key generated by
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
In the above example,
\fBdnssec\-signzone\fR
creates the file
db\&.example\&.com\&.signed\&. This file should be referenced in a zone statement in a
named\&.conf
file\&.
-.PP
+ .PP
This example re\-signs a previously signed zone with default parameters\&. The private keys are assumed to be in the current directory\&.
.sp
.if n \{\
.if n \{\
.RE
.\}
-.SH "SEE ALSO"
-.PP
+.sp
+ .SH "SEE ALSO"
+ .PP
\fBdnssec-keygen\fR(8),
BIND 9 Administrator Reference Manual,
RFC 4033,
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-signzone</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.dnssec-signzone"></a><div class="titlepage"></div>
'\" t
.\" Title: dnssec-verify
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2014-01-15
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
dnssec-verify \- DNSSEC zone verification tool
-.SH "SYNOPSIS"
-.HP \w'\fBdnssec\-verify\fR\ 'u
-\fBdnssec\-verify\fR [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-E\ \fR\fB\fIengine\fR\fR] [\fB\-I\ \fR\fB\fIinput\-format\fR\fR] [\fB\-o\ \fR\fB\fIorigin\fR\fR] [\fB\-v\ \fR\fB\fIlevel\fR\fR] [\fB\-V\fR] [\fB\-x\fR] [\fB\-z\fR] {zonefile}
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBdnssec\-verify\fR\ 'u
+ \fBdnssec\-verify\fR
+ [\fB\-c\ \fR\fB\fIclass\fR\fR]
+ [\fB\-E\ \fR\fB\fIengine\fR\fR]
+ [\fB\-I\ \fR\fB\fIinput\-format\fR\fR]
+ [\fB\-o\ \fR\fB\fIorigin\fR\fR]
+ [\fB\-v\ \fR\fB\fIlevel\fR\fR]
+ [\fB\-V\fR]
+ [\fB\-x\fR]
+ [\fB\-z\fR]
+ {zonefile}
+ .SH "DESCRIPTION"
+ .PP
\fBdnssec\-verify\fR
verifies that a zone is fully signed for each algorithm found in the DNSKEY RRset for the zone, and that the NSEC / NSEC3 chains are complete\&.
-.SH "OPTIONS"
-.PP
+ .SH "OPTIONS"
+ .PP
\-c \fIclass\fR
.RS 4
-Specifies the DNS class of the zone\&.
-.RE
-.PP
+ Specifies the DNS class of the zone\&.
+ .RE
+ .PP
\-E \fIengine\fR
.RS 4
-Specifies the cryptographic hardware to use, when applicable\&.
+ Specifies the cryptographic hardware to use, when applicable\&.
.sp
-When BIND is built with OpenSSL PKCS#11 support, this defaults to the string "pkcs11", which identifies an OpenSSL engine that can drive a cryptographic accelerator or hardware service module\&. When BIND is built with native PKCS#11 cryptography (\-\-enable\-native\-pkcs11), it defaults to the path of the PKCS#11 provider library specified via "\-\-with\-pkcs11"\&.
-.RE
-.PP
+ When BIND is built with OpenSSL PKCS#11 support, this defaults to the string "pkcs11", which identifies an OpenSSL engine that can drive a cryptographic accelerator or hardware service module\&. When BIND is built with native PKCS#11 cryptography (\-\-enable\-native\-pkcs11), it defaults to the path of the PKCS#11 provider library specified via "\-\-with\-pkcs11"\&.
+ .RE
+ .PP
\-I \fIinput\-format\fR
.RS 4
-The format of the input zone file\&. Possible formats are
+ The format of the input zone file\&. Possible formats are
\fB"text"\fR
(default) and
\fB"raw"\fR\&. This option is primarily intended to be used for dynamic signed zones so that the dumped zone file in a non\-text format containing updates can be verified independently\&. The use of this option does not make much sense for non\-dynamic zones\&.
-.RE
-.PP
+ .RE
+ .PP
\-o \fIorigin\fR
.RS 4
-The zone origin\&. If not specified, the name of the zone file is assumed to be the origin\&.
-.RE
-.PP
+ The zone origin\&. If not specified, the name of the zone file is assumed to be the origin\&.
+ .RE
+ .PP
\-v \fIlevel\fR
.RS 4
-Sets the debugging level\&.
-.RE
-.PP
+ Sets the debugging level\&.
+ .RE
+ .PP
\-V
.RS 4
-Prints version information\&.
-.RE
-.PP
+ Prints version information\&.
+ .RE
+ .PP
\-x
.RS 4
-Only verify that the DNSKEY RRset is signed with key\-signing keys\&. Without this flag, it is assumed that the DNSKEY RRset will be signed by all active keys\&. When this flag is set, it will not be an error if the DNSKEY RRset is not signed by zone\-signing keys\&. This corresponds to the
+ Only verify that the DNSKEY RRset is signed with key\-signing keys\&. Without this flag, it is assumed that the DNSKEY RRset will be signed by all active keys\&. When this flag is set, it will not be an error if the DNSKEY RRset is not signed by zone\-signing keys\&. This corresponds to the
\fB\-x\fR
option in
\fBdnssec\-signzone\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-z
.RS 4
-Ignore the KSK flag on the keys when determining whether the zone if correctly signed\&. Without this flag it is assumed that there will be a non\-revoked, self\-signed DNSKEY with the KSK flag set for each algorithm and that RRsets other than DNSKEY RRset will be signed with a different DNSKEY without the KSK flag set\&.
+ Ignore the KSK flag on the keys when determining whether the zone if correctly signed\&. Without this flag it is assumed that there will be a non\-revoked, self\-signed DNSKEY with the KSK flag set for each algorithm and that RRsets other than DNSKEY RRset will be signed with a different DNSKEY without the KSK flag set\&.
.sp
-With this flag set, we only require that for each algorithm, there will be at least one non\-revoked, self\-signed DNSKEY, regardless of the KSK flag state, and that other RRsets will be signed by a non\-revoked key for the same algorithm that includes the self\-signed key; the same key may be used for both purposes\&. This corresponds to the
+ With this flag set, we only require that for each algorithm, there will be at least one non\-revoked, self\-signed DNSKEY, regardless of the KSK flag state, and that other RRsets will be signed by a non\-revoked key for the same algorithm that includes the self\-signed key; the same key may be used for both purposes\&. This corresponds to the
\fB\-z\fR
option in
\fBdnssec\-signzone\fR\&.
-.RE
-.PP
+ .RE
+ .PP
zonefile
.RS 4
-The file containing the zone to be signed\&.
-.RE
-.SH "SEE ALSO"
-.PP
+ The file containing the zone to be signed\&.
+ .RE
+ .SH "SEE ALSO"
+ .PP
\fBdnssec-signzone\fR(8),
BIND 9 Administrator Reference Manual,
RFC 4033\&.
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-verify</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.dnssec-verify"></a><div class="titlepage"></div>
'\" t
.\" Title: lwresd
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2009-01-20
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
lwresd \- lightweight resolver daemon
-.SH "SYNOPSIS"
-.HP \w'\fBlwresd\fR\ 'u
-\fBlwresd\fR [\fB\-c\ \fR\fB\fIconfig\-file\fR\fR] [\fB\-C\ \fR\fB\fIconfig\-file\fR\fR] [\fB\-d\ \fR\fB\fIdebug\-level\fR\fR] [\fB\-f\fR] [\fB\-g\fR] [\fB\-i\ \fR\fB\fIpid\-file\fR\fR] [\fB\-m\ \fR\fB\fIflag\fR\fR] [\fB\-n\ \fR\fB\fI#cpus\fR\fR] [\fB\-P\ \fR\fB\fIport\fR\fR] [\fB\-p\ \fR\fB\fIport\fR\fR] [\fB\-s\fR] [\fB\-t\ \fR\fB\fIdirectory\fR\fR] [\fB\-u\ \fR\fB\fIuser\fR\fR] [\fB\-v\fR] [[\fB\-4\fR] | [\fB\-6\fR]]
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBlwresd\fR\ 'u
+ \fBlwresd\fR
+ [\fB\-c\ \fR\fB\fIconfig\-file\fR\fR]
+ [\fB\-C\ \fR\fB\fIconfig\-file\fR\fR]
+ [\fB\-d\ \fR\fB\fIdebug\-level\fR\fR]
+ [\fB\-f\fR]
+ [\fB\-g\fR]
+ [\fB\-i\ \fR\fB\fIpid\-file\fR\fR]
+ [\fB\-m\ \fR\fB\fIflag\fR\fR]
+ [\fB\-n\ \fR\fB\fI#cpus\fR\fR]
+ [\fB\-P\ \fR\fB\fIport\fR\fR]
+ [\fB\-p\ \fR\fB\fIport\fR\fR]
+ [\fB\-s\fR]
+ [\fB\-t\ \fR\fB\fIdirectory\fR\fR]
+ [\fB\-u\ \fR\fB\fIuser\fR\fR]
+ [\fB\-v\fR]
+ [
+ | [\fB\-4\fR]
+ | [\fB\-6\fR]
+ ]
+ .SH "DESCRIPTION"
+ .PP
\fBlwresd\fR
is the daemon providing name lookup services to clients that use the BIND 9 lightweight resolver library\&. It is essentially a stripped\-down, caching\-only name server that answers queries using the BIND 9 lightweight resolver protocol rather than the DNS protocol\&.
-.PP
+ .PP
\fBlwresd\fR
listens for resolver queries on a UDP port on the IPv4 loopback interface, 127\&.0\&.0\&.1\&. This means that
\fBlwresd\fR
can only be used by processes running on the local machine\&. By default, UDP port number 921 is used for lightweight resolver requests and responses\&.
-.PP
+ .PP
Incoming lightweight resolver requests are decoded by the server which then resolves them using the DNS protocol\&. When the DNS lookup completes,
\fBlwresd\fR
encodes the answers in the lightweight resolver format and returns them to the client that made the request\&.
-.PP
+ .PP
If
/etc/resolv\&.conf
contains any
entries are present, or if forwarding fails,
\fBlwresd\fR
resolves the queries autonomously starting at the root name servers, using a built\-in list of root server hints\&.
-.SH "OPTIONS"
-.PP
+ .SH "OPTIONS"
+ .PP
\-4
.RS 4
-Use IPv4 only even if the host machine is capable of IPv6\&.
+ Use IPv4 only even if the host machine is capable of IPv6\&.
\fB\-4\fR
and
\fB\-6\fR
are mutually exclusive\&.
-.RE
-.PP
+ .RE
+ .PP
\-6
.RS 4
-Use IPv6 only even if the host machine is capable of IPv4\&.
+ Use IPv6 only even if the host machine is capable of IPv4\&.
\fB\-4\fR
and
\fB\-6\fR
are mutually exclusive\&.
-.RE
-.PP
+ .RE
+ .PP
\-c \fIconfig\-file\fR
.RS 4
-Use
+ Use
\fIconfig\-file\fR
as the configuration file instead of the default,
/etc/lwresd\&.conf\&.
\fB\-c\fR
can not be used with
\fB\-C\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-C \fIconfig\-file\fR
.RS 4
-Use
+ Use
\fIconfig\-file\fR
as the configuration file instead of the default,
/etc/resolv\&.conf\&.
\fB\-C\fR
can not be used with
\fB\-c\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-d \fIdebug\-level\fR
.RS 4
-Set the daemon\*(Aqs debug level to
+ Set the daemon\*(Aqs debug level to
\fIdebug\-level\fR\&. Debugging traces from
\fBlwresd\fR
become more verbose as the debug level increases\&.
-.RE
-.PP
+ .RE
+ .PP
\-f
.RS 4
-Run the server in the foreground (i\&.e\&. do not daemonize)\&.
-.RE
-.PP
+ Run the server in the foreground (i\&.e\&. do not daemonize)\&.
+ .RE
+ .PP
\-g
.RS 4
-Run the server in the foreground and force all logging to
+ Run the server in the foreground and force all logging to
stderr\&.
-.RE
-.PP
+ .RE
+ .PP
\-i \fIpid\-file\fR
.RS 4
-Use
+ Use
\fIpid\-file\fR
as the PID file instead of the default,
/var/run/lwresd/lwresd\&.pid\&.
-.RE
-.PP
+ .RE
+ .PP
\-m \fIflag\fR
.RS 4
-Turn on memory usage debugging flags\&. Possible flags are
+ Turn on memory usage debugging flags\&. Possible flags are
\fIusage\fR,
\fItrace\fR,
\fIrecord\fR,
\fIsize\fR, and
\fImctx\fR\&. These correspond to the ISC_MEM_DEBUGXXXX flags described in
<isc/mem\&.h>\&.
-.RE
-.PP
+ .RE
+ .PP
\-n \fI#cpus\fR
.RS 4
-Create
+ Create
\fI#cpus\fR
worker threads to take advantage of multiple CPUs\&. If not specified,
\fBlwresd\fR
will try to determine the number of CPUs present and create one thread per CPU\&. If it is unable to determine the number of CPUs, a single worker thread will be created\&.
-.RE
-.PP
+ .RE
+ .PP
\-P \fIport\fR
.RS 4
-Listen for lightweight resolver queries on port
+ Listen for lightweight resolver queries on port
\fIport\fR\&. If not specified, the default is port 921\&.
-.RE
-.PP
+ .RE
+ .PP
\-p \fIport\fR
.RS 4
-Send DNS lookups to port
+ Send DNS lookups to port
\fIport\fR\&. If not specified, the default is port 53\&. This provides a way of testing the lightweight resolver daemon with a name server that listens for queries on a non\-standard port number\&.
-.RE
-.PP
+ .RE
+ .PP
\-s
.RS 4
-Write memory usage statistics to
+ Write memory usage statistics to
stdout
on exit\&.
-.if n \{\
+ .if n \{\
.sp
.\}
.RS 4
\fBNote\fR
.ps -1
.br
-This option is mainly of interest to BIND 9 developers and may be removed or changed in a future release\&.
-.sp .5v
+ This option is mainly of interest to BIND 9 developers and may be removed or changed in a future release\&.
+ .sp .5v
.RE
-.RE
-.PP
+ .RE
+ .PP
\-t \fIdirectory\fR
.RS 4
-Chroot to
+ Chroot to
\fIdirectory\fR
after processing the command line arguments, but before reading the configuration file\&.
-.if n \{\
+ .if n \{\
.sp
.\}
.RS 4
\fBWarning\fR
.ps -1
.br
-This option should be used in conjunction with the
+ This option should be used in conjunction with the
\fB\-u\fR
option, as chrooting a process running as root doesn\*(Aqt enhance security on most systems; the way
\fBchroot(2)\fR
is defined allows a process with root privileges to escape a chroot jail\&.
-.sp .5v
+ .sp .5v
.RE
-.RE
-.PP
+ .RE
+ .PP
\-u \fIuser\fR
.RS 4
-Setuid to
+ Setuid to
\fIuser\fR
after completing privileged operations, such as creating sockets that listen on privileged ports\&.
-.RE
-.PP
+ .RE
+ .PP
\-v
.RS 4
-Report the version number and exit\&.
-.RE
-.SH "FILES"
-.PP
+ Report the version number and exit\&.
+ .RE
+ .SH "FILES"
+ .PP
/etc/resolv\&.conf
.RS 4
-The default configuration file\&.
-.RE
-.PP
+ The default configuration file\&.
+ .RE
+ .PP
/var/run/lwresd\&.pid
.RS 4
-The default process\-id file\&.
-.RE
-.SH "SEE ALSO"
-.PP
+ The default process\-id file\&.
+ .RE
+ .SH "SEE ALSO"
+ .PP
\fBnamed\fR(8),
\fBlwres\fR(3),
\fBresolver\fR(5)\&.
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>lwresd</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.lwresd"></a><div class="titlepage"></div>
'\" t
.\" Title: named
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2014-02-19
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
named \- Internet domain name server
-.SH "SYNOPSIS"
-.HP \w'\fBnamed\fR\ 'u
-\fBnamed\fR [[\fB\-4\fR] | [\fB\-6\fR]] [\fB\-c\ \fR\fB\fIconfig\-file\fR\fR] [\fB\-d\ \fR\fB\fIdebug\-level\fR\fR] [\fB\-D\ \fR\fB\fIstring\fR\fR] [\fB\-E\ \fR\fB\fIengine\-name\fR\fR] [\fB\-f\fR] [\fB\-g\fR] [\fB\-L\ \fR\fB\fIlogfile\fR\fR] [\fB\-M\ \fR\fB\fIoption\fR\fR] [\fB\-m\ \fR\fB\fIflag\fR\fR] [\fB\-n\ \fR\fB\fI#cpus\fR\fR] [\fB\-p\ \fR\fB\fIport\fR\fR] [\fB\-s\fR] [\fB\-S\ \fR\fB\fI#max\-socks\fR\fR] [\fB\-t\ \fR\fB\fIdirectory\fR\fR] [\fB\-U\ \fR\fB\fI#listeners\fR\fR] [\fB\-u\ \fR\fB\fIuser\fR\fR] [\fB\-v\fR] [\fB\-V\fR] [\fB\-X\ \fR\fB\fIlock\-file\fR\fR] [\fB\-x\ \fR\fB\fIcache\-file\fR\fR]
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBnamed\fR\ 'u
+ \fBnamed\fR
+ [
+ | [\fB\-4\fR]
+ | [\fB\-6\fR]
+ ]
+ [\fB\-c\ \fR\fB\fIconfig\-file\fR\fR]
+ [\fB\-d\ \fR\fB\fIdebug\-level\fR\fR]
+ [\fB\-D\ \fR\fB\fIstring\fR\fR]
+ [\fB\-E\ \fR\fB\fIengine\-name\fR\fR]
+ [\fB\-f\fR]
+ [\fB\-g\fR]
+ [\fB\-L\ \fR\fB\fIlogfile\fR\fR]
+ [\fB\-M\ \fR\fB\fIoption\fR\fR]
+ [\fB\-m\ \fR\fB\fIflag\fR\fR]
+ [\fB\-n\ \fR\fB\fI#cpus\fR\fR]
+ [\fB\-p\ \fR\fB\fIport\fR\fR]
+ [\fB\-s\fR]
+ [\fB\-S\ \fR\fB\fI#max\-socks\fR\fR]
+ [\fB\-t\ \fR\fB\fIdirectory\fR\fR]
+ [\fB\-U\ \fR\fB\fI#listeners\fR\fR]
+ [\fB\-u\ \fR\fB\fIuser\fR\fR]
+ [\fB\-v\fR]
+ [\fB\-V\fR]
+ [\fB\-X\ \fR\fB\fIlock\-file\fR\fR]
+ [\fB\-x\ \fR\fB\fIcache\-file\fR\fR]
+ .SH "DESCRIPTION"
+ .PP
\fBnamed\fR
is a Domain Name System (DNS) server, part of the BIND 9 distribution from ISC\&. For more information on the DNS, see RFCs 1033, 1034, and 1035\&.
-.PP
+ .PP
When invoked without arguments,
\fBnamed\fR
will read the default configuration file
/etc/named\&.conf, read any initial data, and listen for queries\&.
-.SH "OPTIONS"
-.PP
+ .SH "OPTIONS"
+ .PP
\-4
.RS 4
-Use IPv4 only even if the host machine is capable of IPv6\&.
+ Use IPv4 only even if the host machine is capable of IPv6\&.
\fB\-4\fR
and
\fB\-6\fR
are mutually exclusive\&.
-.RE
-.PP
+ .RE
+ .PP
\-6
.RS 4
-Use IPv6 only even if the host machine is capable of IPv4\&.
+ Use IPv6 only even if the host machine is capable of IPv4\&.
\fB\-4\fR
and
\fB\-6\fR
are mutually exclusive\&.
-.RE
-.PP
+ .RE
+ .PP
\-c \fIconfig\-file\fR
.RS 4
-Use
+ Use
\fIconfig\-file\fR
as the configuration file instead of the default,
/etc/named\&.conf\&. To ensure that reloading the configuration file continues to work after the server has changed its working directory due to to a possible
option in the configuration file,
\fIconfig\-file\fR
should be an absolute pathname\&.
-.RE
-.PP
+ .RE
+ .PP
\-d \fIdebug\-level\fR
.RS 4
-Set the daemon\*(Aqs debug level to
+ Set the daemon\*(Aqs debug level to
\fIdebug\-level\fR\&. Debugging traces from
\fBnamed\fR
become more verbose as the debug level increases\&.
-.RE
-.PP
+ .RE
+ .PP
\-D \fIstring\fR
.RS 4
-Specifies a string that is used to identify a instance of
+ Specifies a string that is used to identify a instance of
\fBnamed\fR
in a process listing\&. The contents of
\fIstring\fR
are not examined\&.
-.RE
-.PP
+ .RE
+ .PP
\-E \fIengine\-name\fR
.RS 4
-When applicable, specifies the hardware to use for cryptographic operations, such as a secure key store used for signing\&.
+ When applicable, specifies the hardware to use for cryptographic operations, such as a secure key store used for signing\&.
.sp
-When BIND is built with OpenSSL PKCS#11 support, this defaults to the string "pkcs11", which identifies an OpenSSL engine that can drive a cryptographic accelerator or hardware service module\&. When BIND is built with native PKCS#11 cryptography (\-\-enable\-native\-pkcs11), it defaults to the path of the PKCS#11 provider library specified via "\-\-with\-pkcs11"\&.
-.RE
-.PP
+ When BIND is built with OpenSSL PKCS#11 support, this defaults to the string "pkcs11", which identifies an OpenSSL engine that can drive a cryptographic accelerator or hardware service module\&. When BIND is built with native PKCS#11 cryptography (\-\-enable\-native\-pkcs11), it defaults to the path of the PKCS#11 provider library specified via "\-\-with\-pkcs11"\&.
+ .RE
+ .PP
\-f
.RS 4
-Run the server in the foreground (i\&.e\&. do not daemonize)\&.
-.RE
-.PP
+ Run the server in the foreground (i\&.e\&. do not daemonize)\&.
+ .RE
+ .PP
\-g
.RS 4
-Run the server in the foreground and force all logging to
+ Run the server in the foreground and force all logging to
stderr\&.
-.RE
-.PP
+ .RE
+ .PP
\-L \fIlogfile\fR
.RS 4
-Log to the file
+ Log to the file
\fBlogfile\fR
by default instead of the system log\&.
-.RE
-.PP
+ .RE
+ .PP
\-M \fIoption\fR
.RS 4
-Sets the default memory context options\&. Currently the only supported option is
+ Sets the default memory context options\&. Currently the only supported option is
\fIexternal\fR, which causes the internal memory manager to be bypassed in favor of system\-provided memory allocation functions\&.
-.RE
-.PP
+ .RE
+ .PP
\-m \fIflag\fR
.RS 4
-Turn on memory usage debugging flags\&. Possible flags are
+ Turn on memory usage debugging flags\&. Possible flags are
\fIusage\fR,
\fItrace\fR,
\fIrecord\fR,
\fIsize\fR, and
\fImctx\fR\&. These correspond to the ISC_MEM_DEBUGXXXX flags described in
<isc/mem\&.h>\&.
-.RE
-.PP
+ .RE
+ .PP
\-n \fI#cpus\fR
.RS 4
-Create
+ Create
\fI#cpus\fR
worker threads to take advantage of multiple CPUs\&. If not specified,
\fBnamed\fR
will try to determine the number of CPUs present and create one thread per CPU\&. If it is unable to determine the number of CPUs, a single worker thread will be created\&.
-.RE
-.PP
+ .RE
+ .PP
\-p \fIport\fR
.RS 4
-Listen for queries on port
+ Listen for queries on port
\fIport\fR\&. If not specified, the default is port 53\&.
-.RE
-.PP
+ .RE
+ .PP
\-s
.RS 4
-Write memory usage statistics to
+ Write memory usage statistics to
stdout
on exit\&.
-.if n \{\
+ .if n \{\
.sp
.\}
.RS 4
\fBNote\fR
.ps -1
.br
-This option is mainly of interest to BIND 9 developers and may be removed or changed in a future release\&.
-.sp .5v
-.RE
+ This option is mainly of interest to BIND 9 developers and may be removed or changed in a future release\&.
+ .sp .5v
.RE
-.PP
+ .RE
+ .PP
\-S \fI#max\-socks\fR
.RS 4
-Allow
+ Allow
\fBnamed\fR
to use up to
\fI#max\-socks\fR
sockets\&. The default value is 4096 on systems built with default configuration options, and 21000 on systems built with "configure \-\-with\-tuning=large"\&.
-.if n \{\
+ .if n \{\
.sp
.\}
.RS 4
\fBWarning\fR
.ps -1
.br
-This option should be unnecessary for the vast majority of users\&. The use of this option could even be harmful because the specified value may exceed the limitation of the underlying system API\&. It is therefore set only when the default configuration causes exhaustion of file descriptors and the operational environment is known to support the specified number of sockets\&. Note also that the actual maximum number is normally a little fewer than the specified value because
+ This option should be unnecessary for the vast majority of users\&. The use of this option could even be harmful because the specified value may exceed the limitation of the underlying system API\&. It is therefore set only when the default configuration causes exhaustion of file descriptors and the operational environment is known to support the specified number of sockets\&. Note also that the actual maximum number is normally a little fewer than the specified value because
\fBnamed\fR
reserves some file descriptors for its internal use\&.
-.sp .5v
-.RE
+ .sp .5v
.RE
-.PP
+ .RE
+ .PP
\-t \fIdirectory\fR
.RS 4
-Chroot to
+ Chroot to
\fIdirectory\fR
after processing the command line arguments, but before reading the configuration file\&.
-.if n \{\
+ .if n \{\
.sp
.\}
.RS 4
\fBWarning\fR
.ps -1
.br
-This option should be used in conjunction with the
+ This option should be used in conjunction with the
\fB\-u\fR
option, as chrooting a process running as root doesn\*(Aqt enhance security on most systems; the way
\fBchroot(2)\fR
is defined allows a process with root privileges to escape a chroot jail\&.
-.sp .5v
-.RE
+ .sp .5v
.RE
-.PP
+ .RE
+ .PP
\-U \fI#listeners\fR
.RS 4
-Use
+ Use
\fI#listeners\fR
worker threads to listen for incoming UDP packets on each address\&. If not specified,
\fBnamed\fR
has been set to a higher value than the number of detected CPUs, then
\fB\-U\fR
may be increased as high as that value, but no higher\&. On Windows, the number of UDP listeners is hardwired to 1 and this option has no effect\&.
-.RE
-.PP
+ .RE
+ .PP
\-u \fIuser\fR
.RS 4
-Setuid to
+ Setuid to
\fIuser\fR
after completing privileged operations, such as creating sockets that listen on privileged ports\&.
-.if n \{\
+ .if n \{\
.sp
.\}
.RS 4
\fBNote\fR
.ps -1
.br
-On Linux,
+ On Linux,
\fBnamed\fR
uses the kernel\*(Aqs capability mechanism to drop all root privileges except the ability to
\fBbind(2)\fR
\fBnamed\fR
is run on kernel 2\&.2\&.18 or later, or kernel 2\&.3\&.99\-pre3 or later, since previous kernels did not allow privileges to be retained after
\fBsetuid(2)\fR\&.
-.sp .5v
-.RE
+ .sp .5v
.RE
-.PP
+ .RE
+ .PP
\-v
.RS 4
-Report the version number and exit\&.
-.RE
-.PP
+ Report the version number and exit\&.
+ .RE
+ .PP
\-V
.RS 4
-Report the version number and build options, and exit\&.
-.RE
-.PP
+ Report the version number and build options, and exit\&.
+ .RE
+ .PP
\-X \fIlock\-file\fR
.RS 4
-Acquire a lock on the specified file at runtime; this helps to prevent duplicate
+ Acquire a lock on the specified file at runtime; this helps to prevent duplicate
\fBnamed\fR
instances from running simultaneously\&. Use of this option overrides the
\fBlock\-file\fR
option in
named\&.conf\&. If set to
none, the lock file check is disabled\&.
-.RE
-.PP
+ .RE
+ .PP
\-x \fIcache\-file\fR
.RS 4
-Load data from
+ Load data from
\fIcache\-file\fR
into the cache of the default view\&.
-.if n \{\
+ .if n \{\
.sp
.\}
.RS 4
\fBWarning\fR
.ps -1
.br
-This option must not be used\&. It is only of interest to BIND 9 developers and may be removed or changed in a future release\&.
-.sp .5v
+ This option must not be used\&. It is only of interest to BIND 9 developers and may be removed or changed in a future release\&.
+ .sp .5v
.RE
-.RE
-.SH "SIGNALS"
-.PP
+ .RE
+ .SH "SIGNALS"
+ .PP
In routine operation, signals should not be used to control the nameserver;
\fBrndc\fR
should be used instead\&.
-.PP
+ .PP
SIGHUP
.RS 4
-Force a reload of the server\&.
-.RE
-.PP
+ Force a reload of the server\&.
+ .RE
+ .PP
SIGINT, SIGTERM
.RS 4
-Shut down the server\&.
-.RE
-.PP
+ Shut down the server\&.
+ .RE
+ .PP
The result of sending any other signals to the server is undefined\&.
-.SH "CONFIGURATION"
-.PP
+ .SH "CONFIGURATION"
+ .PP
The
\fBnamed\fR
configuration file is too complex to describe in detail here\&. A complete description is provided in the
BIND 9 Administrator Reference Manual\&.
-.PP
+ .PP
\fBnamed\fR
inherits the
\fBumask\fR
should be set explicitly in the script used to start the
\fBnamed\fR
process\&.
-.SH "FILES"
-.PP
+ .SH "FILES"
+ .PP
/etc/named\&.conf
.RS 4
-The default configuration file\&.
-.RE
-.PP
+ The default configuration file\&.
+ .RE
+ .PP
/var/run/named/named\&.pid
.RS 4
-The default process\-id file\&.
-.RE
-.SH "SEE ALSO"
-.PP
+ The default process\-id file\&.
+ .RE
+ .SH "SEE ALSO"
+ .PP
RFC 1033,
RFC 1034,
RFC 1035,
'\" t
.\" Title: named.conf
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2020-03-12
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
named.conf \- configuration file for \fBnamed\fR
-.SH "SYNOPSIS"
-.HP \w'\fBnamed\&.conf\fR\ 'u
-\fBnamed\&.conf\fR
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBnamed\&.conf\fR\ 'u
+ \fBnamed\&.conf\fR
+ .SH "DESCRIPTION"
+ .PP
named\&.conf
is the configuration file for
\fBnamed\fR\&. Statements are enclosed in braces and terminated with a semi\-colon\&. Clauses in the statements are also semi\-colon terminated\&. The usual comment styles are supported:
-.PP
+ .PP
C style: /* */
-.PP
+ .PP
C++ style: // to end of line
-.PP
+ .PP
Unix style: # to end of line
-.SH "ACL"
+ .SH "ACL"
.sp
.if n \{\
.RS 4
.if n \{\
.RE
.\}
-.SH "CONTROLS"
+.sp
+ .SH "CONTROLS"
.sp
.if n \{\
.RS 4
.if n \{\
.RE
.\}
-.SH "DLZ"
+.sp
+ .SH "DLZ"
.sp
.if n \{\
.RS 4
.if n \{\
.RE
.\}
-.SH "DYNDB"
+.sp
+ .SH "DYNDB"
.sp
.if n \{\
.RS 4
.if n \{\
.RE
.\}
-.SH "KEY"
+.sp
+ .SH "KEY"
.sp
.if n \{\
.RS 4
.if n \{\
.RE
.\}
-.SH "LOGGING"
+.sp
+ .SH "LOGGING"
.sp
.if n \{\
.RS 4
.if n \{\
.RE
.\}
-.SH "LWRES"
+.sp
+ .SH "LWRES"
.sp
.if n \{\
.RS 4
.if n \{\
.RE
.\}
-.SH "MANAGED-KEYS"
+.sp
+ .SH "MANAGED\-KEYS"
.sp
.if n \{\
.RS 4
.if n \{\
.RE
.\}
-.SH "MASTERS"
+.sp
+ .SH "MASTERS"
.sp
.if n \{\
.RS 4
.if n \{\
.RE
.\}
-.SH "OPTIONS"
+.sp
+ .SH "OPTIONS"
.sp
.if n \{\
.RS 4
.if n \{\
.RE
.\}
-.SH "SERVER"
+.sp
+ .SH "SERVER"
.sp
.if n \{\
.RS 4
.if n \{\
.RE
.\}
-.SH "STATISTICS-CHANNELS"
+.sp
+ .SH "STATISTICS\-CHANNELS"
.sp
.if n \{\
.RS 4
.if n \{\
.RE
.\}
-.SH "TRUSTED-KEYS"
+.sp
+ .SH "TRUSTED\-KEYS"
.sp
.if n \{\
.RS 4
.if n \{\
.RE
.\}
-.SH "VIEW"
+.sp
+ .SH "VIEW"
.sp
.if n \{\
.RS 4
.if n \{\
.RE
.\}
-.SH "ZONE"
+.sp
+ .SH "ZONE"
.sp
.if n \{\
.RS 4
.if n \{\
.RE
.\}
-.SH "FILES"
-.PP
+.sp
+ .SH "FILES"
+ .PP
/etc/named\&.conf
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBddns-confgen\fR(8),
\fBnamed\fR(8),
\fBnamed-checkconf\fR(8),
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>named.conf</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.named.conf"></a><div class="titlepage"></div>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>named</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.named"></a><div class="titlepage"></div>
'\" t
.\" Title: nsupdate
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2014-04-18
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
nsupdate \- Dynamic DNS update utility
-.SH "SYNOPSIS"
-.HP \w'\fBnsupdate\fR\ 'u
-\fBnsupdate\fR [\fB\-d\fR] [\fB\-D\fR] [\fB\-i\fR] [\fB\-L\ \fR\fB\fIlevel\fR\fR] [[\fB\-g\fR] | [\fB\-o\fR] | [\fB\-l\fR] | [\fB\-y\ \fR\fB\fI[hmac:]\fR\fIkeyname:secret\fR\fR] | [\fB\-k\ \fR\fB\fIkeyfile\fR\fR]] [\fB\-t\ \fR\fB\fItimeout\fR\fR] [\fB\-u\ \fR\fB\fIudptimeout\fR\fR] [\fB\-r\ \fR\fB\fIudpretries\fR\fR] [\fB\-R\ \fR\fB\fIrandomdev\fR\fR] [\fB\-v\fR] [\fB\-T\fR] [\fB\-P\fR] [\fB\-V\fR] [filename]
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBnsupdate\fR\ 'u
+ \fBnsupdate\fR
+ [\fB\-d\fR]
+ [\fB\-D\fR]
+ [\fB\-i\fR]
+ [\fB\-L\ \fR\fB\fIlevel\fR\fR]
+ [
+ | [\fB\-g\fR]
+ | [\fB\-o\fR]
+ | [\fB\-l\fR]
+ | [\fB\-y\ \fR\fB\fI[hmac:]\fR\fIkeyname:secret\fR\fR]
+ | [\fB\-k\ \fR\fB\fIkeyfile\fR\fR]
+ ]
+ [\fB\-t\ \fR\fB\fItimeout\fR\fR]
+ [\fB\-u\ \fR\fB\fIudptimeout\fR\fR]
+ [\fB\-r\ \fR\fB\fIudpretries\fR\fR]
+ [\fB\-R\ \fR\fB\fIrandomdev\fR\fR]
+ [\fB\-v\fR]
+ [\fB\-T\fR]
+ [\fB\-P\fR]
+ [\fB\-V\fR]
+ [filename]
+ .SH "DESCRIPTION"
+ .PP
\fBnsupdate\fR
is used to submit Dynamic DNS Update requests as defined in RFC 2136 to a name server\&. This allows resource records to be added or removed from a zone without manually editing the zone file\&. A single update request can contain requests to add or remove more than one resource record\&.
-.PP
+ .PP
Zones that are under dynamic control via
\fBnsupdate\fR
or a DHCP server should not be edited by hand\&. Manual edits could conflict with dynamic updates and cause data to be lost\&.
-.PP
+ .PP
The resource records that are dynamically added or removed with
\fBnsupdate\fR
have to be in the same zone\&. Requests are sent to the zone\*(Aqs master server\&. This is identified by the MNAME field of the zone\*(Aqs SOA record\&.
-.PP
+ .PP
Transaction signatures can be used to authenticate the Dynamic DNS updates\&. These use the TSIG resource record type described in RFC 2845 or the SIG(0) record described in RFC 2535 and RFC 2931 or GSS\-TSIG as described in RFC 3645\&.
-.PP
+ .PP
TSIG relies on a shared secret that should only be known to
\fBnsupdate\fR
and the name server\&. For instance, suitable
or
\fB\-k\fR
options to provide the TSIG shared secret\&. These options are mutually exclusive\&.
-.PP
+ .PP
SIG(0) uses public key cryptography\&. To use a SIG(0) key, the public key must be stored in a KEY record in a zone served by the name server\&.
-.PP
+ .PP
GSS\-TSIG uses Kerberos credentials\&. Standard GSS\-TSIG mode is switched on with the
\fB\-g\fR
flag\&. A non\-standards\-compliant variant of GSS\-TSIG used by Windows 2000 can be switched on with the
\fB\-o\fR
flag\&.
-.SH "OPTIONS"
-.PP
+ .SH "OPTIONS"
+ .PP
\-d
.RS 4
-Debug mode\&. This provides tracing information about the update requests that are made and the replies received from the name server\&.
-.RE
-.PP
+ Debug mode\&. This provides tracing information about the update requests that are made and the replies received from the name server\&.
+ .RE
+ .PP
\-D
.RS 4
-Extra debug mode\&.
-.RE
-.PP
+ Extra debug mode\&.
+ .RE
+ .PP
\-i
.RS 4
-Force interactive mode, even when standard input is not a terminal\&.
-.RE
-.PP
+ Force interactive mode, even when standard input is not a terminal\&.
+ .RE
+ .PP
\-k \fIkeyfile\fR
.RS 4
-The file containing the TSIG authentication key\&. Keyfiles may be in two formats: a single file containing a
+ The file containing the TSIG authentication key\&. Keyfiles may be in two formats: a single file containing a
named\&.conf\-format
\fBkey\fR
statement, which may be generated automatically by
\fBdnssec\-keygen\fR\&. The
\fB\-k\fR
may also be used to specify a SIG(0) key used to authenticate Dynamic DNS update requests\&. In this case, the key specified is not an HMAC\-MD5 key\&.
-.RE
-.PP
+ .RE
+ .PP
\-l
.RS 4
-Local\-host only mode\&. This sets the server address to localhost (disabling the
+ Local\-host only mode\&. This sets the server address to localhost (disabling the
\fBserver\fR
so that the server address cannot be overridden)\&. Connections to the local server will use a TSIG key found in
/var/run/named/session\&.key, which is automatically generated by
\fBlocal\fR\&. The location of this key file can be overridden with the
\fB\-k\fR
option\&.
-.RE
-.PP
+ .RE
+ .PP
\-L \fIlevel\fR
.RS 4
-Set the logging debug level\&. If zero, logging is disabled\&.
-.RE
-.PP
+ Set the logging debug level\&. If zero, logging is disabled\&.
+ .RE
+ .PP
\-p \fIport\fR
.RS 4
-Set the port to use for connections to a name server\&. The default is 53\&.
-.RE
-.PP
+ Set the port to use for connections to a name server\&. The default is 53\&.
+ .RE
+ .PP
\-P
.RS 4
-Print the list of private BIND\-specific resource record types whose format is understood by
+ Print the list of private BIND\-specific resource record types whose format is understood by
\fBnsupdate\fR\&. See also the
\fB\-T\fR
option\&.
-.RE
-.PP
+ .RE
+ .PP
\-r \fIudpretries\fR
.RS 4
-The number of UDP retries\&. The default is 3\&. If zero, only one update request will be made\&.
-.RE
-.PP
+ The number of UDP retries\&. The default is 3\&. If zero, only one update request will be made\&.
+ .RE
+ .PP
\-R \fIrandomdev\fR
.RS 4
-Where to obtain randomness\&. If the operating system does not provide a
+ Where to obtain randomness\&. If the operating system does not provide a
/dev/random
or equivalent device, the default source of randomness is keyboard input\&.
randomdev
specifies the name of a character device or file containing random data to be used instead of the default\&. The special value
keyboard
indicates that keyboard input should be used\&. This option may be specified multiple times\&.
-.RE
-.PP
+ .RE
+ .PP
\-t \fItimeout\fR
.RS 4
-The maximum time an update request can take before it is aborted\&. The default is 300 seconds\&. Zero can be used to disable the timeout\&.
-.RE
-.PP
+ The maximum time an update request can take before it is aborted\&. The default is 300 seconds\&. Zero can be used to disable the timeout\&.
+ .RE
+ .PP
\-T
.RS 4
-Print the list of IANA standard resource record types whose format is understood by
+ Print the list of IANA standard resource record types whose format is understood by
\fBnsupdate\fR\&.
\fBnsupdate\fR
will exit after the lists are printed\&. The
\fB\-P\fR
option\&.
.sp
-Other types can be entered using "TYPEXXXXX" where "XXXXX" is the decimal value of the type with no leading zeros\&. The rdata, if present, will be parsed using the UNKNOWN rdata format, (<backslash> <hash> <space> <length> <space> <hexstring>)\&.
-.RE
-.PP
+ Other types can be entered using "TYPEXXXXX" where "XXXXX" is the decimal value of the type with no leading zeros\&. The rdata, if present, will be parsed using the UNKNOWN rdata format, (<backslash> <hash> <space> <length> <space> <hexstring>)\&.
+ .RE
+ .PP
\-u \fIudptimeout\fR
.RS 4
-The UDP retry interval\&. The default is 3 seconds\&. If zero, the interval will be computed from the timeout interval and number of UDP retries\&.
-.RE
-.PP
+ The UDP retry interval\&. The default is 3 seconds\&. If zero, the interval will be computed from the timeout interval and number of UDP retries\&.
+ .RE
+ .PP
\-v
.RS 4
-Use TCP even for small update requests\&. By default,
+ Use TCP even for small update requests\&. By default,
\fBnsupdate\fR
uses UDP to send update requests to the name server unless they are too large to fit in a UDP request in which case TCP will be used\&. TCP may be preferable when a batch of update requests is made\&.
-.RE
-.PP
+ .RE
+ .PP
\-V
.RS 4
-Print the version number and exit\&.
-.RE
-.PP
+ Print the version number and exit\&.
+ .RE
+ .PP
\-y \fI[hmac:]\fR\fIkeyname:secret\fR
.RS 4
-Literal TSIG authentication key\&.
+ Literal TSIG authentication key\&.
\fIkeyname\fR
is the name of the key, and
\fIsecret\fR
or if MD5 was disabled
hmac\-sha256\&.
.sp
-NOTE: Use of the
+ NOTE: Use of the
\fB\-y\fR
option is discouraged because the shared secret is supplied as a command line argument in clear text\&. This may be visible in the output from
\fBps\fR(1)
or in a history file maintained by the user\*(Aqs shell\&.
-.RE
-.SH "INPUT FORMAT"
-.PP
+ .RE
+ .SH "INPUT FORMAT"
+ .PP
\fBnsupdate\fR
reads input from
\fIfilename\fR
or standard input\&. Each command is supplied on exactly one line of input\&. Some commands are for administrative purposes\&. The others are either update instructions or prerequisite checks on the contents of the zone\&. These checks set conditions that some name or set of resource records (RRset) either exists or is absent from the zone\&. These conditions must be met if the entire update request is to succeed\&. Updates will be rejected if the tests for the prerequisite conditions fail\&.
-.PP
+ .PP
Every update request consists of zero or more prerequisites and zero or more updates\&. This allows a suitably authenticated update request to proceed if some specified resource records are present or missing from the zone\&. A blank input line (or the
\fBsend\fR
command) causes the accumulated commands to be sent as one Dynamic DNS update request to the name server\&.
-.PP
+ .PP
The command formats and their meaning are as follows:
-.PP
+ .PP
\fBserver\fR {servername} [port]
.RS 4
-Sends all dynamic update requests to the name server
+ Sends all dynamic update requests to the name server
\fIservername\fR\&. When no server statement is provided,
\fBnsupdate\fR
will send updates to the master server of the correct zone\&. The MNAME field of that zone\*(Aqs SOA record will identify the master server for that zone\&.
is the port number on
\fIservername\fR
where the dynamic update requests get sent\&. If no port number is specified, the default DNS port number of 53 is used\&.
-.RE
-.PP
+ .RE
+ .PP
\fBlocal\fR {address} [port]
.RS 4
-Sends all dynamic update requests using the local
+ Sends all dynamic update requests using the local
\fIaddress\fR\&. When no local statement is provided,
\fBnsupdate\fR
will send updates using an address and port chosen by the system\&.
\fIport\fR
can additionally be used to make requests come from a specific port\&. If no port number is specified, the system will assign one\&.
-.RE
-.PP
+ .RE
+ .PP
\fBzone\fR {zonename}
.RS 4
-Specifies that all updates are to be made to the zone
+ Specifies that all updates are to be made to the zone
\fIzonename\fR\&. If no
\fIzone\fR
statement is provided,
\fBnsupdate\fR
will attempt determine the correct zone to update based on the rest of the input\&.
-.RE
-.PP
+ .RE
+ .PP
\fBclass\fR {classname}
.RS 4
-Specify the default class\&. If no
+ Specify the default class\&. If no
\fIclass\fR
is specified, the default class is
\fIIN\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\fBttl\fR {seconds}
.RS 4
-Specify the default time to live for records to be added\&. The value
+ Specify the default time to live for records to be added\&. The value
\fInone\fR
will clear the default ttl\&.
-.RE
-.PP
+ .RE
+ .PP
\fBkey\fR [hmac:] {keyname} {secret}
.RS 4
-Specifies that all updates are to be TSIG\-signed using the
-\fIkeyname\fR\fIsecret\fR
+ Specifies that all updates are to be TSIG\-signed using the
+\fIkeyname\fR
+\fIsecret\fR
pair\&. If
\fIhmac\fR
is specified, then it sets the signing algorithm in use; the default is
\fB\-y\fR
or
\fB\-k\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\fBgsstsig\fR
.RS 4
-Use GSS\-TSIG to sign the updated\&. This is equivalent to specifying
+ Use GSS\-TSIG to sign the updated\&. This is equivalent to specifying
\fB\-g\fR
on the command line\&.
-.RE
-.PP
+ .RE
+ .PP
\fBoldgsstsig\fR
.RS 4
-Use the Windows 2000 version of GSS\-TSIG to sign the updated\&. This is equivalent to specifying
+ Use the Windows 2000 version of GSS\-TSIG to sign the updated\&. This is equivalent to specifying
\fB\-o\fR
on the command line\&.
-.RE
-.PP
+ .RE
+ .PP
\fBrealm\fR {[realm_name]}
.RS 4
-When using GSS\-TSIG use
+ When using GSS\-TSIG use
\fIrealm_name\fR
rather than the default realm in
krb5\&.conf\&. If no realm is specified the saved realm is cleared\&.
-.RE
-.PP
+ .RE
+ .PP
\fBcheck\-names\fR {[yes_or_no]}
.RS 4
-Turn on or off check\-names processing on records to be added\&. Check\-names has no effect on prerequisites or records to be deleted\&. By default check\-names processing is on\&. If check\-names processing fails the record will not be added to the UPDATE message\&.
-.RE
-.PP
+ Turn on or off check\-names processing on records to be added\&. Check\-names has no effect on prerequisites or records to be deleted\&. By default check\-names processing is on\&. If check\-names processing fails the record will not be added to the UPDATE message\&.
+ .RE
+ .PP
\fB[prereq]\fR\fB nxdomain\fR {domain\-name}
.RS 4
-Requires that no resource record of any type exists with name
+ Requires that no resource record of any type exists with name
\fIdomain\-name\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\fB[prereq]\fR\fB yxdomain\fR {domain\-name}
.RS 4
-Requires that
+ Requires that
\fIdomain\-name\fR
exists (has as at least one resource record, of any type)\&.
-.RE
-.PP
+ .RE
+ .PP
\fB[prereq]\fR\fB nxrrset\fR {domain\-name} [class] {type}
.RS 4
-Requires that no resource record exists of the specified
+ Requires that no resource record exists of the specified
\fItype\fR,
\fIclass\fR
and
\fIdomain\-name\fR\&. If
\fIclass\fR
is omitted, IN (internet) is assumed\&.
-.RE
-.PP
+ .RE
+ .PP
\fB[prereq]\fR\fB yxrrset\fR {domain\-name} [class] {type}
.RS 4
-This requires that a resource record of the specified
+ This requires that a resource record of the specified
\fItype\fR,
\fIclass\fR
and
must exist\&. If
\fIclass\fR
is omitted, IN (internet) is assumed\&.
-.RE
-.PP
+ .RE
+ .PP
\fB[prereq]\fR\fB yxrrset\fR {domain\-name} [class] {type} {data...}
.RS 4
-The
+ The
\fIdata\fR
from each set of prerequisites of this form sharing a common
\fItype\fR,
\fIdomain\-name\fR\&. The
\fIdata\fR
are written in the standard text representation of the resource record\*(Aqs RDATA\&.
-.RE
-.PP
+ .RE
+ .PP
\fB[update]\fR\fB del\fR\fB[ete]\fR {domain\-name} [ttl] [class] [type\ [data...]]
.RS 4
-Deletes any resource records named
+ Deletes any resource records named
\fIdomain\-name\fR\&. If
\fItype\fR
and
is not supplied\&. The
\fIttl\fR
is ignored, and is only allowed for compatibility\&.
-.RE
-.PP
+ .RE
+ .PP
\fB[update]\fR\fB add\fR {domain\-name} {ttl} [class] {type} {data...}
.RS 4
-Adds a new resource record with the specified
+ Adds a new resource record with the specified
\fIttl\fR,
\fIclass\fR
and
\fIdata\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\fBshow\fR
.RS 4
-Displays the current message, containing all of the prerequisites and updates specified since the last send\&.
-.RE
-.PP
+ Displays the current message, containing all of the prerequisites and updates specified since the last send\&.
+ .RE
+ .PP
\fBsend\fR
.RS 4
-Sends the current message\&. This is equivalent to entering a blank line\&.
-.RE
-.PP
+ Sends the current message\&. This is equivalent to entering a blank line\&.
+ .RE
+ .PP
\fBanswer\fR
.RS 4
-Displays the answer\&.
-.RE
-.PP
+ Displays the answer\&.
+ .RE
+ .PP
\fBdebug\fR
.RS 4
-Turn on debugging\&.
-.RE
-.PP
+ Turn on debugging\&.
+ .RE
+ .PP
\fBversion\fR
.RS 4
-Print version number\&.
-.RE
-.PP
+ Print version number\&.
+ .RE
+ .PP
\fBhelp\fR
.RS 4
-Print a list of commands\&.
-.RE
-.PP
+ Print a list of commands\&.
+ .RE
+ .PP
Lines beginning with a semicolon are comments and are ignored\&.
-.SH "EXAMPLES"
-.PP
+ .SH "EXAMPLES"
+ .PP
The examples below show how
\fBnsupdate\fR
could be used to insert and delete resource records from the
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
Any A records for
\fBoldhost\&.example\&.com\fR
are deleted\&. And an A record for
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
The prerequisite condition gets the name server to check that there are no resource records of any type for
\fBnickname\&.example\&.com\fR\&. If there are, the update request fails\&. If this name does not exist, a CNAME for it is added\&. This ensures that when the CNAME is added, it cannot conflict with the long\-standing rule in RFC 1034 that a name must not exist as any other record type if it exists as a CNAME\&. (The rule has been updated for DNSSEC in RFC 2535 to allow CNAMEs to have RRSIG, DNSKEY and NSEC records\&.)
-.SH "FILES"
-.PP
+ .SH "FILES"
+ .PP
\fB/etc/resolv\&.conf\fR
.RS 4
-used to identify default name server
-.RE
-.PP
+ used to identify default name server
+ .RE
+ .PP
\fB/var/run/named/session\&.key\fR
.RS 4
-sets the default TSIG key for use in local\-only mode
-.RE
-.PP
+ sets the default TSIG key for use in local\-only mode
+ .RE
+ .PP
\fBK{name}\&.+157\&.+{random}\&.key\fR
.RS 4
-base\-64 encoding of HMAC\-MD5 key created by
+ base\-64 encoding of HMAC\-MD5 key created by
\fBdnssec-keygen\fR(8)\&.
-.RE
-.PP
+ .RE
+ .PP
\fBK{name}\&.+157\&.+{random}\&.private\fR
.RS 4
-base\-64 encoding of HMAC\-MD5 key created by
+ base\-64 encoding of HMAC\-MD5 key created by
\fBdnssec-keygen\fR(8)\&.
-.RE
-.SH "SEE ALSO"
-.PP
+ .RE
+ .SH "SEE ALSO"
+ .PP
RFC 2136,
RFC 3007,
RFC 2104,
\fBnamed\fR(8),
\fBddns-confgen\fR(8),
\fBdnssec-keygen\fR(8)\&.
-.SH "BUGS"
-.PP
+ .SH "BUGS"
+ .PP
The TSIG key is redundantly stored in two separate files\&. This is a consequence of nsupdate using the DST library for its cryptographic operations, and may change in future releases\&.
.SH "AUTHOR"
.PP
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>nsupdate</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.nsupdate"></a><div class="titlepage"></div>
'\" t
.\" Title: pkcs11-destroy
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2014-01-15
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
pkcs11-destroy \- destroy PKCS#11 objects
-.SH "SYNOPSIS"
-.HP \w'\fBpkcs11\-destroy\fR\ 'u
-\fBpkcs11\-destroy\fR [\fB\-m\ \fR\fB\fImodule\fR\fR] [\fB\-s\ \fR\fB\fIslot\fR\fR] {\-i\ \fIID\fR | \-l\ \fIlabel\fR} [\fB\-p\ \fR\fB\fIPIN\fR\fR] [\fB\-w\ \fR\fB\fIseconds\fR\fR]
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBpkcs11\-destroy\fR\ 'u
+ \fBpkcs11\-destroy\fR
+ [\fB\-m\ \fR\fB\fImodule\fR\fR]
+ [\fB\-s\ \fR\fB\fIslot\fR\fR]
+ {
+ | \-i\ \fIID\fR
+ | \-l\ \fIlabel\fR
+ }
+ [\fB\-p\ \fR\fB\fIPIN\fR\fR]
+ [\fB\-w\ \fR\fB\fIseconds\fR\fR]
+ .SH "DESCRIPTION"
+ .PP
\fBpkcs11\-destroy\fR
destroys keys stored in a PKCS#11 device, identified by their
\fBID\fR
or
\fBlabel\fR\&.
-.PP
+ .PP
Matching keys are displayed before being destroyed\&. By default, there is a five second delay to allow the user to interrupt the process before the destruction takes place\&.
-.SH "ARGUMENTS"
-.PP
+ .SH "ARGUMENTS"
+ .PP
\-m \fImodule\fR
.RS 4
-Specify the PKCS#11 provider module\&. This must be the full path to a shared library object implementing the PKCS#11 API for the device\&.
-.RE
-.PP
+ Specify the PKCS#11 provider module\&. This must be the full path to a shared library object implementing the PKCS#11 API for the device\&.
+ .RE
+ .PP
\-s \fIslot\fR
.RS 4
-Open the session with the given PKCS#11 slot\&. The default is slot 0\&.
-.RE
-.PP
+ Open the session with the given PKCS#11 slot\&. The default is slot 0\&.
+ .RE
+ .PP
\-i \fIID\fR
.RS 4
-Destroy keys with the given object ID\&.
-.RE
-.PP
+ Destroy keys with the given object ID\&.
+ .RE
+ .PP
\-l \fIlabel\fR
.RS 4
-Destroy keys with the given label\&.
-.RE
-.PP
+ Destroy keys with the given label\&.
+ .RE
+ .PP
\-p \fIPIN\fR
.RS 4
-Specify the PIN for the device\&. If no PIN is provided on the command line,
+ Specify the PIN for the device\&. If no PIN is provided on the command line,
\fBpkcs11\-destroy\fR
will prompt for it\&.
-.RE
-.PP
+ .RE
+ .PP
\-w \fIseconds\fR
.RS 4
-Specify how long to pause before carrying out key destruction\&. The default is five seconds\&. If set to
+ Specify how long to pause before carrying out key destruction\&. The default is five seconds\&. If set to
0, destruction will be immediate\&.
-.RE
-.SH "SEE ALSO"
-.PP
+ .RE
+ .SH "SEE ALSO"
+ .PP
\fBpkcs11-keygen\fR(8),
\fBpkcs11-list\fR(8),
\fBpkcs11-tokens\fR(8)
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>pkcs11-destroy</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.pkcs11-destroy"></a><div class="titlepage"></div>
'\" t
.\" Title: pkcs11-keygen
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2014-01-15
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
pkcs11-keygen \- generate keys on a PKCS#11 device
-.SH "SYNOPSIS"
-.HP \w'\fBpkcs11\-keygen\fR\ 'u
-\fBpkcs11\-keygen\fR {\-a\ \fIalgorithm\fR} [\fB\-b\ \fR\fB\fIkeysize\fR\fR] [\fB\-e\fR] [\fB\-i\ \fR\fB\fIid\fR\fR] [\fB\-m\ \fR\fB\fImodule\fR\fR] [\fB\-P\fR] [\fB\-p\ \fR\fB\fIPIN\fR\fR] [\fB\-q\fR] [\fB\-S\fR] [\fB\-s\ \fR\fB\fIslot\fR\fR] {label}
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBpkcs11\-keygen\fR\ 'u
+ \fBpkcs11\-keygen\fR
+ {\-a\ \fIalgorithm\fR}
+ [\fB\-b\ \fR\fB\fIkeysize\fR\fR]
+ [\fB\-e\fR]
+ [\fB\-i\ \fR\fB\fIid\fR\fR]
+ [\fB\-m\ \fR\fB\fImodule\fR\fR]
+ [\fB\-P\fR]
+ [\fB\-p\ \fR\fB\fIPIN\fR\fR]
+ [\fB\-q\fR]
+ [\fB\-S\fR]
+ [\fB\-s\ \fR\fB\fIslot\fR\fR]
+ {label}
+ .SH "DESCRIPTION"
+ .PP
\fBpkcs11\-keygen\fR
causes a PKCS#11 device to generate a new key pair with the given
\fBlabel\fR
(which must be unique) and with
\fBkeysize\fR
bits of prime\&.
-.SH "ARGUMENTS"
-.PP
+ .SH "ARGUMENTS"
+ .PP
\-a \fIalgorithm\fR
.RS 4
-Specify the key algorithm class: Supported classes are RSA, DSA, DH, ECC and ECX\&. In addition to these strings, the
+ Specify the key algorithm class: Supported classes are RSA, DSA, DH, ECC and ECX\&. In addition to these strings, the
\fBalgorithm\fR
can be specified as a DNSSEC signing algorithm that will be used with this key; for example, NSEC3RSASHA1 maps to RSA, ECDSAP256SHA256 maps to ECC, and ED25519 to ECX\&. The default class is "RSA"\&.
-.RE
-.PP
+ .RE
+ .PP
\-b \fIkeysize\fR
.RS 4
-Create the key pair with
+ Create the key pair with
\fBkeysize\fR
bits of prime\&. For ECC keys, the only valid values are 256 and 384, and the default is 256\&. For ECX kyes, the only valid values are 256 and 456, and the default is 256\&.
-.RE
-.PP
+ .RE
+ .PP
\-e
.RS 4
-For RSA keys only, use a large exponent\&.
-.RE
-.PP
+ For RSA keys only, use a large exponent\&.
+ .RE
+ .PP
\-i \fIid\fR
.RS 4
-Create key objects with id\&. The id is either an unsigned short 2 byte or an unsigned long 4 byte number\&.
-.RE
-.PP
+ Create key objects with id\&. The id is either an unsigned short 2 byte or an unsigned long 4 byte number\&.
+ .RE
+ .PP
\-m \fImodule\fR
.RS 4
-Specify the PKCS#11 provider module\&. This must be the full path to a shared library object implementing the PKCS#11 API for the device\&.
-.RE
-.PP
+ Specify the PKCS#11 provider module\&. This must be the full path to a shared library object implementing the PKCS#11 API for the device\&.
+ .RE
+ .PP
\-P
.RS 4
-Set the new private key to be non\-sensitive and extractable\&. The allows the private key data to be read from the PKCS#11 device\&. The default is for private keys to be sensitive and non\-extractable\&.
-.RE
-.PP
+ Set the new private key to be non\-sensitive and extractable\&. The allows the private key data to be read from the PKCS#11 device\&. The default is for private keys to be sensitive and non\-extractable\&.
+ .RE
+ .PP
\-p \fIPIN\fR
.RS 4
-Specify the PIN for the device\&. If no PIN is provided on the command line,
+ Specify the PIN for the device\&. If no PIN is provided on the command line,
\fBpkcs11\-keygen\fR
will prompt for it\&.
-.RE
-.PP
+ .RE
+ .PP
\-q
.RS 4
-Quiet mode: suppress unnecessary output\&.
-.RE
-.PP
+ Quiet mode: suppress unnecessary output\&.
+ .RE
+ .PP
\-S
.RS 4
-For Diffie\-Hellman (DH) keys only, use a special prime of 768, 1024 or 1536 bit size and base (aka generator) 2\&. If not specified, bit size will default to 1024\&.
-.RE
-.PP
+ For Diffie\-Hellman (DH) keys only, use a special prime of 768, 1024 or 1536 bit size and base (aka generator) 2\&. If not specified, bit size will default to 1024\&.
+ .RE
+ .PP
\-s \fIslot\fR
.RS 4
-Open the session with the given PKCS#11 slot\&. The default is slot 0\&.
-.RE
-.SH "SEE ALSO"
-.PP
+ Open the session with the given PKCS#11 slot\&. The default is slot 0\&.
+ .RE
+ .SH "SEE ALSO"
+ .PP
\fBpkcs11-destroy\fR(8),
\fBpkcs11-list\fR(8),
\fBpkcs11-tokens\fR(8),
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>pkcs11-keygen</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.pkcs11-keygen"></a><div class="titlepage"></div>
'\" t
.\" Title: pkcs11-list
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2009-10-05
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
pkcs11-list \- list PKCS#11 objects
-.SH "SYNOPSIS"
-.HP \w'\fBpkcs11\-list\fR\ 'u
-\fBpkcs11\-list\fR [\fB\-P\fR] [\fB\-m\ \fR\fB\fImodule\fR\fR] [\fB\-s\ \fR\fB\fIslot\fR\fR] [\-i\ \fIID\fR] [\-l\ \fIlabel\fR] [\fB\-p\ \fR\fB\fIPIN\fR\fR]
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBpkcs11\-list\fR\ 'u
+ \fBpkcs11\-list\fR
+ [\fB\-P\fR]
+ [\fB\-m\ \fR\fB\fImodule\fR\fR]
+ [\fB\-s\ \fR\fB\fIslot\fR\fR]
+ [\-i\ \fIID\fR]
+ [\-l\ \fIlabel\fR]
+ [\fB\-p\ \fR\fB\fIPIN\fR\fR]
+ .SH "DESCRIPTION"
+ .PP
\fBpkcs11\-list\fR
lists the PKCS#11 objects with
\fBID\fR
true,
false, or
never\&.
-.SH "ARGUMENTS"
-.PP
+ .SH "ARGUMENTS"
+ .PP
\-P
.RS 4
-List only the public objects\&. (Note that on some PKCS#11 devices, all objects are private\&.)
-.RE
-.PP
+ List only the public objects\&. (Note that on some PKCS#11 devices, all objects are private\&.)
+ .RE
+ .PP
\-m \fImodule\fR
.RS 4
-Specify the PKCS#11 provider module\&. This must be the full path to a shared library object implementing the PKCS#11 API for the device\&.
-.RE
-.PP
+ Specify the PKCS#11 provider module\&. This must be the full path to a shared library object implementing the PKCS#11 API for the device\&.
+ .RE
+ .PP
\-s \fIslot\fR
.RS 4
-Open the session with the given PKCS#11 slot\&. The default is slot 0\&.
-.RE
-.PP
+ Open the session with the given PKCS#11 slot\&. The default is slot 0\&.
+ .RE
+ .PP
\-i \fIID\fR
.RS 4
-List only key objects with the given object ID\&.
-.RE
-.PP
+ List only key objects with the given object ID\&.
+ .RE
+ .PP
\-l \fIlabel\fR
.RS 4
-List only key objects with the given label\&.
-.RE
-.PP
+ List only key objects with the given label\&.
+ .RE
+ .PP
\-p \fIPIN\fR
.RS 4
-Specify the PIN for the device\&. If no PIN is provided on the command line,
+ Specify the PIN for the device\&. If no PIN is provided on the command line,
\fBpkcs11\-list\fR
will prompt for it\&.
-.RE
-.SH "SEE ALSO"
-.PP
+ .RE
+ .SH "SEE ALSO"
+ .PP
\fBpkcs11-destroy\fR(8),
\fBpkcs11-keygen\fR(8),
\fBpkcs11-tokens\fR(8)
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>pkcs11-list</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.pkcs11-list"></a><div class="titlepage"></div>
'\" t
.\" Title: pkcs11-tokens
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2014-01-15
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
pkcs11-tokens \- list PKCS#11 available tokens
-.SH "SYNOPSIS"
-.HP \w'\fBpkcs11\-tokens\fR\ 'u
-\fBpkcs11\-tokens\fR [\fB\-m\ \fR\fB\fImodule\fR\fR] [\fB\-v\fR]
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBpkcs11\-tokens\fR\ 'u
+ \fBpkcs11\-tokens\fR
+ [\fB\-m\ \fR\fB\fImodule\fR\fR]
+ [\fB\-v\fR]
+ .SH "DESCRIPTION"
+ .PP
\fBpkcs11\-tokens\fR
lists the PKCS#11 available tokens with defaults from the slot/token scan performed at application initialization\&.
-.SH "ARGUMENTS"
-.PP
+ .SH "ARGUMENTS"
+ .PP
\-m \fImodule\fR
.RS 4
-Specify the PKCS#11 provider module\&. This must be the full path to a shared library object implementing the PKCS#11 API for the device\&.
-.RE
-.PP
+ Specify the PKCS#11 provider module\&. This must be the full path to a shared library object implementing the PKCS#11 API for the device\&.
+ .RE
+ .PP
\-v
.RS 4
-Make the PKCS#11 libisc initialization verbose\&.
-.RE
-.SH "SEE ALSO"
-.PP
+ Make the PKCS#11 libisc initialization verbose\&.
+ .RE
+ .SH "SEE ALSO"
+ .PP
\fBpkcs11-destroy\fR(8),
\fBpkcs11-keygen\fR(8),
\fBpkcs11-list\fR(8)
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>pkcs11-tokens</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.pkcs11-tokens"></a><div class="titlepage"></div>
'\" t
.\" Title: dnssec-checkds
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2013-01-01
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
dnssec-checkds \- DNSSEC delegation consistency checking tool
-.SH "SYNOPSIS"
-.HP \w'\fBdnssec\-checkds\fR\ 'u
-\fBdnssec\-checkds\fR [\fB\-l\ \fR\fB\fIdomain\fR\fR] [\fB\-f\ \fR\fB\fIfile\fR\fR] [\fB\-d\ \fR\fB\fIdig\ path\fR\fR] [\fB\-D\ \fR\fB\fIdsfromkey\ path\fR\fR] {zone}
-.HP \w'\fBdnssec\-dsfromkey\fR\ 'u
-\fBdnssec\-dsfromkey\fR [\fB\-l\ \fR\fB\fIdomain\fR\fR] [\fB\-f\ \fR\fB\fIfile\fR\fR] [\fB\-d\ \fR\fB\fIdig\ path\fR\fR] [\fB\-D\ \fR\fB\fIdsfromkey\ path\fR\fR] {zone}
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBdnssec\-checkds\fR\ 'u
+ \fBdnssec\-checkds\fR
+ [\fB\-l\ \fR\fB\fIdomain\fR\fR]
+ [\fB\-f\ \fR\fB\fIfile\fR\fR]
+ [\fB\-d\ \fR\fB\fIdig\ path\fR\fR]
+ [\fB\-D\ \fR\fB\fIdsfromkey\ path\fR\fR]
+ {zone}
+ .HP \w'\fBdnssec\-dsfromkey\fR\ 'u
+ \fBdnssec\-dsfromkey\fR
+ [\fB\-l\ \fR\fB\fIdomain\fR\fR]
+ [\fB\-f\ \fR\fB\fIfile\fR\fR]
+ [\fB\-d\ \fR\fB\fIdig\ path\fR\fR]
+ [\fB\-D\ \fR\fB\fIdsfromkey\ path\fR\fR]
+ {zone}
+ .SH "DESCRIPTION"
+ .PP
\fBdnssec\-checkds\fR
verifies the correctness of Delegation Signer (DS) or DNSSEC Lookaside Validation (DLV) resource records for keys in a specified zone\&.
-.SH "OPTIONS"
-.PP
+ .SH "OPTIONS"
+ .PP
\-f \fIfile\fR
.RS 4
-If a
+ If a
\fBfile\fR
is specified, then the zone is read from that file to find the DNSKEY records\&. If not, then the DNSKEY records for the zone are looked up in the DNS\&.
-.RE
-.PP
+ .RE
+ .PP
\-l \fIdomain\fR
.RS 4
-Check for a DLV record in the specified lookaside domain, instead of checking for a DS record in the zone\*(Aqs parent\&.
-.RE
-.PP
+ Check for a DLV record in the specified lookaside domain, instead of checking for a DS record in the zone\*(Aqs parent\&.
+ .RE
+ .PP
\-d \fIdig path\fR
.RS 4
-Specifies a path to a
+ Specifies a path to a
\fBdig\fR
binary\&. Used for testing\&.
-.RE
-.PP
+ .RE
+ .PP
\-D \fIdsfromkey path\fR
.RS 4
-Specifies a path to a
+ Specifies a path to a
\fBdnssec\-dsfromkey\fR
binary\&. Used for testing\&.
-.RE
-.SH "SEE ALSO"
-.PP
+ .RE
+ .SH "SEE ALSO"
+ .PP
\fBdnssec-dsfromkey\fR(8),
\fBdnssec-keygen\fR(8),
\fBdnssec-signzone\fR(8),
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-checkds</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.dnssec-checkds"></a><div class="titlepage"></div>
'\" t
.\" Title: dnssec-coverage
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2014-01-11
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
dnssec-coverage \- checks future DNSKEY coverage for a zone
-.SH "SYNOPSIS"
-.HP \w'\fBdnssec\-coverage\fR\ 'u
-\fBdnssec\-coverage\fR [\fB\-K\ \fR\fB\fIdirectory\fR\fR] [\fB\-l\ \fR\fB\fIlength\fR\fR] [\fB\-f\ \fR\fB\fIfile\fR\fR] [\fB\-d\ \fR\fB\fIDNSKEY\ TTL\fR\fR] [\fB\-m\ \fR\fB\fImax\ TTL\fR\fR] [\fB\-r\ \fR\fB\fIinterval\fR\fR] [\fB\-c\ \fR\fB\fIcompilezone\ path\fR\fR] [\fB\-k\fR] [\fB\-z\fR] [zone...]
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBdnssec\-coverage\fR\ 'u
+ \fBdnssec\-coverage\fR
+ [\fB\-K\ \fR\fB\fIdirectory\fR\fR]
+ [\fB\-l\ \fR\fB\fIlength\fR\fR]
+ [\fB\-f\ \fR\fB\fIfile\fR\fR]
+ [\fB\-d\ \fR\fB\fIDNSKEY\ TTL\fR\fR]
+ [\fB\-m\ \fR\fB\fImax\ TTL\fR\fR]
+ [\fB\-r\ \fR\fB\fIinterval\fR\fR]
+ [\fB\-c\ \fR\fB\fIcompilezone\ path\fR\fR]
+ [\fB\-k\fR]
+ [\fB\-z\fR]
+ [zone...]
+ .SH "DESCRIPTION"
+ .PP
\fBdnssec\-coverage\fR
verifies that the DNSSEC keys for a given zone or a set of zones have timing metadata set properly to ensure no future lapses in DNSSEC coverage\&.
-.PP
+ .PP
If
\fBzone\fR
is specified, then keys found in the key repository matching that zone are scanned, and an ordered list is generated of the events scheduled for that key (i\&.e\&., publication, activation, inactivation, deletion)\&. The list of events is walked in order of occurrence\&. Warnings are generated if any event is scheduled which could cause the zone to enter a state in which validation failures might occur: for example, if the number of published or active keys for a given algorithm drops to zero, or if a key is deleted from the zone too soon after a new key is rolled, and cached data signed by the prior key has not had time to expire from resolver caches\&.
-.PP
+ .PP
If
\fBzone\fR
is not specified, then all keys in the key repository will be scanned, and all zones for which there are keys will be analyzed\&. (Note: This method of reporting is only accurate if all the zones that have keys in a given repository share the same TTL parameters\&.)
-.SH "OPTIONS"
-.PP
+ .SH "OPTIONS"
+ .PP
\-K \fIdirectory\fR
.RS 4
-Sets the directory in which keys can be found\&. Defaults to the current working directory\&.
-.RE
-.PP
+ Sets the directory in which keys can be found\&. Defaults to the current working directory\&.
+ .RE
+ .PP
\-f \fIfile\fR
.RS 4
-If a
+ If a
\fBfile\fR
is specified, then the zone is read from that file; the largest TTL and the DNSKEY TTL are determined directly from the zone data, and the
\fB\-m\fR
and
\fB\-d\fR
options do not need to be specified on the command line\&.
-.RE
-.PP
+ .RE
+ .PP
\-l \fIduration\fR
.RS 4
-The length of time to check for DNSSEC coverage\&. Key events scheduled further into the future than
+ The length of time to check for DNSSEC coverage\&. Key events scheduled further into the future than
\fBduration\fR
will be ignored, and assumed to be correct\&.
.sp
-The value of
+ The value of
\fBduration\fR
can be set in seconds, or in larger units of time by adding a suffix: \*(Aqmi\*(Aq for minutes, \*(Aqh\*(Aq for hours, \*(Aqd\*(Aq for days, \*(Aqw\*(Aq for weeks, \*(Aqmo\*(Aq for months, \*(Aqy\*(Aq for years\&.
-.RE
-.PP
+ .RE
+ .PP
\-m \fImaximum TTL\fR
.RS 4
-Sets the value to be used as the maximum TTL for the zone or zones being analyzed when determining whether there is a possibility of validation failure\&. When a zone\-signing key is deactivated, there must be enough time for the record in the zone with the longest TTL to have expired from resolver caches before that key can be purged from the DNSKEY RRset\&. If that condition does not apply, a warning will be generated\&.
+ Sets the value to be used as the maximum TTL for the zone or zones being analyzed when determining whether there is a possibility of validation failure\&. When a zone\-signing key is deactivated, there must be enough time for the record in the zone with the longest TTL to have expired from resolver caches before that key can be purged from the DNSKEY RRset\&. If that condition does not apply, a warning will be generated\&.
.sp
-The length of the TTL can be set in seconds, or in larger units of time by adding a suffix: \*(Aqmi\*(Aq for minutes, \*(Aqh\*(Aq for hours, \*(Aqd\*(Aq for days, \*(Aqw\*(Aq for weeks, \*(Aqmo\*(Aq for months, \*(Aqy\*(Aq for years\&.
+ The length of the TTL can be set in seconds, or in larger units of time by adding a suffix: \*(Aqmi\*(Aq for minutes, \*(Aqh\*(Aq for hours, \*(Aqd\*(Aq for days, \*(Aqw\*(Aq for weeks, \*(Aqmo\*(Aq for months, \*(Aqy\*(Aq for years\&.
.sp
-This option is not necessary if the
+ This option is not necessary if the
\fB\-f\fR
has been used to specify a zone file\&. If
\fB\-f\fR
has been specified, this option may still be used; it will override the value found in the file\&.
.sp
-If this option is not used and the maximum TTL cannot be retrieved from a zone file, a warning is generated and a default value of 1 week is used\&.
-.RE
-.PP
+ If this option is not used and the maximum TTL cannot be retrieved from a zone file, a warning is generated and a default value of 1 week is used\&.
+ .RE
+ .PP
\-d \fIDNSKEY TTL\fR
.RS 4
-Sets the value to be used as the DNSKEY TTL for the zone or zones being analyzed when determining whether there is a possibility of validation failure\&. When a key is rolled (that is, replaced with a new key), there must be enough time for the old DNSKEY RRset to have expired from resolver caches before the new key is activated and begins generating signatures\&. If that condition does not apply, a warning will be generated\&.
+ Sets the value to be used as the DNSKEY TTL for the zone or zones being analyzed when determining whether there is a possibility of validation failure\&. When a key is rolled (that is, replaced with a new key), there must be enough time for the old DNSKEY RRset to have expired from resolver caches before the new key is activated and begins generating signatures\&. If that condition does not apply, a warning will be generated\&.
.sp
-The length of the TTL can be set in seconds, or in larger units of time by adding a suffix: \*(Aqmi\*(Aq for minutes, \*(Aqh\*(Aq for hours, \*(Aqd\*(Aq for days, \*(Aqw\*(Aq for weeks, \*(Aqmo\*(Aq for months, \*(Aqy\*(Aq for years\&.
+ The length of the TTL can be set in seconds, or in larger units of time by adding a suffix: \*(Aqmi\*(Aq for minutes, \*(Aqh\*(Aq for hours, \*(Aqd\*(Aq for days, \*(Aqw\*(Aq for weeks, \*(Aqmo\*(Aq for months, \*(Aqy\*(Aq for years\&.
.sp
-This option is not necessary if
+ This option is not necessary if
\fB\-f\fR
has been used to specify a zone file from which the TTL of the DNSKEY RRset can be read, or if a default key TTL was set using ith the
\fB\-L\fR
to
\fBdnssec\-keygen\fR\&. If either of those is true, this option may still be used; it will override the values found in the zone file or the key file\&.
.sp
-If this option is not used and the key TTL cannot be retrieved from the zone file or the key file, then a warning is generated and a default value of 1 day is used\&.
-.RE
-.PP
+ If this option is not used and the key TTL cannot be retrieved from the zone file or the key file, then a warning is generated and a default value of 1 day is used\&.
+ .RE
+ .PP
\-r \fIresign interval\fR
.RS 4
-Sets the value to be used as the resign interval for the zone or zones being analyzed when determining whether there is a possibility of validation failure\&. This value defaults to 22\&.5 days, which is also the default in
+ Sets the value to be used as the resign interval for the zone or zones being analyzed when determining whether there is a possibility of validation failure\&. This value defaults to 22\&.5 days, which is also the default in
\fBnamed\fR\&. However, if it has been changed by the
\fBsig\-validity\-interval\fR
option in
named\&.conf, then it should also be changed here\&.
.sp
-The length of the interval can be set in seconds, or in larger units of time by adding a suffix: \*(Aqmi\*(Aq for minutes, \*(Aqh\*(Aq for hours, \*(Aqd\*(Aq for days, \*(Aqw\*(Aq for weeks, \*(Aqmo\*(Aq for months, \*(Aqy\*(Aq for years\&.
-.RE
-.PP
+ The length of the interval can be set in seconds, or in larger units of time by adding a suffix: \*(Aqmi\*(Aq for minutes, \*(Aqh\*(Aq for hours, \*(Aqd\*(Aq for days, \*(Aqw\*(Aq for weeks, \*(Aqmo\*(Aq for months, \*(Aqy\*(Aq for years\&.
+ .RE
+ .PP
\-k
.RS 4
-Only check KSK coverage; ignore ZSK events\&. Cannot be used with
+ Only check KSK coverage; ignore ZSK events\&. Cannot be used with
\fB\-z\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-z
.RS 4
-Only check ZSK coverage; ignore KSK events\&. Cannot be used with
+ Only check ZSK coverage; ignore KSK events\&. Cannot be used with
\fB\-k\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-c \fIcompilezone path\fR
.RS 4
-Specifies a path to a
+ Specifies a path to a
\fBnamed\-compilezone\fR
binary\&. Used for testing\&.
-.RE
-.SH "SEE ALSO"
-.PP
+ .RE
+ .SH "SEE ALSO"
+ .PP
\fBdnssec-checkds\fR(8),
\fBdnssec-dsfromkey\fR(8),
\fBdnssec-keygen\fR(8),
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-coverage</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.dnssec-coverage"></a><div class="titlepage"></div>
'\" t
.\" Title: dnssec-keymgr
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2016-06-03
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
dnssec-keymgr \- Ensures correct DNSKEY coverage for a zone based on a defined policy
-.SH "SYNOPSIS"
-.HP \w'\fBdnssec\-keymgr\fR\ 'u
-\fBdnssec\-keymgr\fR [\fB\-K\ \fR\fB\fIdirectory\fR\fR] [\fB\-c\ \fR\fB\fIfile\fR\fR] [\fB\-f\fR] [\fB\-k\fR] [\fB\-q\fR] [\fB\-v\fR] [\fB\-z\fR] [\fB\-g\ \fR\fB\fIpath\fR\fR] [\fB\-r\ \fR\fB\fIpath\fR\fR] [\fB\-s\ \fR\fB\fIpath\fR\fR] [zone...]
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBdnssec\-keymgr\fR\ 'u
+ \fBdnssec\-keymgr\fR
+ [\fB\-K\ \fR\fB\fIdirectory\fR\fR]
+ [\fB\-c\ \fR\fB\fIfile\fR\fR]
+ [\fB\-f\fR]
+ [\fB\-k\fR]
+ [\fB\-q\fR]
+ [\fB\-v\fR]
+ [\fB\-z\fR]
+ [\fB\-g\ \fR\fB\fIpath\fR\fR]
+ [\fB\-r\ \fR\fB\fIpath\fR\fR]
+ [\fB\-s\ \fR\fB\fIpath\fR\fR]
+ [zone...]
+ .SH "DESCRIPTION"
+ .PP
\fBdnssec\-keymgr\fR
is a high level Python wrapper to facilitate the key rollover process for zones handled by BIND\&. It uses the BIND commands for manipulating DNSSEC key metadata:
\fBdnssec\-keygen\fR
and
\fBdnssec\-settime\fR\&.
-.PP
+ .PP
DNSSEC policy can be read from a configuration file (default
/etc/dnssec\-policy\&.conf), from which the key parameters, publication and rollover schedule, and desired coverage duration for any given zone can be determined\&. This file may be used to define individual DNSSEC policies on a per\-zone basis, or to set a "default" policy used for all zones\&.
-.PP
+ .PP
When
\fBdnssec\-keymgr\fR
runs, it examines the DNSSEC keys for one or more zones, comparing their timing metadata against the policies for those zones\&. If key settings do not conform to the DNSSEC policy (for example, because the policy has been changed), they are automatically corrected\&.
-.PP
+ .PP
A zone policy can specify a duration for which we want to ensure the key correctness (\fBcoverage\fR)\&. It can also specify a rollover period (\fBroll\-period\fR)\&. If policy indicates that a key should roll over before the coverage period ends, then a successor key will automatically be created and added to the end of the key series\&.
-.PP
+ .PP
If zones are specified on the command line,
\fBdnssec\-keymgr\fR
will examine only those zones\&. If a specified zone does not already have keys in place, then keys will be generated for it according to policy\&.
-.PP
+ .PP
If zones are
\fInot\fR
specified on the command line, then
will search the key directory (either the current working directory or the directory set by the
\fB\-K\fR
option), and check the keys for all the zones represented in the directory\&.
-.PP
+ .PP
Key times that are in the past will not be updated unless the
\fB\-f\fR
is used (see below)\&. Key inactivation and deletion times that are less than five minutes in the future will be delayed by five minutes\&.
-.PP
+ .PP
It is expected that this tool will be run automatically and unattended (for example, by
\fBcron\fR)\&.
-.SH "OPTIONS"
-.PP
+ .SH "OPTIONS"
+ .PP
\-c \fIfile\fR
.RS 4
-If
+ If
\fB\-c\fR
is specified, then the DNSSEC policy is read from
\fBfile\fR\&. (If not specified, then the policy is read from
/etc/dnssec\-policy\&.conf; if that file doesn\*(Aqt exist, a built\-in global default policy is used\&.)
-.RE
-.PP
+ .RE
+ .PP
\-f
.RS 4
-Force: allow updating of key events even if they are already in the past\&. This is not recommended for use with zones in which keys have already been published\&. However, if a set of keys has been generated all of which have publication and activation dates in the past, but the keys have not been published in a zone as yet, then this option can be used to clean them up and turn them into a proper series of keys with appropriate rollover intervals\&.
-.RE
-.PP
+ Force: allow updating of key events even if they are already in the past\&. This is not recommended for use with zones in which keys have already been published\&. However, if a set of keys has been generated all of which have publication and activation dates in the past, but the keys have not been published in a zone as yet, then this option can be used to clean them up and turn them into a proper series of keys with appropriate rollover intervals\&.
+ .RE
+ .PP
\-g \fIkeygen\-path\fR
.RS 4
-Specifies a path to a
+ Specifies a path to a
\fBdnssec\-keygen\fR
binary\&. Used for testing\&. See also the
\fB\-s\fR
option\&.
-.RE
-.PP
+ .RE
+ .PP
\-h
.RS 4
-Print the
+ Print the
\fBdnssec\-keymgr\fR
help summary and exit\&.
-.RE
-.PP
+ .RE
+ .PP
\-K \fIdirectory\fR
.RS 4
-Sets the directory in which keys can be found\&. Defaults to the current working directory\&.
-.RE
-.PP
+ Sets the directory in which keys can be found\&. Defaults to the current working directory\&.
+ .RE
+ .PP
\-k
.RS 4
-Only apply policies to KSK keys\&. See also the
+ Only apply policies to KSK keys\&. See also the
\fB\-z\fR
option\&.
-.RE
-.PP
+ .RE
+ .PP
\-q
.RS 4
-Quiet: suppress printing of
+ Quiet: suppress printing of
\fBdnssec\-keygen\fR
and
\fBdnssec\-settime\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\-r \fIrandomdev\fR
.RS 4
-Specifies a path to a file containing random data\&. This is passed to the
+ Specifies a path to a file containing random data\&. This is passed to the
\fBdnssec\-keygen\fR
binary using its
\fB\-r\fR
option\&.
-.RE
-.PP
+ .RE
+ .PP
\-s \fIsettime\-path\fR
.RS 4
-Specifies a path to a
+ Specifies a path to a
\fBdnssec\-settime\fR
binary\&. Used for testing\&. See also the
\fB\-g\fR
option\&.
-.RE
-.PP
+ .RE
+ .PP
\-v
.RS 4
-Print the
+ Print the
\fBdnssec\-keymgr\fR
version and exit\&.
-.RE
-.PP
+ .RE
+ .PP
\-z
.RS 4
-Only apply policies to ZSK keys\&. See also the
+ Only apply policies to ZSK keys\&. See also the
\fB\-k\fR
option\&.
-.RE
-.SH "POLICY CONFIGURATION"
-.PP
+ .RE
+ .SH "POLICY CONFIGURATION"
+ .PP
The
dnssec\-policy\&.conf
file can specify three kinds of policies:
.sp -1
.IP \(bu 2.3
.\}
-\fIPolicy classes\fR
+ \fIPolicy classes\fR
(\fBpolicy \fR\fB\fIname\fR\fR\fB { \&.\&.\&. };\fR) can be inherited by zone policies or other policy classes; these can be used to create sets of different security profiles\&. For example, a policy class
\fBnormal\fR
might specify 1024\-bit key sizes, but a class
might specify 2048 bits instead;
\fBextra\fR
would be used for zones that had unusually high security needs\&.
-.RE
+ .RE
.sp
.RS 4
.ie n \{\
.sp -1
.IP \(bu 2.3
.\}
-\fIAlgorithm policies:\fR
+ \fIAlgorithm policies:\fR
(\fBalgorithm\-policy \fR\fB\fIalgorithm\fR\fR\fB { \&.\&.\&. };\fR
) override default per\-algorithm settings\&. For example, by default, RSASHA256 keys use 2048\-bit key sizes for both KSK and ZSK\&. This can be modified using
\fBalgorithm\-policy\fR, and the new key sizes would then be used for any key of type RSASHA256\&.
-.RE
+ .RE
.sp
.RS 4
.ie n \{\
.sp -1
.IP \(bu 2.3
.\}
-\fIZone policies:\fR
+ \fIZone policies:\fR
(\fBzone \fR\fB\fIname\fR\fR\fB { \&.\&.\&. };\fR
) set policy for a single zone by name\&. A zone policy can inherit a policy class by including a
\fBpolicy\fR
option\&. Zone names beginning with digits (i\&.e\&., 0\-9) must be quoted\&. If a zone does not have its own policy then the "default" policy applies\&.
-.RE
-.PP
+ .RE
+ .PP
Options that can be specified in policies:
-.PP
+ .PP
\fBalgorithm\fR \fIname\fR;
.RS 4
-The key algorithm\&. If no policy is defined, the default is RSASHA256\&.
-.RE
-.PP
+ The key algorithm\&. If no policy is defined, the default is RSASHA256\&.
+ .RE
+ .PP
\fBcoverage\fR \fIduration\fR;
.RS 4
-The length of time to ensure that keys will be correct; no action will be taken to create new keys to be activated after this time\&. This can be represented as a number of seconds, or as a duration using human\-readable units (examples: "1y" or "6 months")\&. A default value for this option can be set in algorithm policies as well as in policy classes or zone policies\&. If no policy is configured, the default is six months\&.
-.RE
-.PP
+ The length of time to ensure that keys will be correct; no action will be taken to create new keys to be activated after this time\&. This can be represented as a number of seconds, or as a duration using human\-readable units (examples: "1y" or "6 months")\&. A default value for this option can be set in algorithm policies as well as in policy classes or zone policies\&. If no policy is configured, the default is six months\&.
+ .RE
+ .PP
\fBdirectory\fR \fIpath\fR;
.RS 4
-Specifies the directory in which keys should be stored\&.
-.RE
-.PP
+ Specifies the directory in which keys should be stored\&.
+ .RE
+ .PP
\fBkey\-size\fR \fIkeytype\fR \fIsize\fR;
.RS 4
-Specifies the number of bits to use in creating keys\&. The keytype is either "zsk" or "ksk"\&. A default value for this option can be set in algorithm policies as well as in policy classes or zone policies\&. If no policy is configured, the default is 1024 bits for DSA keys and 2048 for RSA\&.
-.RE
-.PP
+ Specifies the number of bits to use in creating keys\&. The keytype is either "zsk" or "ksk"\&. A default value for this option can be set in algorithm policies as well as in policy classes or zone policies\&. If no policy is configured, the default is 1024 bits for DSA keys and 2048 for RSA\&.
+ .RE
+ .PP
\fBkeyttl\fR \fIduration\fR;
.RS 4
-The key TTL\&. If no policy is defined, the default is one hour\&.
-.RE
-.PP
+ The key TTL\&. If no policy is defined, the default is one hour\&.
+ .RE
+ .PP
\fBpost\-publish\fR \fIkeytype\fR \fIduration\fR;
.RS 4
-How long after inactivation a key should be deleted from the zone\&. Note: If
+ How long after inactivation a key should be deleted from the zone\&. Note: If
\fBroll\-period\fR
is not set, this value is ignored\&. The keytype is either "zsk" or "ksk"\&. A default duration for this option can be set in algorithm policies as well as in policy classes or zone policies\&. The default is one month\&.
-.RE
-.PP
+ .RE
+ .PP
\fBpre\-publish\fR \fIkeytype\fR \fIduration\fR;
.RS 4
-How long before activation a key should be published\&. Note: If
+ How long before activation a key should be published\&. Note: If
\fBroll\-period\fR
is not set, this value is ignored\&. The keytype is either "zsk" or "ksk"\&. A default duration for this option can be set in algorithm policies as well as in policy classes or zone policies\&. The default is one month\&.
-.RE
-.PP
+ .RE
+ .PP
\fBroll\-period\fR \fIkeytype\fR \fIduration\fR;
.RS 4
-How frequently keys should be rolled over\&. The keytype is either "zsk" or "ksk"\&. A default duration for this option can be set in algorithm policies as well as in policy classes or zone policies\&. If no policy is configured, the default is one year for ZSKs\&. KSKs do not roll over by default\&.
-.RE
-.PP
+ How frequently keys should be rolled over\&. The keytype is either "zsk" or "ksk"\&. A default duration for this option can be set in algorithm policies as well as in policy classes or zone policies\&. If no policy is configured, the default is one year for ZSKs\&. KSKs do not roll over by default\&.
+ .RE
+ .PP
\fBstandby\fR \fIkeytype\fR \fInumber\fR;
.RS 4
-Not yet implemented\&.
-.RE
-.SH "REMAINING WORK"
+ Not yet implemented\&.
+ .RE
+ .SH "REMAINING WORK"
.sp
.RS 4
.ie n \{\
.sp -1
.IP \(bu 2.3
.\}
-Enable scheduling of KSK rollovers using the
+ Enable scheduling of KSK rollovers using the
\fB\-P sync\fR
and
\fB\-D sync\fR
and
\fBdnssec\-settime\fR\&. Check the parent zone (as in
\fBdnssec\-checkds\fR) to determine when it\*(Aqs safe for the key to roll\&.
-.RE
+ .RE
.sp
.RS 4
.ie n \{\
.sp -1
.IP \(bu 2.3
.\}
-Allow configuration of standby keys and use of the REVOKE bit, for keys that use RFC 5011 semantics\&.
-.RE
-.SH "SEE ALSO"
-.PP
+ Allow configuration of standby keys and use of the REVOKE bit, for keys that use RFC 5011 semantics\&.
+ .RE
+ .SH "SEE ALSO"
+ .PP
\fBdnssec-coverage\fR(8),
\fBdnssec-keygen\fR(8),
\fBdnssec-settime\fR(8),
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-keymgr</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.dnssec-keymgr"></a><div class="titlepage"></div>
'\" t
.\" Title: rndc
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2014-08-15
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
rndc \- name server control utility
-.SH "SYNOPSIS"
-.HP \w'\fBrndc\fR\ 'u
-\fBrndc\fR [\fB\-b\ \fR\fB\fIsource\-address\fR\fR] [\fB\-c\ \fR\fB\fIconfig\-file\fR\fR] [\fB\-k\ \fR\fB\fIkey\-file\fR\fR] [\fB\-s\ \fR\fB\fIserver\fR\fR] [\fB\-p\ \fR\fB\fIport\fR\fR] [\fB\-q\fR] [\fB\-r\fR] [\fB\-V\fR] [\fB\-y\ \fR\fB\fIkey_id\fR\fR] {command}
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBrndc\fR\ 'u
+ \fBrndc\fR
+ [\fB\-b\ \fR\fB\fIsource\-address\fR\fR]
+ [\fB\-c\ \fR\fB\fIconfig\-file\fR\fR]
+ [\fB\-k\ \fR\fB\fIkey\-file\fR\fR]
+ [\fB\-s\ \fR\fB\fIserver\fR\fR]
+ [\fB\-p\ \fR\fB\fIport\fR\fR]
+ [\fB\-q\fR]
+ [\fB\-r\fR]
+ [\fB\-V\fR]
+ [\fB\-y\ \fR\fB\fIkey_id\fR\fR]
+ {command}
+ .SH "DESCRIPTION"
+ .PP
\fBrndc\fR
controls the operation of a name server\&. It supersedes the
\fBndc\fR
utility that was provided in old BIND releases\&. If
\fBrndc\fR
is invoked with no command line options or arguments, it prints a short summary of the supported commands and the available options and their arguments\&.
-.PP
+ .PP
\fBrndc\fR
communicates with the name server over a TCP connection, sending commands authenticated with digital signatures\&. In the current versions of
\fBrndc\fR
and
\fBnamed\fR, the only supported authentication algorithms are HMAC\-MD5 (for compatibility), HMAC\-SHA1, HMAC\-SHA224, HMAC\-SHA256 (default), HMAC\-SHA384 and HMAC\-SHA512\&. They use a shared secret on each end of the connection\&. This provides TSIG\-style authentication for the command request and the name server\*(Aqs response\&. All commands sent over the channel must be signed by a key_id known to the server\&.
-.PP
+ .PP
\fBrndc\fR
reads a configuration file to determine how to contact the name server and decide what algorithm and key it should use\&.
-.SH "OPTIONS"
-.PP
+ .SH "OPTIONS"
+ .PP
\-b \fIsource\-address\fR
.RS 4
-Use
+ Use
\fIsource\-address\fR
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\&.
-.RE
-.PP
+ .RE
+ .PP
\-c \fIconfig\-file\fR
.RS 4
-Use
+ Use
\fIconfig\-file\fR
as the configuration file instead of the default,
/etc/rndc\&.conf\&.
-.RE
-.PP
+ .RE
+ .PP
\-k \fIkey\-file\fR
.RS 4
-Use
+ Use
\fIkey\-file\fR
as the key file instead of the default,
/etc/rndc\&.key\&. The key in
will be used to authenticate commands sent to the server if the
\fIconfig\-file\fR
does not exist\&.
-.RE
-.PP
+ .RE
+ .PP
\-s \fIserver\fR
.RS 4
-\fIserver\fR
+ \fIserver\fR
is the name or address of the server which matches a server statement in the configuration file for
\fBrndc\fR\&. If no server is supplied on the command line, the host named by the default\-server clause in the options statement of the
\fBrndc\fR
configuration file will be used\&.
-.RE
-.PP
+ .RE
+ .PP
\-p \fIport\fR
.RS 4
-Send commands to TCP port
+ Send commands to TCP port
\fIport\fR
instead of BIND 9\*(Aqs default control channel port, 953\&.
-.RE
-.PP
+ .RE
+ .PP
\-q
.RS 4
-Quiet mode: Message text returned by the server will not be printed except when there is an error\&.
-.RE
-.PP
+ Quiet mode: Message text returned by the server will not be printed except when there is an error\&.
+ .RE
+ .PP
\-r
.RS 4
-Instructs
+ Instructs
\fBrndc\fR
to print the result code returned by
\fBnamed\fR
after executing the requested command (e\&.g\&., ISC_R_SUCCESS, ISC_R_FAILURE, etc)\&.
-.RE
-.PP
+ .RE
+ .PP
\-V
.RS 4
-Enable verbose logging\&.
-.RE
-.PP
+ Enable verbose logging\&.
+ .RE
+ .PP
\-y \fIkey_id\fR
.RS 4
-Use the key
+ Use the key
\fIkey_id\fR
from the configuration file\&.
\fIkey_id\fR
is specified,
\fBrndc\fR
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\&.
-.RE
-.SH "COMMANDS"
-.PP
+ .RE
+ .SH "COMMANDS"
+ .PP
A list of commands supported by
\fBrndc\fR
can be seen by running
\fBrndc\fR
without arguments\&.
-.PP
+ .PP
Currently supported commands are:
-.PP
+ .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
+ Add a zone while the server is running\&. This command requires the
\fBallow\-new\-zones\fR
option to be set to
\fByes\fR\&. The
string specified on the command line is the zone configuration text that would ordinarily be placed in
named\&.conf\&.
.sp
-The configuration is saved in a file called
+ The configuration is saved in a file called
\fIname\fR\&.nzf, where
\fIname\fR
is the name of the view, or if it contains characters that are incompatible with use as a file name, a cryptographic hash generated from the name of the view\&. When
\fBnamed\fR
is restarted, the file will be loaded into the view configuration, so that zones that were added can persist after a restart\&.
.sp
-This sample
+ This sample
\fBaddzone\fR
command would add the zone
example\&.com
to the default view:
.sp
-$\fBrndc addzone example\&.com \*(Aq{ type master; file "example\&.com\&.db"; };\*(Aq\fR
+ $\fBrndc addzone example\&.com \*(Aq{ type master; file "example\&.com\&.db"; };\*(Aq\fR
.sp
-(Note the brackets and semi\-colon around the zone configuration text\&.)
+ (Note the brackets and semi\-colon around the zone configuration text\&.)
.sp
-See also
+ See also
\fBrndc delzone\fR
and
\fBrndc modzone\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\fBdelzone \fR\fB[\-clean]\fR\fB \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR\fB \fR
.RS 4
-Delete a zone while the server is running\&.
+ Delete a zone while the server is running\&.
.sp
-If the
+ If the
\fB\-clean\fR
argument is specified, the zone\*(Aqs master file (and journal file, if any) will be deleted along with the zone\&. Without the
\fB\-clean\fR
\fBrndc delzone\fR
command\&.)
.sp
-If the zone was originally added via
+ If the zone was originally added via
\fBrndc addzone\fR, then it will be removed permanently\&. However, if it was originally configured in
named\&.conf, then that original configuration is still in place; when the server is restarted or reconfigured, the zone will come back\&. To remove it permanently, it must also be removed from
named\&.conf
.sp
-See also
+ See also
\fBrndc addzone\fR
and
\fBrndc modzone\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\fBdnstap ( \-reopen | \-roll \fR\fB[\fInumber\fR]\fR\fB )\fR
.RS 4
-Close and re\-open DNSTAP output files\&.
+ Close and re\-open DNSTAP output files\&.
\fBrndc dnstap \-reopen\fR
allows the output file to be renamed externally, so that
\fBnamed\fR
causes the output file to be rolled automatically, similar to log files; the most recent output file has "\&.0" appended to its name; the previous most recent output file is moved to "\&.1", and so on\&. If
\fInumber\fR
is specified, then the number of backup log files is limited to that number\&.
-.RE
-.PP
+ .RE
+ .PP
\fBdumpdb \fR\fB[\-all|\-cache|\-zones|\-adb|\-bad|\-fail]\fR\fB \fR\fB[\fIview \&.\&.\&.\fR]\fR
.RS 4
-Dump the server\*(Aqs caches (default) and/or zones to the dump file for the specified views\&. If no view is specified, all views are dumped\&. (See the
+ Dump the server\*(Aqs 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
+ .RE
+ .PP
\fBflush\fR
.RS 4
-Flushes the server\*(Aqs cache\&.
-.RE
-.PP
+ Flushes the server\*(Aqs cache\&.
+ .RE
+ .PP
\fBflushname\fR \fIname\fR [\fIview\fR]
.RS 4
-Flushes the given name from the view\*(Aqs DNS cache and, if applicable, from the view\*(Aqs nameserver address database, bad server cache and SERVFAIL cache\&.
-.RE
-.PP
+ Flushes the given name from the view\*(Aqs DNS cache and, if applicable, from the view\*(Aqs nameserver address database, bad server cache and SERVFAIL cache\&.
+ .RE
+ .PP
\fBflushtree\fR \fIname\fR [\fIview\fR]
.RS 4
-Flushes the given name, and all of its subdomains, from the view\*(Aqs DNS cache, address database, bad server cache, and SERVFAIL cache\&.
-.RE
-.PP
+ Flushes the given name, and all of its subdomains, from the view\*(Aqs DNS cache, address database, bad server cache, and SERVFAIL 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\&.
+ 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
+ See also
\fBrndc thaw\fR\&.
-.RE
-.PP
+ .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
+ 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\*(Aqs process id is returned\&. This allows an external process to determine when
\fBnamed\fR
had completed halting\&.
.sp
-See also
+ See also
\fBrndc stop\fR\&.
-.RE
-.PP
+ .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\*(Aqs DNSKEY RRset\&. Unlike
+ Fetch all DNSSEC keys for the given zone from the key directory\&. If they are within their publication period, merge them into the zone\*(Aqs 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
+ 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
+ .RE
+ .PP
\fBmanaged\-keys \fR\fB\fI(status | refresh | sync)\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR
.RS 4
-When run with the "status" keyword, print the current status of the managed\-keys database for the specified view, or for all views if none is specified\&. When run with the "refresh" keyword, force an immediate refresh of all the managed\-keys in the specified view, or all views\&. When run with the "sync" keyword, force an immediate dump of the managed\-keys database to disk (in the file
+ When run with the "status" keyword, print the current status of the managed\-keys database for the specified view, or for all views if none is specified\&. When run with the "refresh" keyword, force an immediate refresh of all the managed\-keys in the specified view, or all views\&. When run with the "sync" keyword, force an immediate dump of the managed\-keys database to disk (in the file
managed\-keys\&.bind
or (\fIviewname\fR\&.mkeys)\&.
-.RE
-.PP
+ .RE
+ .PP
\fBmodzone \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR\fB \fR\fB\fIconfiguration\fR\fR\fB \fR
.RS 4
-Modify the configuration of a zone while the server is running\&. This command requires the
+ Modify the configuration of a zone while the server is running\&. This command requires the
\fBallow\-new\-zones\fR
option to be set to
\fByes\fR\&. As with
string specified on the command line is the zone configuration text that would ordinarily be placed in
named\&.conf\&.
.sp
-If the zone was originally added via
+ If the zone was originally added via
\fBrndc addzone\fR, the configuration changes will be recorded permanently and will still be in effect after the server is restarted or reconfigured\&. However, if it was originally configured in
named\&.conf, then that original configuration is still in place; when the server is restarted or reconfigured, the zone will revert to its original configuration\&. To make the changes permanent, it must also be modified in
named\&.conf
.sp
-See also
+ See also
\fBrndc addzone\fR
and
\fBrndc delzone\fR\&.
-.RE
-.PP
+ .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
+ Resend NOTIFY messages for the zone\&.
+ .RE
+ .PP
\fBnotrace\fR
.RS 4
-Sets the server\*(Aqs debugging level to 0\&.
+ Sets the server\*(Aqs debugging level to 0\&.
.sp
-See also
+ See also
\fBrndc trace\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\fBnta \fR\fB[( \-class \fIclass\fR | \-dump | \-force | \-remove | \-lifetime \fIduration\fR)]\fR\fB \fR\fB\fIdomain\fR\fR\fB \fR\fB[\fIview\fR]\fR\fB \fR
.RS 4
-Sets a DNSSEC negative trust anchor (NTA) for
+ Sets a DNSSEC negative trust anchor (NTA) for
\fBdomain\fR, with a lifetime of
\fBduration\fR\&. The default lifetime is configured in
named\&.conf
\fBnta\-lifetime\fR
option, and defaults to one hour\&. The lifetime cannot exceed one week\&.
.sp
-A negative trust anchor selectively disables DNSSEC validation for zones that are known to be failing because of misconfiguration rather than an attack\&. When data to be validated is at or below an active NTA (and above any other configured trust anchors),
+ A negative trust anchor selectively disables DNSSEC validation for zones that are known to be failing because of misconfiguration rather than an attack\&. When data to be validated is at or below an active NTA (and above any other configured trust anchors),
\fBnamed\fR
will abort the DNSSEC validation process and treat the data as insecure rather than bogus\&. This continues until the NTA\*(Aqs lifetime is elapsed\&.
.sp
-NTAs persist across restarts of the
+ NTAs persist across restarts of the
\fBnamed\fR
server\&. The NTAs for a view are saved in a file called
\fIname\fR\&.nta, where
\fIname\fR
is the name of the view, or if it contains characters that are incompatible with use as a file name, a cryptographic hash generated from the name of the view\&.
.sp
-An existing NTA can be removed by using the
+ An existing NTA can be removed by using the
\fB\-remove\fR
option\&.
.sp
-An NTA\*(Aqs lifetime can be specified with the
+ An NTA\*(Aqs lifetime can be specified with the
\fB\-lifetime\fR
option\&. TTL\-style suffixes can be used to specify the lifetime in seconds, minutes, or hours\&. If the specified NTA already exists, its lifetime will be updated to the new value\&. Setting
\fBlifetime\fR
to zero is equivalent to
\fB\-remove\fR\&.
.sp
-If the
+ If the
\fB\-dump\fR
is used, any other arguments are ignored, and a list of existing NTAs is printed (note that this may include NTAs that are expired but have not yet been cleaned up)\&.
.sp
-Normally,
+ Normally,
\fBnamed\fR
will periodically test to see whether data below an NTA can now be validated (see the
\fBnta\-recheck\fR
\fB\-force\fR
overrides this behavior and forces an NTA to persist for its entire lifetime, regardless of whether data could be validated if the NTA were not present\&.
.sp
-The view class can be specified with
+ The view class can be specified with
\fB\-class\fR\&. The default is class
\fBIN\fR, which is the only class for which DNSSEC is currently supported\&.
.sp
-All of these options can be shortened, i\&.e\&., to
+ All of these options can be shortened, i\&.e\&., to
\fB\-l\fR,
\fB\-r\fR,
\fB\-d\fR,
\fB\-f\fR, and
\fB\-c\fR\&.
-.RE
-.PP
+ .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\&.)
+ 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
+ Query logging can also be enabled by explicitly directing the
+\fBqueries\fR
+\fBcategory\fR
to a
\fBchannel\fR
in the
\fBoptions\fR
section of
named\&.conf\&.
-.RE
-.PP
+ .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
+ 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
+ .RE
+ .PP
\fBrecursing\fR
.RS 4
-Dump the list of queries
+ Dump the list of queries
\fBnamed\fR
is currently recursing on, and the list of domains to which iterative queries are currently being sent\&. (The second list includes the number of fetches currently active for the given domain, and how many have been passed or dropped because of the
\fBfetches\-per\-zone\fR
option\&.)
-.RE
-.PP
+ .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
+ Schedule zone maintenance for the given zone\&.
+ .RE
+ .PP
\fBreload\fR
.RS 4
-Reload configuration file and zones\&.
-.RE
-.PP
+ 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
+ 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\&.
+ Retransfer the given slave zone from the master server\&.
.sp
-If the zone is configured to use
+ 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
+ .RE
+ .PP
\fBscan\fR
.RS 4
-Scan the list of available network interfaces for changes, without performing a full
+ 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
+ .RE
+ .PP
\fBsecroots \fR\fB[\-]\fR\fB \fR\fB[\fIview \&.\&.\&.\fR]\fR
.RS 4
-Dump the server\*(Aqs security roots and negative trust anchors for the specified views\&. If no view is specified, all views are dumped\&.
+ Dump the server\*(Aqs security roots and negative trust anchors for the specified views\&. If no view is specified, all views are dumped\&.
.sp
-If the first argument is "\-", then the output is returned via the
+ If the first argument is "\-", then the output is returned via the
\fBrndc\fR
response channel and printed to the standard output\&. Otherwise, it is written to the secroots dump file, which defaults to
named\&.secroots, but can be overridden via the
option in
named\&.conf\&.
.sp
-See also
+ See also
\fBrndc managed\-keys\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\fBshowzone \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR\fB \fR
.RS 4
-Print the configuration of a running zone\&.
+ Print the configuration of a running zone\&.
.sp
-See also
+ See also
\fBrndc zonestatus\fR\&.
-.RE
-.PP
+ .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
+ 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\*(Aqs 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
+ 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
+ See also
\fBrndc loadkeys\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\fBsigning \fR\fB[( \-list | \-clear \fIkeyid/algorithm\fR | \-clear all | \-nsec3param ( \fIparameters\fR | none ) | \-serial \fIvalue\fR ) ]\fR\fB \fR\fB\fIzone\fR\fR\fB \fR\fB[\fIclass\fR [\fIview\fR]]\fR\fB \fR
.RS 4
-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
+ 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
\fBsig\-signing\-type\fR\&.
\fBrndc signing \-list\fR
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\&.
.sp
-\fBrndc signing \-clear\fR
+ \fBrndc signing \-clear\fR
can remove a single key (specified in the same format that
\fBrndc signing \-list\fR
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\&.
.sp
-\fBrndc signing \-nsec3param\fR
+ \fBrndc signing \-nsec3param\fR
sets the NSEC3 parameters for a zone\&. This is the only supported mechanism for using NSEC3 with
\fBinline\-signing\fR
zones\&. Parameters are specified in the same format as an NSEC3PARAM resource record: hash algorithm, flags, iterations, and salt, in that order\&.
.sp
-Currently, the only defined value for hash algorithm is
+ Currently, the only defined value for hash algorithm is
1, representing SHA\-1\&. The
\fBflags\fR
may be set to
\fBnamed\fR
to generate a random 64\-bit salt\&.
.sp
-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:
+ 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:
\fBrndc signing \-nsec3param 1 0 10 FFFF \fR\fB\fIzone\fR\fR\&. To set the opt\-out flag, 15 iterations, and no salt, use:
\fBrndc signing \-nsec3param 1 1 15 \- \fR\fB\fIzone\fR\fR\&.
.sp
-\fBrndc signing \-nsec3param none\fR
+ \fBrndc signing \-nsec3param none\fR
removes an existing NSEC3 chain and replaces it with NSEC\&.
.sp
-\fBrndc signing \-serial value\fR
+ \fBrndc signing \-serial value\fR
sets the serial number of the zone to value\&. If the value would cause the serial number to go backwards it will be rejected\&. The primary use is to set the serial on inline signed zones\&.
-.RE
-.PP
+ .RE
+ .PP
\fBstats\fR
.RS 4
-Write server statistics to the statistics file\&. (See the
+ Write server statistics to the statistics file\&. (See the
\fBstatistics\-file\fR
option in the BIND 9 Administrator Reference Manual\&.)
-.RE
-.PP
+ .RE
+ .PP
\fBstatus\fR
.RS 4
-Display status of the server\&. Note that the number of zones includes the internal
+ 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
+ .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
+ 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\*(Aqs process id is returned\&. This allows an external process to determine when
\fBnamed\fR
had completed stopping\&.
.sp
-See also
+ See also
\fBrndc halt\fR\&.
-.RE
-.PP
+ .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
+ 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
+ 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
+ See also
\fBrndc freeze\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\fBtrace\fR
.RS 4
-Increment the servers debugging level by one\&.
-.RE
-.PP
+ Increment the servers debugging level by one\&.
+ .RE
+ .PP
\fBtrace \fR\fB\fIlevel\fR\fR
.RS 4
-Sets the server\*(Aqs debugging level to an explicit value\&.
+ Sets the server\*(Aqs debugging level to an explicit value\&.
.sp
-See also
+ See also
\fBrndc notrace\fR\&.
-.RE
-.PP
+ .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
+ 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
+ List the names of all TSIG keys currently configured for use by
\fBnamed\fR
in each view\&. The list includes both statically configured keys and dynamic TKEY\-negotiated keys\&.
-.RE
-.PP
+ .RE
+ .PP
\fBvalidation ( on | off | status ) \fR\fB[\fIview \&.\&.\&.\fR]\fR\fB \fR
.RS 4
-Enable, disable, or check the current status of DNSSEC validation\&. Note
+ 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
+ .RE
+ .PP
\fBzonestatus \fR\fB\fIzone\fR\fR\fB \fR\fB[\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\&.
+ 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\&.
.sp
-See also
+ See also
\fBrndc showzone\fR\&.
-.RE
-.SH "LIMITATIONS"
-.PP
+ .RE
+ .SH "LIMITATIONS"
+ .PP
There is currently no way to provide the shared secret for a
\fBkey_id\fR
without using the configuration file\&.
-.PP
+ .PP
Several error messages could be clearer\&.
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBrndc.conf\fR(5),
\fBrndc-confgen\fR(8),
\fBnamed\fR(8),
'\" t
.\" Title: rndc.conf
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2013-03-14
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
rndc.conf \- rndc configuration file
-.SH "SYNOPSIS"
-.HP \w'\fBrndc\&.conf\fR\ 'u
-\fBrndc\&.conf\fR
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBrndc\&.conf\fR\ 'u
+ \fBrndc\&.conf\fR
+ .SH "DESCRIPTION"
+ .PP
rndc\&.conf
is the configuration file for
\fBrndc\fR, the BIND 9 name server control utility\&. This file has a similar structure and syntax to
named\&.conf\&. Statements are enclosed in braces and terminated with a semi\-colon\&. Clauses in the statements are also semi\-colon terminated\&. The usual comment styles are supported:
-.PP
+ .PP
C style: /* */
-.PP
+ .PP
C++ style: // to end of line
-.PP
+ .PP
Unix style: # to end of line
-.PP
+ .PP
rndc\&.conf
is much simpler than
named\&.conf\&. The file uses three statements: an options statement, a server statement and a key statement\&.
-.PP
+ .PP
The
\fBoptions\fR
statement contains five clauses\&. The
and
\fBdefault\-source\-address\-v6\fR
clauses which can be used to set the IPv4 and IPv6 source addresses respectively\&.
-.PP
+ .PP
After the
\fBserver\fR
keyword, the server statement includes a string which is the hostname or address for a name server\&. The statement has three possible clauses:
or
\fBsource\-address\-v6\fR
of supplied then these will be used to specify the IPv4 and IPv6 source addresses respectively\&.
-.PP
+ .PP
The
\fBkey\fR
statement begins with an identifying string, the name of the key\&. The statement has two clauses\&.
identifies the authentication algorithm for
\fBrndc\fR
to use; currently only HMAC\-MD5 (for compatibility), HMAC\-SHA1, HMAC\-SHA224, HMAC\-SHA256 (default), HMAC\-SHA384 and HMAC\-SHA512 are supported\&. This is followed by a secret clause which contains the base\-64 encoding of the algorithm\*(Aqs authentication key\&. The base\-64 string is enclosed in double quotes\&.
-.PP
+ .PP
There are two common ways to generate the base\-64 string for the secret\&. The BIND 9 program
\fBrndc\-confgen\fR
can be used to generate a random key, or the
\fBmimencode\fR, can be used to generate a base\-64 string from known input\&.
\fBmmencode\fR
does not ship with BIND 9 but is available on many systems\&. See the EXAMPLE section for sample command lines for each\&.
-.SH "EXAMPLE"
-.PP
+ .SH "EXAMPLE"
+ .PP
.if n \{\
.RS 4
.\}
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
.if n \{\
.RS 4
.\}
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
.if n \{\
.RS 4
.\}
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
.if n \{\
.RS 4
.\}
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
.if n \{\
.RS 4
.\}
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
In the above example,
\fBrndc\fR
will by default use the server at localhost (127\&.0\&.0\&.1) and the key called samplekey\&. Commands to the localhost server will use the samplekey key, which must also be defined in the server\*(Aqs configuration file with the same name and secret\&. The key statement indicates that samplekey uses the HMAC\-SHA256 algorithm and its secret clause contains the base\-64 encoding of the HMAC\-SHA256 secret enclosed in double quotes\&.
-.PP
+ .PP
If
\fBrndc \-s testserver\fR
is used then
\fBrndc\fR
will connect to server on localhost port 5353 using the key testkey\&.
-.PP
+ .PP
To generate a random secret with
\fBrndc\-confgen\fR:
-.PP
+ .PP
\fBrndc\-confgen\fR
-.PP
+ .PP
A complete
rndc\&.conf
file, including the randomly generated key, will be written to the standard output\&. Commented\-out
statements for
named\&.conf
are also printed\&.
-.PP
+ .PP
To generate a base\-64 secret with
\fBmmencode\fR:
-.PP
+ .PP
\fBecho "known plaintext for a secret" | mmencode\fR
-.SH "NAME SERVER CONFIGURATION"
-.PP
+ .SH "NAME SERVER CONFIGURATION"
+ .PP
The name server must be configured to accept rndc connections and to recognize the key specified in the
rndc\&.conf
file, using the controls statement in
named\&.conf\&. See the sections on the
\fBcontrols\fR
statement in the BIND 9 Administrator Reference Manual for details\&.
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBrndc\fR(8),
\fBrndc-confgen\fR(8),
\fBmmencode\fR(1),
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>rndc.conf</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.rndc.conf"></a><div class="titlepage"></div>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>rndc</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.rndc"></a><div class="titlepage"></div>
'\" t
.\" Title: arpaname
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2009-03-03
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
arpaname \- translate IP addresses to the corresponding ARPA names
-.SH "SYNOPSIS"
-.HP \w'\fBarpaname\fR\ 'u
-\fBarpaname\fR {\fIipaddress\ \fR...}
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBarpaname\fR\ 'u
+ \fBarpaname\fR
+ {\fIipaddress\ \fR...}
+ .SH "DESCRIPTION"
+ .PP
\fBarpaname\fR
translates IP addresses (IPv4 and IPv6) to the corresponding IN\-ADDR\&.ARPA or IP6\&.ARPA names\&.
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
BIND 9 Administrator Reference Manual\&.
.SH "AUTHOR"
.PP
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>arpaname</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.arpaname"></a><div class="titlepage"></div>
'\" t
.\" Title: dnstap-read
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2015-09-13
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
dnstap-read \- print dnstap data in human\-readable form
-.SH "SYNOPSIS"
-.HP \w'\fBdnstap\-read\fR\ 'u
-\fBdnstap\-read\fR [\fB\-m\fR] [\fB\-p\fR] [\fB\-y\fR] {\fIfile\fR}
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBdnstap\-read\fR\ 'u
+ \fBdnstap\-read\fR
+ [\fB\-m\fR]
+ [\fB\-p\fR]
+ [\fB\-y\fR]
+ {\fIfile\fR}
+ .SH "DESCRIPTION"
+ .PP
\fBdnstap\-read\fR
reads
\fBdnstap\fR
data is printed in a short summary format, but if the
\fB\-y\fR
option is specified, then a longer and more detailed YAML format is used instead\&.
-.SH "OPTIONS"
-.PP
+ .SH "OPTIONS"
+ .PP
\-m
.RS 4
-Trace memory allocations; used for debugging memory leaks\&.
-.RE
-.PP
+ Trace memory allocations; used for debugging memory leaks\&.
+ .RE
+ .PP
\-p
.RS 4
-After printing the
+ After printing the
\fBdnstap\fR
data, print the text form of the DNS message that was encapsulated in the
\fBdnstap\fR
frame\&.
-.RE
-.PP
+ .RE
+ .PP
\-y
.RS 4
-Print
+ Print
\fBdnstap\fR
data in a detailed YAML format\&.
-.RE
-.SH "SEE ALSO"
-.PP
+ .RE
+ .SH "SEE ALSO"
+ .PP
\fBnamed\fR(8),
\fBrndc\fR(8),
BIND 9 Administrator Reference Manual\&.
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnstap-read</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.dnstap-read"></a><div class="titlepage"></div>
'\" t
.\" Title: genrandom
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2011-08-08
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
genrandom \- generate a file containing random data
-.SH "SYNOPSIS"
-.HP \w'\fBgenrandom\fR\ 'u
-\fBgenrandom\fR [\fB\-n\ \fR\fB\fInumber\fR\fR] {\fIsize\fR} {\fIfilename\fR}
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBgenrandom\fR\ 'u
+ \fBgenrandom\fR
+ [\fB\-n\ \fR\fB\fInumber\fR\fR]
+ {\fIsize\fR}
+ {\fIfilename\fR}
+ .SH "DESCRIPTION"
+ .PP
\fBgenrandom\fR
generates a file or a set of files containing a specified quantity of pseudo\-random data, which can be used as a source of entropy for other commands on systems with no random device\&.
-.SH "ARGUMENTS"
-.PP
+ .SH "ARGUMENTS"
+ .PP
\-n \fInumber\fR
.RS 4
-In place of generating one file, generates
+ In place of generating one file, generates
\fBnumber\fR
(from 2 to 9) files, appending
\fBnumber\fR
to the name\&.
-.RE
-.PP
+ .RE
+ .PP
size
.RS 4
-The size of the file, in kilobytes, to generate\&.
-.RE
-.PP
+ The size of the file, in kilobytes, to generate\&.
+ .RE
+ .PP
filename
.RS 4
-The file name into which random data should be written\&.
-.RE
-.SH "SEE ALSO"
-.PP
+ The file name into which random data should be written\&.
+ .RE
+ .SH "SEE ALSO"
+ .PP
\fBrand\fR(3),
\fBarc4random\fR(3)
.SH "AUTHOR"
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>genrandom</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.genrandom"></a><div class="titlepage"></div>
'\" t
.\" Title: isc-hmac-fixup
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2013-04-28
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
isc-hmac-fixup \- fixes HMAC keys generated by older versions of BIND
-.SH "SYNOPSIS"
-.HP \w'\fBisc\-hmac\-fixup\fR\ 'u
-\fBisc\-hmac\-fixup\fR {\fIalgorithm\fR} {\fIsecret\fR}
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBisc\-hmac\-fixup\fR\ 'u
+ \fBisc\-hmac\-fixup\fR
+ {\fIalgorithm\fR}
+ {\fIsecret\fR}
+ .SH "DESCRIPTION"
+ .PP
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 hash algorithm (i\&.e\&., SHA1 keys longer than 160 bits, SHA256 keys longer than 256 bits, etc) to be used incorrectly, generating a message authentication code that was incompatible with other DNS implementations\&.
-.PP
+ .PP
This bug was fixed in BIND 9\&.7\&. However, the fix may cause incompatibility between older and newer versions of BIND, when using long keys\&.
\fBisc\-hmac\-fixup\fR
modifies those keys to restore compatibility\&.
-.PP
+ .PP
To modify a key, run
\fBisc\-hmac\-fixup\fR
and specify the key\*(Aqs algorithm and secret on the command line\&. If the secret is longer than the digest length of the algorithm (64 bytes for SHA1 through SHA256, or 128 bytes for SHA384 and SHA512), then a new secret will be generated consisting of a hash digest of the old secret\&. (If the secret did not require conversion, then it will be printed without modification\&.)
-.SH "SECURITY CONSIDERATIONS"
-.PP
+ .SH "SECURITY CONSIDERATIONS"
+ .PP
Secrets that have been converted by
\fBisc\-hmac\-fixup\fR
are shortened, but as this is how the HMAC protocol works in operation anyway, it does not affect security\&. RFC 2104 notes, "Keys longer than [the digest length] are acceptable but the extra length would not significantly increase the function strength\&."
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
BIND 9 Administrator Reference Manual,
RFC 2104\&.
.SH "AUTHOR"
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>isc-hmac-fixup</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.isc-hmac-fixup"></a><div class="titlepage"></div>
'\" t
.\" Title: mdig
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2015-01-05
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
mdig \- DNS pipelined lookup utility
-.SH "SYNOPSIS"
-.HP \w'\fBmdig\fR\ 'u
-\fBmdig\fR {@server} [\fB\-f\ \fR\fB\fIfilename\fR\fR] [\fB\-h\fR] [\fB\-v\fR] [[\fB\-4\fR] | [\fB\-6\fR]] [\fB\-m\fR] [\fB\-b\ \fR\fB\fIaddress\fR\fR] [\fB\-p\ \fR\fB\fIport#\fR\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-t\ \fR\fB\fItype\fR\fR] [\fB\-i\fR] [\fB\-x\ \fR\fB\fIaddr\fR\fR] [plusopt...]
-.HP \w'\fBmdig\fR\ 'u
-\fBmdig\fR {\-h}
-.HP \w'\fBmdig\fR\ 'u
-\fBmdig\fR [@server] {global\-opt...} {{local\-opt...}\ {query}...}
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBmdig\fR\ 'u
+ \fBmdig\fR
+ {@server}
+ [\fB\-f\ \fR\fB\fIfilename\fR\fR]
+ [\fB\-h\fR]
+ [\fB\-v\fR]
+ [
+ | [\fB\-4\fR]
+ | [\fB\-6\fR]
+ ]
+ [\fB\-m\fR]
+ [\fB\-b\ \fR\fB\fIaddress\fR\fR]
+ [\fB\-p\ \fR\fB\fIport#\fR\fR]
+ [\fB\-c\ \fR\fB\fIclass\fR\fR]
+ [\fB\-t\ \fR\fB\fItype\fR\fR]
+ [\fB\-i\fR]
+ [\fB\-x\ \fR\fB\fIaddr\fR\fR]
+ [plusopt...]
+ .HP \w'\fBmdig\fR\ 'u
+ \fBmdig\fR
+ {\-h}
+ .HP \w'\fBmdig\fR\ 'u
+ \fBmdig\fR
+ [@server]
+ {global\-opt...}
+ {{local\-opt...}\ {query}...}
+ .SH "DESCRIPTION"
+ .PP
\fBmdig\fR
is a multiple/pipelined query version of
\fBdig\fR: instead of waiting for a response after sending each query, it begins by sending all queries\&. Responses are displayed in the order in which they are received, not in the order the corresponding queries were sent\&.
-.PP
+ .PP
\fBmdig\fR
options are a subset of the
\fBdig\fR
options, and are divided into "anywhere options" which can occur anywhere, "global options" which must occur before the query name (or they are ignored with a warning), and "local options" which apply to the next query on the command line\&.
-.PP
+ .PP
The
{@server}
option is a mandatory global option\&. It is the name or IP address of the name server to query\&. (Unlike
argument is a hostname,
\fBmdig\fR
resolves that name before querying the name server\&.
-.PP
+ .PP
\fBmdig\fR
provides a number of query options which affect the way in which lookups are made and the results displayed\&. Some of these set or reset flag bits in the query header, some determine which sections of the answer get printed, and others determine the timeout and retry strategies\&.
-.PP
+ .PP
Each query option is identified by a keyword preceded by a plus sign (+)\&. Some keywords set or reset an option\&. These may be preceded by the string
no
to negate the meaning of that keyword\&. Other keywords assign values to options like the timeout interval\&. They have the form
\fB+keyword=value\fR\&.
-.SH "ANYWHERE OPTIONS"
-.PP
+ .SH "ANYWHERE OPTIONS"
+ .PP
The
\fB\-f\fR
option makes
\fIfilename\fR\&. The file contains a number of queries, one per line\&. Each entry in the file should be organized in the same way they would be presented as queries to
\fBmdig\fR
using the command\-line interface\&.
-.PP
+ .PP
The
\fB\-h\fR
causes
\fBmdig\fR
to print the detailed help with the full list of options and exit\&.
-.PP
+ .PP
The
\fB\-v\fR
causes
\fBmdig\fR
to print the version number and exit\&.
-.SH "GLOBAL OPTIONS"
-.PP
+ .SH "GLOBAL OPTIONS"
+ .PP
The
\fB\-4\fR
option forces
\fBmdig\fR
to only use IPv4 query transport\&.
-.PP
+ .PP
The
\fB\-6\fR
option forces
\fBmdig\fR
to only use IPv6 query transport\&.
-.PP
+ .PP
The
\fB\-b\fR
option sets the source IP address of the query to
\fIaddress\fR\&. This must be a valid address on one of the host\*(Aqs network interfaces or "0\&.0\&.0\&.0" or "::"\&. An optional port may be specified by appending "#<port>"
-.PP
+ .PP
The
\fB\-m\fR
option enables memory usage debugging\&.
-.PP
+ .PP
The
\fB\-p\fR
option is used when a non\-standard port number is to be queried\&.
is the port number that
\fBmdig\fR
will send its queries instead of the standard DNS port number 53\&. This option would be used to test a name server that has been configured to listen for queries on a non\-standard port number\&.
-.PP
+ .PP
The global query options are:
-.PP
+ .PP
\fB+[no]additional\fR
.RS 4
-Display [do not display] the additional section of a reply\&. The default is to display it\&.
-.RE
-.PP
+ Display [do not display] the additional section of a reply\&. The default is to display it\&.
+ .RE
+ .PP
\fB+[no]all\fR
.RS 4
-Set or clear all display flags\&.
-.RE
-.PP
+ Set or clear all display flags\&.
+ .RE
+ .PP
\fB+[no]answer\fR
.RS 4
-Display [do not display] the answer section of a reply\&. The default is to display it\&.
-.RE
-.PP
+ Display [do not display] the answer section of a reply\&. The default is to display it\&.
+ .RE
+ .PP
\fB+[no]authority\fR
.RS 4
-Display [do not display] the authority section of a reply\&. The default is to display it\&.
-.RE
-.PP
+ Display [do not display] the authority section of a reply\&. The default is to display it\&.
+ .RE
+ .PP
\fB+[no]besteffort\fR
.RS 4
-Attempt to display the contents of messages which are malformed\&. The default is to not display malformed answers\&.
-.RE
-.PP
+ Attempt to display the contents of messages which are malformed\&. The default is to not display malformed answers\&.
+ .RE
+ .PP
+\fB+burst\fR
+.RS 4
+ This option delays queries until the start of the next second\&.
+ .RE
+ .PP
\fB+[no]cl\fR
.RS 4
-Display [do not display] the CLASS when printing the record\&.
-.RE
-.PP
+ Display [do not display] the CLASS when printing the record\&.
+ .RE
+ .PP
\fB+[no]comments\fR
.RS 4
-Toggle the display of comment lines in the output\&. The default is to print comments\&.
-.RE
-.PP
+ Toggle the display of comment lines in the output\&. The default is to print comments\&.
+ .RE
+ .PP
\fB+[no]continue\fR
.RS 4
-Continue on errors (e\&.g\&. timeouts)\&.
-.RE
-.PP
+ Continue on errors (e\&.g\&. timeouts)\&.
+ .RE
+ .PP
\fB+[no]crypto\fR
.RS 4
-Toggle the display of cryptographic fields in DNSSEC records\&. The contents of these field are unnecessary to debug most DNSSEC validation failures and removing them makes it easier to see the common failures\&. The default is to display the fields\&. When omitted they are replaced by the string "[omitted]" or in the DNSKEY case the key id is displayed as the replacement, e\&.g\&. "[ key id = value ]"\&.
-.RE
-.PP
+ Toggle the display of cryptographic fields in DNSSEC records\&. The contents of these field are unnecessary to debug most DNSSEC validation failures and removing them makes it easier to see the common failures\&. The default is to display the fields\&. When omitted they are replaced by the string "[omitted]" or in the DNSKEY case the key id is displayed as the replacement, e\&.g\&. "[ key id = value ]"\&.
+ .RE
+ .PP
\fB+dscp[=value]\fR
.RS 4
-Set the DSCP code point to be used when sending the query\&. Valid DSCP code points are in the range [0\&.\&.63]\&. By default no code point is explicitly set\&.
-.RE
-.PP
+ Set the DSCP code point to be used when sending the query\&. Valid DSCP code points are in the range [0\&.\&.63]\&. By default no code point is explicitly set\&.
+ .RE
+ .PP
\fB+[no]multiline\fR
.RS 4
-Print records like the SOA records in a verbose multi\-line format with human\-readable comments\&. The default is to print each record on a single line, to facilitate machine parsing of the
+ Print records like the SOA records in a verbose multi\-line format with human\-readable comments\&. The default is to print each record on a single line, to facilitate machine parsing of the
\fBmdig\fR
output\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]question\fR
.RS 4
-Print [do not print] the question section of a query when an answer is returned\&. The default is to print the question section as a comment\&.
-.RE
-.PP
+ Print [do not print] the question section of a query when an answer is returned\&. The default is to print the question section as a comment\&.
+ .RE
+ .PP
\fB+[no]rrcomments\fR
.RS 4
-Toggle the display of per\-record comments in the output (for example, human\-readable key information about DNSKEY records)\&. The default is not to print record comments unless multiline mode is active\&.
-.RE
-.PP
+ Toggle the display of per\-record comments in the output (for example, human\-readable key information about DNSKEY records)\&. The default is not to print record comments unless multiline mode is active\&.
+ .RE
+ .PP
\fB+[no]short\fR
.RS 4
-Provide a terse answer\&. The default is to print the answer in a verbose form\&.
-.RE
-.PP
+ Provide a terse answer\&. The default is to print the answer in a verbose form\&.
+ .RE
+ .PP
\fB+split=W\fR
.RS 4
-Split long hex\- or base64\-formatted fields in resource records into chunks of
+ Split long hex\- or base64\-formatted fields in resource records into chunks of
\fIW\fR
characters (where
\fIW\fR
or
\fI+split=0\fR
causes fields not to be split at all\&. The default is 56 characters, or 44 characters when multiline mode is active\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]tcp\fR
.RS 4
-Use [do not use] TCP when querying name servers\&. The default behavior is to use UDP\&.
-.RE
-.PP
+ Use [do not use] TCP when querying name servers\&. The default behavior is to use UDP\&.
+ .RE
+ .PP
\fB+[no]ttlid\fR
.RS 4
-Display [do not display] the TTL when printing the record\&.
-.RE
-.PP
+ Display [do not display] the TTL when printing the record\&.
+ .RE
+ .PP
\fB+[no]ttlunits\fR
.RS 4
-Display [do not display] the TTL in friendly human\-readable time units of "s", "m", "h", "d", and "w", representing seconds, minutes, hours, days and weeks\&. Implies +ttlid\&.
-.RE
-.PP
+ Display [do not display] the TTL in friendly human\-readable time units of "s", "m", "h", "d", and "w", representing seconds, minutes, hours, days and weeks\&. Implies +ttlid\&.
+ .RE
+ .PP
\fB+[no]vc\fR
.RS 4
-Use [do not use] TCP when querying name servers\&. This alternate syntax to
+ Use [do not use] TCP when querying name servers\&. This alternate syntax to
\fI+[no]tcp\fR
is provided for backwards compatibility\&. The "vc" stands for "virtual circuit"\&.
-.RE
-.SH "LOCAL OPTIONS"
-.PP
+ .RE
+ .SH "LOCAL OPTIONS"
+ .PP
The
\fB\-c\fR
option sets the query class to
\fIclass\fR\&. It can be any valid query class which is supported in BIND 9\&. The default query class is "IN"\&.
-.PP
+ .PP
The
\fB\-t\fR
option sets the query type to
\fItype\fR\&. It can be any valid query type which is supported in BIND 9\&. The default query type is "A", unless the
\fB\-x\fR
option is supplied to indicate a reverse lookup with the "PTR" query type\&.
-.PP
+ .PP
The
\fB\-i\fR
option sets the reverse domain for IPv6 addresses to IP6\&.INT\&.
-.PP
+ .PP
Reverse lookups \(em mapping addresses to names \(em are simplified by the
\fB\-x\fR
option\&.
and sets the query type and class to PTR and IN respectively\&. By default, IPv6 addresses are looked up using nibble format under the IP6\&.ARPA domain\&. To use the older RFC1886 method using the IP6\&.INT domain specify the
\fB\-i\fR
option\&.
-.PP
+ .PP
The local query options are:
-.PP
+ .PP
\fB+[no]aaflag\fR
.RS 4
-A synonym for
+ A synonym for
\fI+[no]aaonly\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]aaonly\fR
.RS 4
-Sets the "aa" flag in the query\&.
-.RE
-.PP
+ Sets the "aa" flag in the query\&.
+ .RE
+ .PP
\fB+[no]adflag\fR
.RS 4
-Set [do not set] the AD (authentic data) bit in the query\&. This requests the server to return whether all of the answer and authority sections have all been validated as secure according to the security policy of the server\&. AD=1 indicates that all records have been validated as secure and the answer is not from a OPT\-OUT range\&. AD=0 indicate that some part of the answer was insecure or not validated\&. This bit is set by default\&.
-.RE
-.PP
+ Set [do not set] the AD (authentic data) bit in the query\&. This requests the server to return whether all of the answer and authority sections have all been validated as secure according to the security policy of the server\&. AD=1 indicates that all records have been validated as secure and the answer is not from a OPT\-OUT range\&. AD=0 indicate that some part of the answer was insecure or not validated\&. This bit is set by default\&.
+ .RE
+ .PP
\fB+bufsize=B\fR
.RS 4
-Set the UDP message buffer size advertised using EDNS0 to
+ Set the UDP message buffer size advertised using EDNS0 to
\fIB\fR
bytes\&. The maximum and minimum sizes of this buffer are 65535 and 0 respectively\&. Values outside this range are rounded up or down appropriately\&. Values other than zero will cause a EDNS query to be sent\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]cdflag\fR
.RS 4
-Set [do not set] the CD (checking disabled) bit in the query\&. This requests the server to not perform DNSSEC validation of responses\&.
-.RE
-.PP
+ Set [do not set] the CD (checking disabled) bit in the query\&. This requests the server to not perform DNSSEC validation of responses\&.
+ .RE
+ .PP
\fB+[no]cookie\fR\fB[=####]\fR
.RS 4
-Send a COOKIE EDNS option, with optional value\&. Replaying a COOKIE from a previous response will allow the server to identify a previous client\&. The default is
+ Send a COOKIE EDNS option, with optional value\&. Replaying a COOKIE from a previous response will allow the server to identify a previous client\&. The default is
\fB+nocookie\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]dnssec\fR
.RS 4
-Requests DNSSEC records be sent by setting the DNSSEC OK bit (DO) in the OPT record in the additional section of the query\&.
-.RE
-.PP
+ Requests DNSSEC records be sent by setting the DNSSEC OK bit (DO) in the OPT record in the additional section of the query\&.
+ .RE
+ .PP
\fB+[no]edns[=#]\fR
.RS 4
-Specify the EDNS version to query with\&. Valid values are 0 to 255\&. Setting the EDNS version will cause a EDNS query to be sent\&.
+ Specify the EDNS version to query with\&. Valid values are 0 to 255\&. Setting the EDNS version will cause a EDNS query to be sent\&.
\fB+noedns\fR
clears the remembered EDNS version\&. EDNS is set to 0 by default\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]ednsflags[=#]\fR
.RS 4
-Set the must\-be\-zero EDNS flags bits (Z bits) to the specified value\&. Decimal, hex and octal encodings are accepted\&. Setting a named flag (e\&.g\&. DO) will silently be ignored\&. By default, no Z bits are set\&.
-.RE
-.PP
+ Set the must\-be\-zero EDNS flags bits (Z bits) to the specified value\&. Decimal, hex and octal encodings are accepted\&. Setting a named flag (e\&.g\&. DO) will silently be ignored\&. By default, no Z bits are set\&.
+ .RE
+ .PP
\fB+[no]ednsopt[=code[:value]]\fR
.RS 4
-Specify EDNS option with code point
+ Specify EDNS option with code point
\fBcode\fR
and optionally payload of
\fBvalue\fR
as a hexadecimal string\&.
\fB+noednsopt\fR
clears the EDNS options to be sent\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]expire\fR
.RS 4
-Send an EDNS Expire option\&.
-.RE
-.PP
+ Send an EDNS Expire option\&.
+ .RE
+ .PP
\fB+[no]nsid\fR
.RS 4
-Include an EDNS name server ID request when sending a query\&.
-.RE
-.PP
+ Include an EDNS name server ID request when sending a query\&.
+ .RE
+ .PP
\fB+[no]recurse\fR
.RS 4
-Toggle the setting of the RD (recursion desired) bit in the query\&. This bit is set by default, which means
+ Toggle the setting of the RD (recursion desired) bit in the query\&. This bit is set by default, which means
\fBmdig\fR
normally sends recursive queries\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+retry=T\fR
.RS 4
-Sets the number of times to retry UDP queries to server to
+ Sets the number of times to retry UDP queries to server to
\fIT\fR
instead of the default, 2\&. Unlike
\fI+tries\fR, this does not include the initial query\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+[no]subnet=addr[/prefix\-length]\fR
.RS 4
-Send (don\*(Aqt send) an EDNS Client Subnet option with the specified IP address or network prefix\&.
+ Send (don\*(Aqt send) an EDNS Client Subnet option with the specified IP address or network prefix\&.
.sp
-\fBmdig +subnet=0\&.0\&.0\&.0/0\fR, or simply
+ \fBmdig +subnet=0\&.0\&.0\&.0/0\fR, or simply
\fBmdig +subnet=0\fR
for short, sends an EDNS client\-subnet option with an empty address and a source prefix\-length of zero, which signals a resolver that the client\*(Aqs address information must
\fInot\fR
be used when resolving this query\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+timeout=T\fR
.RS 4
-Sets the timeout for a query to
+ Sets the timeout for a query to
\fIT\fR
seconds\&. The default timeout is 5 seconds for UDP transport and 10 for TCP\&. An attempt to set
\fIT\fR
to less than 1 will result in a query timeout of 1 second being applied\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+tries=T\fR
.RS 4
-Sets the number of times to try UDP queries to server to
+ Sets the number of times to try UDP queries to server to
\fIT\fR
instead of the default, 3\&. If
\fIT\fR
is less than or equal to zero, the number of tries is silently rounded up to 1\&.
-.RE
-.PP
+ .RE
+ .PP
\fB+udptimeout=T\fR
.RS 4
-Sets the timeout between UDP query retries\&.
-.RE
-.PP
+ Sets the timeout between UDP query retries\&.
+ .RE
+ .PP
\fB+[no]unknownformat\fR
.RS 4
-Print all RDATA in unknown RR type presentation format (RFC 3597)\&. The default is to print RDATA for known types in the type\*(Aqs presentation format\&.
-.RE
-.PP
+ Print all RDATA in unknown RR type presentation format (RFC 3597)\&. The default is to print RDATA for known types in the type\*(Aqs presentation format\&.
+ .RE
+ .PP
\fB+[no]zflag\fR
.RS 4
-Set [do not set] the last unassigned DNS header flag in a DNS query\&. This flag is off by default\&.
-.RE
-.SH "SEE ALSO"
-.PP
+ Set [do not set] the last unassigned DNS header flag in a DNS query\&. This flag is off by default\&.
+ .RE
+ .SH "SEE ALSO"
+ .PP
\fBdig\fR(1),
RFC1035\&.
.SH "AUTHOR"
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>mdig</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.mdig"></a><div class="titlepage"></div>
answers.
</p>
</dd>
+<dt><span class="term"><code class="option">+burst</code></span></dt>
+<dd>
+ This option delays queries until the start of the next second.
+ </dd>
<dt><span class="term"><code class="option">+[no]cl</code></span></dt>
<dd>
<p>
'\" t
.\" Title: named-journalprint
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2009-12-04
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
named-journalprint \- print zone journal in human\-readable form
-.SH "SYNOPSIS"
-.HP \w'\fBnamed\-journalprint\fR\ 'u
-\fBnamed\-journalprint\fR {\fIjournal\fR}
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBnamed\-journalprint\fR\ 'u
+ \fBnamed\-journalprint\fR
+ {\fIjournal\fR}
+ .SH "DESCRIPTION"
+ .PP
\fBnamed\-journalprint\fR
prints the contents of a zone journal file in a human\-readable form\&.
-.PP
+ .PP
Journal files are automatically created by
\fBnamed\fR
when changes are made to dynamic zones (e\&.g\&., by
\fBnsupdate\fR)\&. They record each addition or deletion of a resource record, in binary format, allowing the changes to be re\-applied to the zone when the server is restarted after a shutdown or crash\&. By default, the name of the journal file is formed by appending the extension
\&.jnl
to the name of the corresponding zone file\&.
-.PP
+ .PP
\fBnamed\-journalprint\fR
converts the contents of a given journal file into a human\-readable text format\&. Each line begins with "add" or "del", to indicate whether the record was added or deleted, and continues with the resource record in master\-file format\&.
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBnamed\fR(8),
\fBnsupdate\fR(1),
BIND 9 Administrator Reference Manual\&.
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>named-journalprint</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.named-journalprint"></a><div class="titlepage"></div>
'\" t
.\" Title: named-nzd2nzf
.\" Author: [see the "AUTHOR" section]
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: May 5, 2016
.\" Manual: BIND9
.\" Source: BIND9
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
named-nzd2nzf \- Convert an NZD database to NZF text format
-.SH "SYNOPSIS"
-.HP \w'\fBnamed\-nzd2nzf\fR\ 'u
-\fBnamed\-nzd2nzf\fR {filename}
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBnamed\-nzd2nzf\fR\ 'u
+ \fBnamed\-nzd2nzf\fR
+ {filename}
+ .SH "DESCRIPTION"
+ .PP
\fBnamed\-nzd2nzf\fR
converts an NZD database to NZF format and prints it to standard output\&. This can be used to review the configuration of zones that were added to
\fBnamed\fR
via
\fBrndc addzone\fR\&. It can also be used to restore the old file format when rolling back from a newer version of BIND to an older version\&.
-.SH "ARGUMENTS"
-.PP
+ .SH "ARGUMENTS"
+ .PP
filename
.RS 4
-The name of the
+ The name of the
\&.nzd
file whose contents should be printed\&.
-.RE
-.SH "SEE ALSO"
-.PP
+ .RE
+ .SH "SEE ALSO"
+ .PP
BIND 9 Administrator Reference Manual
-.SH "AUTHOR"
-.PP
+ .SH "AUTHOR"
+ .PP
Internet Systems Consortium
.SH "COPYRIGHT"
.br
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>named-nzd2nzf</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.named-nzd2nzf"></a><div class="titlepage"></div>
'\" t
.\" Title: named-rrchecker
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2013-11-12
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
named-rrchecker \- syntax checker for individual DNS resource records
-.SH "SYNOPSIS"
-.HP \w'\fBnamed\-rrchecker\fR\ 'u
-\fBnamed\-rrchecker\fR [\fB\-h\fR] [\fB\-o\ \fR\fB\fIorigin\fR\fR] [\fB\-p\fR] [\fB\-u\fR] [\fB\-C\fR] [\fB\-T\fR] [\fB\-P\fR]
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBnamed\-rrchecker\fR\ 'u
+ \fBnamed\-rrchecker\fR
+ [\fB\-h\fR]
+ [\fB\-o\ \fR\fB\fIorigin\fR\fR]
+ [\fB\-p\fR]
+ [\fB\-u\fR]
+ [\fB\-C\fR]
+ [\fB\-T\fR]
+ [\fB\-P\fR]
+ .SH "DESCRIPTION"
+ .PP
\fBnamed\-rrchecker\fR
read a individual DNS resource record from standard input and checks if it is syntactically correct\&.
-.PP
+ .PP
The
\fB\-h\fR
prints out the help menu\&.
-.PP
+ .PP
The
\fB\-o \fR\fB\fIorigin\fR\fR
option specifies a origin to be used when interpreting the record\&.
-.PP
+ .PP
The
\fB\-p\fR
prints out the resulting record in canonical form\&. If there is no canonical form defined then the record will be printed in unknown record format\&.
-.PP
+ .PP
The
\fB\-u\fR
prints out the resulting record in unknown record form\&.
-.PP
+ .PP
The
\fB\-C\fR,
\fB\-T\fR
and
\fB\-P\fR
print out the known class, standard type and private type mnemonics respectively\&.
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
RFC 1034,
RFC 1035,
\fBnamed\fR(8)
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>named-rrchecker</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.named-rrchecker"></a><div class="titlepage"></div>
'\" t
.\" Title: nsec3hash
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2009-03-02
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
nsec3hash \- generate NSEC3 hash
-.SH "SYNOPSIS"
-.HP \w'\fBnsec3hash\fR\ 'u
-\fBnsec3hash\fR {\fIsalt\fR} {\fIalgorithm\fR} {\fIiterations\fR} {\fIdomain\fR}
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBnsec3hash\fR\ 'u
+ \fBnsec3hash\fR
+ {\fIsalt\fR}
+ {\fIalgorithm\fR}
+ {\fIiterations\fR}
+ {\fIdomain\fR}
+ .SH "DESCRIPTION"
+ .PP
\fBnsec3hash\fR
generates an NSEC3 hash based on a set of NSEC3 parameters\&. This can be used to check the validity of NSEC3 records in a signed zone\&.
-.SH "ARGUMENTS"
-.PP
+ .SH "ARGUMENTS"
+ .PP
salt
.RS 4
-The salt provided to the hash algorithm\&.
-.RE
-.PP
+ The salt provided to the hash algorithm\&.
+ .RE
+ .PP
algorithm
.RS 4
-A number indicating the hash algorithm\&. Currently the only supported hash algorithm for NSEC3 is SHA\-1, which is indicated by the number 1; consequently "1" is the only useful value for this argument\&.
-.RE
-.PP
+ A number indicating the hash algorithm\&. Currently the only supported hash algorithm for NSEC3 is SHA\-1, which is indicated by the number 1; consequently "1" is the only useful value for this argument\&.
+ .RE
+ .PP
iterations
.RS 4
-The number of additional times the hash should be performed\&.
-.RE
-.PP
+ The number of additional times the hash should be performed\&.
+ .RE
+ .PP
domain
.RS 4
-The domain name to be hashed\&.
-.RE
-.SH "SEE ALSO"
-.PP
+ The domain name to be hashed\&.
+ .RE
+ .SH "SEE ALSO"
+ .PP
BIND 9 Administrator Reference Manual,
RFC 5155\&.
.SH "AUTHOR"
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>nsec3hash</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.nsec3hash"></a><div class="titlepage"></div>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Chapter 1. Introduction</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
</p>
<div class="informaltable">
- <table border="1">
+ <table class="informaltable" border="1">
<colgroup>
<col width="3.000in" class="1">
<col width="2.625in" class="2">
The following conventions are used in descriptions of the
<acronym class="acronym">BIND</acronym> configuration file:</p>
<div class="informaltable">
- <table border="1">
+ <table class="informaltable" border="1">
<colgroup>
<col width="3.000in" class="1">
<col width="2.625in" class="2">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Chapter 2. BIND Resource Requirements</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch01.html" title="Chapter 1. Introduction">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Chapter 3. Name Server Configuration</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch02.html" title="Chapter 2. BIND Resource Requirements">
</p>
<div class="informaltable">
- <table border="1">
+ <table class="informaltable" border="1">
<colgroup>
<col width="0.875in" class="1">
<col width="0.500in" class="2">
be sent using the <span class="command"><strong>kill</strong></span> command.
</p>
<div class="informaltable">
- <table border="1">
+ <table class="informaltable" border="1">
<colgroup>
<col width="1.125in" class="1">
<col width="4.000in" class="2">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Chapter 4. Advanced DNS Features</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch03.html" title="Chapter 3. Name Server Configuration">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Chapter 5. The BIND 9 Lightweight Resolver</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch04.html" title="Chapter 4. Advanced DNS Features">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Chapter 6. BIND 9 Configuration Reference</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch05.html" title="Chapter 5. The BIND 9 Lightweight Resolver">
file documentation:
</p>
<div class="informaltable">
- <table border="1">
+ <table class="informaltable" border="1">
<colgroup>
<col width="1.855in" class="1">
<col width="3.770in" class="2">
</p>
<div class="informaltable">
- <table border="1">
+ <table class="informaltable" border="1">
<colgroup>
<col width="1.336in" class="1">
<col width="3.778in" class="2">
</p>
<div class="informaltable">
- <table border="1">
+ <table class="informaltable" border="1">
<colgroup>
<col width="1.130in" class="1">
<col width="4.000in" class="2">
categories may be added in future <acronym class="acronym">BIND</acronym> releases.
</p>
<div class="informaltable">
- <table border="1">
+ <table class="informaltable" border="1">
<colgroup>
<col width="1.150in" class="1">
<col width="3.350in" class="2">
</p>
<div class="informaltable">
- <table border="1">
+ <table class="informaltable" border="1">
<colgroup>
<col width="1.150in" class="1">
<col width="3.350in" class="2">
</p>
<div class="informaltable">
- <table border="1">
+ <table class="informaltable" border="1">
<colgroup>
<col width="1.150in" class="1">
<col width="1.150in" class="2">
</p>
<div class="informaltable">
- <table border="1">
+ <table class="informaltable" border="1">
<colgroup>
<col>
<col>
</div>
<div class="informaltable">
- <table border="1">
+ <table class="informaltable" border="1">
<colgroup>
<col class="1">
<col class="2">
<code class="varname">6to4-self</code>, and <code class="varname">external</code>.
</p>
<div class="informaltable">
- <table border="1">
+ <table class="informaltable" border="1">
<colgroup>
<col width="0.819in" class="1">
<col width="3.681in" class="2">
The components of a Resource Record are:
</p>
<div class="informaltable">
- <table border="1">
+ <table class="informaltable" border="1">
<colgroup>
<col width="1.000in" class="1">
<col width="3.500in" class="2">
are currently valid in the DNS:
</p>
<div class="informaltable">
-<table border="1">
+<table class="informaltable" border="1">
<colgroup>
<col width="0.875in" class="1">
<col width="3.625in" class="2">
For example, the RRs carried in a message might be shown as:
</p>
<div class="informaltable">
-<table border="1">
+<table class="informaltable" border="1">
<colgroup>
<col width="1.381in" class="1">
<col width="1.020in" class="2">
Here is another possible example:
</p>
<div class="informaltable">
-<table border="1">
+<table class="informaltable" border="1">
<colgroup>
<col width="1.491in" class="1">
<col width="1.067in" class="2">
For example:
</p>
<div class="informaltable">
- <table border="1">
+ <table class="informaltable" border="1">
<colgroup>
<col width="1.708in" class="1">
<col width="0.444in" class="2">
used in a zone file.
</p>
<div class="informaltable">
- <table border="1">
+ <table class="informaltable" border="1">
<colgroup>
<col width="0.750in" class="1">
<col width="4.375in" class="2">
in the [<span class="optional">example.com</span>] domain:
</p>
<div class="informaltable">
- <table border="1">
+ <table class="informaltable" border="1">
<colgroup>
<col width="1.125in" class="1">
<col width="4.000in" class="2">
</pre>
<div class="informaltable">
- <table border="1">
+ <table class="informaltable" border="1">
<colgroup>
<col width="0.875in" class="1">
<col width="4.250in" class="2">
</p>
<div class="informaltable">
- <table border="1">
+ <table class="informaltable" border="1">
<colgroup>
<col width="3.300in" class="1">
<col width="2.625in" class="2">
<a name="stats_counters"></a>Name Server Statistics Counters</h4></div></div></div>
<div class="informaltable">
- <table border="1">
+ <table class="informaltable" border="1">
<colgroup>
<col width="1.150in" class="1">
<col width="1.150in" class="2">
<a name="zone_stats"></a>Zone Maintenance Statistics Counters</h4></div></div></div>
<div class="informaltable">
- <table border="1">
+ <table class="informaltable" border="1">
<colgroup>
<col width="1.150in" class="1">
<col width="3.350in" class="2">
<a name="resolver_stats"></a>Resolver Statistics Counters</h4></div></div></div>
<div class="informaltable">
- <table border="1">
+ <table class="informaltable" border="1">
<colgroup>
<col width="1.150in" class="1">
<col width="1.150in" class="2">
</p>
<div class="informaltable">
- <table border="1">
+ <table class="informaltable" border="1">
<colgroup>
<col width="1.150in" class="1">
<col width="3.350in" class="2">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Chapter 7. BIND 9 Security Considerations</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch06.html" title="Chapter 6. BIND 9 Configuration Reference">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Chapter 8. Troubleshooting</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch07.html" title="Chapter 7. BIND 9 Security Considerations">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Appendix A. Release Notes</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch08.html" title="Chapter 8. Troubleshooting">
<div class="toc">
<p><b>Table of Contents</b></p>
<dl class="toc">
-<dt><span class="section"><a href="Bv9ARM.ch09.html#id-1.10.2">Release Notes for BIND Version 9.11.24</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch09.html#id-1.10.2">Release Notes for BIND Version 9.11.25</a></span></dt>
<dd><dl>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_intro">Introduction</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_download">Download</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_license">License Change</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes-9.11.25">Notes for BIND 9.11.25</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes-9.11.24">Notes for BIND 9.11.24</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes-9.11.23">Notes for BIND 9.11.23</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes-9.11.22">Notes for BIND 9.11.22</a></span></dt>
</div>
<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id-1.10.2"></a>Release Notes for BIND Version 9.11.24</h2></div></div></div>
+<a name="id-1.10.2"></a>Release Notes for BIND Version 9.11.25</h2></div></div></div>
<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<div class="section">
<div class="titlepage"><div><div><h3 class="title">
+<a name="relnotes-9.11.25"></a>Notes for BIND 9.11.25</h3></div></div></div>
+
+ <div class="section">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="relnotes-9.11.25-bugs"></a>Bug Fixes</h4></div></div></div>
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+ <p>
+ <span class="command"><strong>named</strong></span> acting as a resolver could incorrectly treat
+ signed zones with no DS record at the parent as bogus. Such zones
+ should be treated as insecure. This has been fixed. [GL #2236]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ After a Negative Trust Anchor (NTA) is added, BIND performs periodic
+ checks to see if it is still necessary. If BIND encountered a failure
+ while creating a query to perform such a check, it attempted to
+ dereference a NULL pointer, resulting in a crash. [GL #2244]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ A problem obtaining glue records could prevent a stub zone from
+ functioning properly, if the authoritative server for the zone were
+ configured for minimal responses. [GL #1736]
+ </p>
+ </li>
+</ul></div>
+ </div>
+
+</div>
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
<a name="relnotes-9.11.24"></a>Notes for BIND 9.11.24</h3></div></div></div>
<div class="section">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Appendix B. A Brief History of the DNS and BIND</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch09.html" title="Appendix A. Release Notes">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Appendix C. General DNS Reference Information</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch10.html" title="Appendix B. A Brief History of the DNS and BIND">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Appendix D. BIND 9 DNS Library Support</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch11.html" title="Appendix C. General DNS Reference Information">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Manual pages</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch12.html" title="Appendix D. BIND 9 DNS Library Support">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>BIND 9 Administrator Reference Manual</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="next" href="Bv9ARM.ch01.html" title="Chapter 1. Introduction">
</head>
<div>
<div><h1 class="title">
<a name="id-1"></a>BIND 9 Administrator Reference Manual</h1></div>
-<div><p class="releaseinfo">BIND Version 9.11.24</p></div>
+<div><p class="releaseinfo">BIND Version 9.11.25</p></div>
<div><p class="copyright">Copyright © 2000-2020 Internet Systems Consortium, Inc. ("ISC")</p></div>
</div>
<hr>
</dl></dd>
<dt><span class="appendix"><a href="Bv9ARM.ch09.html">A. Release Notes</a></span></dt>
<dd><dl>
-<dt><span class="section"><a href="Bv9ARM.ch09.html#id-1.10.2">Release Notes for BIND Version 9.11.24</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch09.html#id-1.10.2">Release Notes for BIND Version 9.11.25</a></span></dt>
<dd><dl>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_intro">Introduction</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_download">Download</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes_license">License Change</a></span></dt>
+<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes-9.11.25">Notes for BIND 9.11.25</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes-9.11.24">Notes for BIND 9.11.24</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes-9.11.23">Notes for BIND 9.11.23</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch09.html#relnotes-9.11.22">Notes for BIND 9.11.22</a></span></dt>
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>arpaname</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="Bv9ARM.ch13.html" title="Manual pages">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>ddns-confgen</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.arpaname.html" title="arpaname">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>delv</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.ddns-confgen.html" title="ddns-confgen">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dig</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.delv.html" title="delv">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-checkds</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dig.html" title="dig">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-coverage</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnssec-checkds.html" title="dnssec-checkds">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-dsfromkey</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnssec-coverage.html" title="dnssec-coverage">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-importkey</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnssec-dsfromkey.html" title="dnssec-dsfromkey">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-keyfromlabel</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnssec-importkey.html" title="dnssec-importkey">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-keygen</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnssec-keyfromlabel.html" title="dnssec-keyfromlabel">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-keymgr</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnssec-keygen.html" title="dnssec-keygen">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-revoke</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnssec-keymgr.html" title="dnssec-keymgr">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-settime</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnssec-revoke.html" title="dnssec-revoke">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-signzone</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnssec-settime.html" title="dnssec-settime">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnssec-verify</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnssec-signzone.html" title="dnssec-signzone">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>dnstap-read</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnssec-verify.html" title="dnssec-verify">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>genrandom</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.dnstap-read.html" title="dnstap-read">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>host</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.genrandom.html" title="genrandom">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>isc-hmac-fixup</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.host.html" title="host">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>lwresd</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.isc-hmac-fixup.html" title="isc-hmac-fixup">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>mdig</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.lwresd.html" title="lwresd">
answers.
</p>
</dd>
+<dt><span class="term"><code class="option">+burst</code></span></dt>
+<dd>
+ This option delays queries until the start of the next second.
+ </dd>
<dt><span class="term"><code class="option">+[no]cl</code></span></dt>
<dd>
<p>
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>named-checkconf</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.mdig.html" title="mdig">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>named-checkzone</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.named-checkconf.html" title="named-checkconf">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>named-journalprint</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.named-checkzone.html" title="named-checkzone">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>named-nzd2nzf</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.named-journalprint.html" title="named-journalprint">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>named-rrchecker</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.named-nzd2nzf.html" title="named-nzd2nzf">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>named.conf</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.named-rrchecker.html" title="named-rrchecker">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>named</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.named.conf.html" title="named.conf">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>nsec3hash</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.named.html" title="named">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>nslookup</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.nsec3hash.html" title="nsec3hash">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>nsupdate</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.nslookup.html" title="nslookup">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>pkcs11-destroy</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.nsupdate.html" title="nsupdate">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>pkcs11-keygen</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.pkcs11-destroy.html" title="pkcs11-destroy">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>pkcs11-list</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.pkcs11-keygen.html" title="pkcs11-keygen">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>pkcs11-tokens</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.pkcs11-list.html" title="pkcs11-list">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>rndc-confgen</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.pkcs11-tokens.html" title="pkcs11-tokens">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>rndc.conf</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.rndc-confgen.html" title="rndc-confgen">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>rndc</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.rndc.conf.html" title="rndc.conf">
</tr>
</table>
</div>
-<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.24 (Extended Support Version)</p>
+<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.25 (Extended Support Version)</p>
</body>
</html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title></title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="article">
<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id-1.2"></a>Release Notes for BIND Version 9.11.24</h2></div></div></div>
+<a name="id-1.2"></a>Release Notes for BIND Version 9.11.25</h2></div></div></div>
<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<div class="section">
<div class="titlepage"><div><div><h3 class="title">
+<a name="relnotes-9.11.25"></a>Notes for BIND 9.11.25</h3></div></div></div>
+
+ <div class="section">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="relnotes-9.11.25-bugs"></a>Bug Fixes</h4></div></div></div>
+ <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">
+ <p>
+ <span class="command"><strong>named</strong></span> acting as a resolver could incorrectly treat
+ signed zones with no DS record at the parent as bogus. Such zones
+ should be treated as insecure. This has been fixed. [GL #2236]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ After a Negative Trust Anchor (NTA) is added, BIND performs periodic
+ checks to see if it is still necessary. If BIND encountered a failure
+ while creating a query to perform such a check, it attempted to
+ dereference a NULL pointer, resulting in a crash. [GL #2244]
+ </p>
+ </li>
+<li class="listitem">
+ <p>
+ A problem obtaining glue records could prevent a stub zone from
+ functioning properly, if the authoritative server for the zone were
+ configured for minimal responses. [GL #1736]
+ </p>
+ </li>
+</ul></div>
+ </div>
+
+</div>
+ <div class="section">
+<div class="titlepage"><div><div><h3 class="title">
<a name="relnotes-9.11.24"></a>Notes for BIND 9.11.24</h3></div></div></div>
<div class="section">
-Release Notes for BIND Version 9.11.24
+Release Notes for BIND Version 9.11.25
Introduction
or who wish to discuss how to comply with the license may contact ISC at
https://www.isc.org/mission/contact/.
+Notes for BIND 9.11.25
+
+Bug Fixes
+
+ • named acting as a resolver could incorrectly treat signed zones with
+ no DS record at the parent as bogus. Such zones should be treated as
+ insecure. This has been fixed. [GL #2236]
+
+ • After a Negative Trust Anchor (NTA) is added, BIND performs periodic
+ checks to see if it is still necessary. If BIND encountered a failure
+ while creating a query to perform such a check, it attempted to
+ dereference a NULL pointer, resulting in a crash. [GL #2244]
+
+ • A problem obtaining glue records could prevent a stub zone from
+ functioning properly, if the authoritative server for the zone were
+ configured for minimal responses. [GL #1736]
+
Notes for BIND 9.11.24
Feature Changes
'\" t
.\" Title: isc-config.sh
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2009-02-18
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
isc-config.sh \- Get information about the installed version of ISC BIND
-.SH "SYNOPSIS"
-.HP \w'\fBisc\-config\&.sh\fR\ 'u
-\fBisc\-config\&.sh\fR [\fB\-\-cflags\fR] [\fB\-\-exec\-prefix\fR] [\fB\-\-libs\fR] [\fB\-\-prefix\fR] [\fB\-\-version\fR] [libraries...]
-.SH "DESCRIPTION"
-.PP
+ .SH "SYNOPSIS"
+ .HP \w'\fBisc\-config\&.sh\fR\ 'u
+ \fBisc\-config\&.sh\fR
+ [\fB\-\-cflags\fR]
+ [\fB\-\-exec\-prefix\fR]
+ [\fB\-\-libs\fR]
+ [\fB\-\-prefix\fR]
+ [\fB\-\-version\fR]
+ [libraries...]
+ .SH "DESCRIPTION"
+ .PP
\fBisc\-config\&.sh\fR
prints information related to the installed version of ISC BIND, such as the compiler and linker flags required to compile and link programs that use ISC BIND libraries\&.
-.PP
+ .PP
The optional libraries are used to report specific details for compiling and linking for the listed libraries\&. The allowed choices are:
\fBisc\fR,
\fBisccc\fR,
\fBdns\fR,
\fBlwres\fR, and
\fBbind9\fR\&. Multiple libraries may be listed on the command line\&. (Some libraries require other libraries, so are implied\&.)
-.SH "OPTIONS"
-.PP
+ .SH "OPTIONS"
+ .PP
\-\-cflags
.RS 4
-Prints the compiler command line options required to compile files that use ISC BIND\&. Use the
+ Prints the compiler command line options required to compile files that use ISC BIND\&. Use the
\fBlibraries\fR
command line argument(s) to print additional specific flags to pass to the C compiler\&.
-.RE
-.PP
+ .RE
+ .PP
\-\-exec\-prefix
.RS 4
-Prints the directory prefix used in the ISC BIND installation for architecture dependent files to standard output\&.
-.RE
-.PP
+ Prints the directory prefix used in the ISC BIND installation for architecture dependent files to standard output\&.
+ .RE
+ .PP
\-\-libs
.RS 4
-Prints the linker command line options used to link with the ISC BIND libraries\&. Use the
+ Prints the linker command line options used to link with the ISC BIND libraries\&. Use the
\fBlibraries\fR
command line argument(s) to print additional specific flags\&.
-.RE
-.PP
+ .RE
+ .PP
\-\-prefix
.RS 4
-Prints the directory prefix used in the ISC BIND installation for architecture independent files to standard output\&.
-.RE
-.PP
+ Prints the directory prefix used in the ISC BIND installation for architecture independent files to standard output\&.
+ .RE
+ .PP
\-\-version
.RS 4
-Prints the version of the installed ISC BIND suite\&.
-.RE
-.SH "RETURN VALUES"
-.PP
+ Prints the version of the installed ISC BIND suite\&.
+ .RE
+ .SH "RETURN VALUES"
+ .PP
\fBisc\-config\&.sh\fR
returns an exit status of 1 if invoked with invalid arguments or no arguments at all\&. It returns 0 if information was successfully printed\&.
.SH "AUTHOR"
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>isc-config.sh</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="man.isc-config.sh"></a><div class="titlepage"></div>
# 9.11: 160-169,1100-1199
# 9.12: 1200-1299
LIBINTERFACE = 1112
-LIBREVISION = 0
+LIBREVISION = 1
LIBAGE = 0
# 9.11: 160-169,1100-1199
# 9.12: 1200-1299
LIBINTERFACE = 1107
-LIBREVISION = 2
+LIBREVISION = 3
LIBAGE = 0
'\" t
.\" Title: lwres
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2007-06-18
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
lwres \- introduction to the lightweight resolver library
-.SH "SYNOPSIS"
+ .SH "SYNOPSIS"
.sp
.ft B
.nf
#include <lwres/lwres\&.h>
.fi
.ft
-.SH "DESCRIPTION"
-.PP
+.sp
+ .SH "DESCRIPTION"
+ .PP
The BIND 9 lightweight resolver library is a simple, name service independent stub resolver library\&. It provides hostname\-to\-address and address\-to\-hostname lookup services to applications by transmitting lookup requests to a resolver daemon
\fBlwresd\fR
running on the local host\&. The resolver daemon performs the lookup using the DNS or possibly other name service protocols, and returns the results to the application through the library\&. The library and resolver daemon communicate using a simple UDP\-based protocol\&.
-.SH "OVERVIEW"
-.PP
+ .SH "OVERVIEW"
+ .PP
The lwresd library implements multiple name service APIs\&. The standard
\fBgethostbyname()\fR,
\fBgethostbyaddr()\fR,
which contains macro definitions mapping the standard function names into
lwres_
prefixed ones\&. Operating system vendors who integrate the lwres library into their base distributions should rename the functions in the library proper so that the renaming macros are not needed\&.
-.PP
+ .PP
The library also provides a native API consisting of the functions
\fBlwres_getaddrsbyname()\fR
and
\fBlwres_getnamebyaddr()\fR\&. These may be called by applications that require more detailed control over the lookup process than the standard functions provide\&.
-.PP
+ .PP
In addition to these name service independent address lookup functions, the library implements a new, experimental API for looking up arbitrary DNS resource records, using the
\fBlwres_getaddrsbyname()\fR
function\&.
-.PP
+ .PP
Finally, there is a low\-level API for converting lookup requests and responses to and from raw lwres protocol packets\&. This API can be used by clients requiring nonblocking operation, and is also used when implementing the server side of the lwres protocol, for example in the
\fBlwresd\fR
resolver daemon\&. The use of this low\-level API in clients and servers is outlined in the following sections\&.
-.SH "CLIENT-SIDE LOW-LEVEL API CALL FLOW"
-.PP
+ .SH "CLIENT\-SIDE LOW\-LEVEL API CALL FLOW"
+ .PP
When a client program wishes to make an lwres request using the native low\-level API, it typically performs the following sequence of actions\&.
-.PP
+ .PP
(1) Allocate or use an existing
\fBlwres_packet_t\fR, called
\fIpkt\fR
below\&.
-.PP
+ .PP
(2) Set
\fIpkt\&.recvlength\fR
to the maximum length we will accept\&. This is done so the receiver of our packets knows how large our receive buffer is\&. The "default" is a constant in
lwres\&.h:
\fBLWRES_RECVLENGTH = 4096\fR\&.
-.PP
+ .PP
(3) Set
\fIpkt\&.serial\fR
to a unique serial number\&. This value is echoed back to the application by the remote server\&.
-.PP
+ .PP
(4) Set
\fIpkt\&.pktflags\fR\&. Usually this is set to 0\&.
-.PP
+ .PP
(5) Set
\fIpkt\&.result\fR
to 0\&.
-.PP
+ .PP
(6) Call
\fBlwres_*request_render()\fR, or marshall in the data using the primitives such as
\fBlwres_packet_render()\fR
and storing the packet data\&.
-.PP
+ .PP
(7) Transmit the resulting buffer\&.
-.PP
+ .PP
(8) Call
\fBlwres_*response_parse()\fR
to parse any packets received\&.
-.PP
+ .PP
(9) Verify that the opcode and serial match a request, and process the packet specific information contained in the body\&.
-.SH "SERVER-SIDE LOW-LEVEL API CALL FLOW"
-.PP
+ .SH "SERVER\-SIDE LOW\-LEVEL API CALL FLOW"
+ .PP
When implementing the server side of the lightweight resolver protocol using the lwres library, a sequence of actions like the following is typically involved in processing each request packet\&.
-.PP
+ .PP
Note that the same
\fBlwres_packet_t\fR
is used in both the
and
\fB_render()\fR
calls, with only a few modifications made to the packet header\*(Aqs contents between uses\&. This method is recommended as it keeps the serial, opcode, and other fields correct\&.
-.PP
+ .PP
(1) When a packet is received, call
\fBlwres_*request_parse()\fR
to unmarshall it\&. This returns a
(also called
\fIpkt\fR, below) as well as a data specific type, such as
\fBlwres_gabnrequest_t\fR\&.
-.PP
+ .PP
(2) Process the request in the data specific type\&.
-.PP
+ .PP
(3) Set the
\fIpkt\&.result\fR,
\fIpkt\&.recvlength\fR
will be set up properly\&. Otherwise, the
\fBLWRES_LWPACKETFLAG_RESPONSE\fR
bit should be set\&.
-.PP
+ .PP
(4) Call the data specific rendering function, such as
\fBlwres_gabnresponse_render()\fR\&.
-.PP
+ .PP
(5) Send the resulting packet to the client\&.
-.PP
-.SH "SEE ALSO"
-.PP
+ .PP
+ .SH "SEE ALSO"
+ .PP
\fBlwres_gethostent\fR(3),
\fBlwres_getipnode\fR(3),
\fBlwres_getnameinfo\fR(3),
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>lwres</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="id-1"></a><div class="titlepage"></div>
'\" t
.\" Title: lwres_buffer
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2007-06-18
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
lwres_buffer_init, lwres_buffer_invalidate, lwres_buffer_add, lwres_buffer_subtract, lwres_buffer_clear, lwres_buffer_first, lwres_buffer_forward, lwres_buffer_back, lwres_buffer_getuint8, lwres_buffer_putuint8, lwres_buffer_getuint16, lwres_buffer_putuint16, lwres_buffer_getuint32, lwres_buffer_putuint32, lwres_buffer_putmem, lwres_buffer_getmem \- lightweight resolver buffer management
-.SH "SYNOPSIS"
+ .SH "SYNOPSIS"
.sp
.ft B
.nf
#include <lwres/lwbuffer\&.h>
.fi
.ft
+.sp
.HP \w'void\ lwres_buffer_init('u
.BI "void lwres_buffer_init(lwres_buffer_t\ *" "b" ", void\ *" "base" ", unsigned\ int\ " "length" ");"
.HP \w'void\ lwres_buffer_invalidate('u
.BI "void lwres_buffer_putmem(lwres_buffer_t\ *" "b" ", const\ unsigned\ char\ *" "base" ", unsigned\ int\ " "length" ");"
.HP \w'void\ lwres_buffer_getmem('u
.BI "void lwres_buffer_getmem(lwres_buffer_t\ *" "b" ", unsigned\ char\ *" "base" ", unsigned\ int\ " "length" ");"
-.SH "DESCRIPTION"
-.PP
+ .SH "DESCRIPTION"
+ .PP
These functions provide bounds checked access to a region of memory where data is being read or written\&. They are based on, and similar to, the
isc_buffer_
functions in the ISC library\&.
-.PP
+ .PP
A buffer is a region of memory, together with a set of related subregions\&. The
\fIused region\fR
and the
\fIavailable\fR
region are disjoint, and their union is the buffer\*(Aqs region\&. The used region extends from the beginning of the buffer region to the last used byte\&. The available region extends from one byte greater than the last used byte to the end of the buffer\*(Aqs region\&. The size of the used region can be changed using various buffer commands\&. Initially, the used region is empty\&.
-.PP
+ .PP
The used region is further subdivided into two disjoint regions: the
\fIconsumed region\fR
and the
offset (if any)\&. The
\fIremaining\fR
region the current pointer to the end of the used region\&. The size of the consumed region can be changed using various buffer commands\&. Initially, the consumed region is empty\&.
-.PP
+ .PP
The
\fIactive region\fR
is an (optional) subregion of the remaining region\&. It extends from the current offset to an offset in the remaining region\&. Initially, the active region is empty\&. If the current offset advances beyond the chosen offset, the active region will also be empty\&.
-.PP
+ .PP
.if n \{\
.RS 4
.\}
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
.if n \{\
.RS 4
.\}
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
.if n \{\
.RS 4
.\}
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
\fBlwres_buffer_init()\fR
initializes the
-\fBlwres_buffer_t\fR\fI*b\fR
+\fBlwres_buffer_t\fR
+\fI*b\fR
and associates it with the memory region of size
\fIlength\fR
bytes starting at location
\fIbase\&.\fR
-.PP
+ .PP
\fBlwres_buffer_invalidate()\fR
marks the buffer
\fI*b\fR
as invalid\&. Invalidating a buffer after use is not required, but makes it possible to catch its possible accidental use\&.
-.PP
+ .PP
The functions
\fBlwres_buffer_add()\fR
and
\fBlwres_buffer_subtract()\fR
checks for underflow\&. These functions do not allocate or deallocate memory\&. They just change the value of
\fIused\fR\&.
-.PP
+ .PP
A buffer is re\-initialised by
\fBlwres_buffer_clear()\fR\&. The function sets
\fIused\fR,
and
\fIactive\fR
to zero\&.
-.PP
+ .PP
\fBlwres_buffer_first\fR
makes the consumed region of buffer
\fI*p\fR
empty by setting
\fIcurrent\fR
to zero (the start of the buffer)\&.
-.PP
+ .PP
\fBlwres_buffer_forward()\fR
increases the consumed region of buffer
\fI*b\fR
\fIb\fR\*(Aqs consumed region by
\fIn\fR
bytes and checks for underflow\&.
-.PP
+ .PP
\fBlwres_buffer_getuint8()\fR
reads an unsigned 8\-bit integer from
\fI*b\fR
\fIval\fR
to buffer
\fI*b\fR\&.
-.PP
+ .PP
\fBlwres_buffer_getuint16()\fR
and
\fBlwres_buffer_getuint32()\fR
\fIval\fR
to buffer
\fIb\fR, in network byte order\&.
-.PP
+ .PP
Arbitrary amounts of data are read or written from a lightweight resolver buffer with
\fBlwres_buffer_getmem()\fR
and
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>lwres_buffer</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="id-1"></a><div class="titlepage"></div>
'\" t
.\" Title: lwres_config
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2007-06-18
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
lwres_conf_init, lwres_conf_clear, lwres_conf_parse, lwres_conf_print, lwres_conf_get \- lightweight resolver configuration
-.SH "SYNOPSIS"
+ .SH "SYNOPSIS"
.sp
.ft B
.nf
#include <lwres/lwres\&.h>
.fi
.ft
+.sp
.HP \w'void\ lwres_conf_init('u
.BI "void lwres_conf_init(lwres_context_t\ *" "ctx" ");"
.HP \w'void\ lwres_conf_clear('u
.BI "lwres_result_t lwres_conf_print(lwres_context_t\ *" "ctx" ", FILE\ *" "fp" ");"
.HP \w'lwres_conf_t\ *\ lwres_conf_get('u
.BI "lwres_conf_t * lwres_conf_get(lwres_context_t\ *" "ctx" ");"
-.SH "DESCRIPTION"
-.PP
+ .SH "DESCRIPTION"
+ .PP
\fBlwres_conf_init()\fR
creates an empty
\fBlwres_conf_t\fR
structure for lightweight resolver context
\fIctx\fR\&.
-.PP
+ .PP
\fBlwres_conf_clear()\fR
frees up all the internal memory used by that
\fBlwres_conf_t\fR
structure in resolver context
\fIctx\fR\&.
-.PP
+ .PP
\fBlwres_conf_parse()\fR
opens the file
\fIfilename\fR
\fIctx\fR\*(Aqs
\fBlwres_conf_t\fR
structure\&.
-.PP
+ .PP
\fBlwres_conf_print()\fR
prints the
\fBlwres_conf_t\fR
structure for resolver context
\fIctx\fR
to the
-\fBFILE\fR\fIfp\fR\&.
-.SH "RETURN VALUES"
-.PP
+\fBFILE\fR
+\fIfp\fR\&.
+ .SH "RETURN VALUES"
+ .PP
\fBlwres_conf_parse()\fR
returns
\fBLWRES_R_SUCCESS\fR
if
\fIfilename\fR
could not be opened or contained incorrect resolver statements\&.
-.PP
+ .PP
\fBlwres_conf_print()\fR
returns
\fBLWRES_R_SUCCESS\fR
unless an error occurred when converting the network addresses to a numeric host address string\&. If this happens, the function returns
\fBLWRES_R_FAILURE\fR\&.
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBstdio\fR(3),
\fBresolver\fR(5)\&.
-.SH "FILES"
-.PP
+ .SH "FILES"
+ .PP
/etc/resolv\&.conf
.SH "AUTHOR"
.PP
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>lwres_config</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="id-1"></a><div class="titlepage"></div>
'\" t
.\" Title: lwres_context
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2007-06-18
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
lwres_context_create, lwres_context_destroy, lwres_context_nextserial, lwres_context_initserial, lwres_context_freemem, lwres_context_allocmem, lwres_context_sendrecv \- lightweight resolver context management
-.SH "SYNOPSIS"
+ .SH "SYNOPSIS"
.sp
.ft B
.nf
#include <lwres/lwres\&.h>
.fi
.ft
+.sp
.HP \w'lwres_result_t\ lwres_context_create('u
.BI "lwres_result_t lwres_context_create(lwres_context_t\ **" "contextp" ", void\ *" "arg" ", lwres_malloc_t\ " "malloc_function" ", lwres_free_t\ " "free_function" ");"
.HP \w'lwres_result_t\ lwres_context_destroy('u
.BI "void lwres_context_allocmem(lwres_context_t\ *" "ctx" ", size_t\ " "len" ");"
.HP \w'void\ *\ lwres_context_sendrecv('u
.BI "void * lwres_context_sendrecv(lwres_context_t\ *" "ctx" ", void\ *" "sendbase" ", int\ " "sendlen" ", void\ *" "recvbase" ", int\ " "recvlen" ", int\ *" "recvd_len" ");"
-.SH "DESCRIPTION"
-.PP
+ .SH "DESCRIPTION"
+ .PP
\fBlwres_context_create()\fR
creates a
\fBlwres_context_t\fR
\fBlwres_context_t\fR
pointer must initially be NULL, and is modified to point to the newly created
\fBlwres_context_t\fR\&.
-.PP
+ .PP
When the lightweight resolver needs to perform dynamic memory allocation, it will call
\fImalloc_function\fR
to allocate memory and
are NULL,
\fIarg\fR
is unused and should be passed as NULL\&.
-.PP
+ .PP
Once memory for the structure has been allocated, it is initialized using
\fBlwres_conf_init\fR(3)
and returned via
\fI*contextp\fR\&.
-.PP
+ .PP
\fBlwres_context_destroy()\fR
destroys a
\fBlwres_context_t\fR, closing its socket\&.
\fIcontextp\fR
is a pointer to a pointer to the context that is to be destroyed\&. The pointer will be set to NULL when the context has been destroyed\&.
-.PP
+ .PP
The context holds a serial number that is used to identify resolver request packets and associate responses with the corresponding requests\&. This serial number is controlled using
\fBlwres_context_initserial()\fR
and
\fIserial\fR\&.
\fBlwres_context_nextserial()\fR
increments the serial number and returns the previous value\&.
-.PP
+ .PP
Memory for a lightweight resolver context is allocated and freed using
\fBlwres_context_allocmem()\fR
and
\fIlen\fR
bytes of space starting at location
\fImem\fR\&.
-.PP
+ .PP
\fBlwres_context_sendrecv()\fR
performs I/O for the context
\fIctx\fR\&. Data are read and written from the context\*(Aqs socket\&. It writes data from
\(em typically a lightweight resolver query packet \(em and waits for a reply which is copied to the receive buffer at
\fIrecvbase\fR\&. The number of bytes that were written to this receive buffer is returned in
\fI*recvd_len\fR\&.
-.SH "RETURN VALUES"
-.PP
+ .SH "RETURN VALUES"
+ .PP
\fBlwres_context_create()\fR
returns
\fBLWRES_R_NOMEMORY\fR
could not be allocated,
\fBLWRES_R_SUCCESS\fR
otherwise\&.
-.PP
+ .PP
Successful calls to the memory allocator
\fBlwres_context_allocmem()\fR
return a pointer to the start of the allocated space\&. It returns NULL if memory could not be allocated\&.
-.PP
+ .PP
\fBLWRES_R_SUCCESS\fR
is returned when
\fBlwres_context_sendrecv()\fR
is returned if
\fBlwres_context_sendrecv()\fR
times out waiting for a response\&.
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBlwres_conf_init\fR(3),
\fBmalloc\fR(3),
\fBfree\fR(3)\&.
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>lwres_context</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="id-1"></a><div class="titlepage"></div>
'\" t
.\" Title: lwres_gabn
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2007-06-18
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
lwres_gabnrequest_render, lwres_gabnresponse_render, lwres_gabnrequest_parse, lwres_gabnresponse_parse, lwres_gabnresponse_free, lwres_gabnrequest_free \- lightweight resolver getaddrbyname message handling
-.SH "SYNOPSIS"
+ .SH "SYNOPSIS"
.sp
.ft B
.nf
#include <lwres/lwres\&.h>
.fi
.ft
+.sp
.HP \w'lwres_result_t\ lwres_gabnrequest_render('u
.BI "lwres_result_t lwres_gabnrequest_render(lwres_context_t\ *" "ctx" ", lwres_gabnrequest_t\ *" "req" ", lwres_lwpacket_t\ *" "pkt" ", lwres_buffer_t\ *" "b" ");"
.HP \w'lwres_result_t\ lwres_gabnresponse_render('u
.BI "void lwres_gabnresponse_free(lwres_context_t\ *" "ctx" ", lwres_gabnresponse_t\ **" "structp" ");"
.HP \w'void\ lwres_gabnrequest_free('u
.BI "void lwres_gabnrequest_free(lwres_context_t\ *" "ctx" ", lwres_gabnrequest_t\ **" "structp" ");"
-.SH "DESCRIPTION"
-.PP
+ .SH "DESCRIPTION"
+ .PP
These are low\-level routines for creating and parsing lightweight resolver name\-to\-address lookup request and response messages\&.
-.PP
+ .PP
There are four main functions for the getaddrbyname opcode\&. One render function converts a getaddrbyname request structure \(em
\fBlwres_gabnrequest_t\fR
\(em to the lightweight resolver\*(Aqs canonical format\&. It is complemented by a parse function that converts a packet in this canonical format to a getaddrbyname request structure\&. Another render function converts the getaddrbyname response structure \(em
\fBlwres_gabnresponse_t\fR
\(em to the canonical format\&. This is complemented by a parse function which converts a packet in canonical format to a getaddrbyname response structure\&.
-.PP
+ .PP
These structures are defined in
<lwres/lwres\&.h>\&. They are shown below\&.
-.PP
+ .PP
.if n \{\
.RS 4
.\}
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
.if n \{\
.RS 4
.\}
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
.if n \{\
.RS 4
.\}
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
.if n \{\
.RS 4
.\}
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
\fBlwres_gabnrequest_render()\fR
uses resolver context
\fIctx\fR
performs the same task, except it converts a getaddrbyname response structure
\fBlwres_gabnresponse_t\fR
to the lightweight resolver\*(Aqs canonical format\&.
-.PP
+ .PP
\fBlwres_gabnrequest_parse()\fR
uses context
\fIctx\fR
except it yields a
\fBlwres_gabnresponse_t\fR
structure\&.
-.PP
+ .PP
\fBlwres_gabnresponse_free()\fR
and
\fBlwres_gabnrequest_free()\fR
\fBlwres_gabnrequest_t\fR
structures referenced via
\fIstructp\fR\&. Any memory associated with ancillary buffers and strings for those structures is also discarded\&.
-.SH "RETURN VALUES"
-.PP
+ .SH "RETURN VALUES"
+ .PP
The getaddrbyname opcode functions
\fBlwres_gabnrequest_render()\fR,
-\fBlwres_gabnresponse_render()\fR\fBlwres_gabnrequest_parse()\fR
+\fBlwres_gabnresponse_render()\fR
+\fBlwres_gabnrequest_parse()\fR
and
\fBlwres_gabnresponse_parse()\fR
all return
in the packet header structure
\fBlwres_lwpacket_t\fR
indicate that the packet is not a response to an earlier query\&.
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBlwres_packet\fR(3)
.SH "AUTHOR"
.PP
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>lwres_gabn</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="id-1"></a><div class="titlepage"></div>
'\" t
.\" Title: lwres_gai_strerror
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2007-06-18
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
lwres_gai_strerror \- print suitable error string
-.SH "SYNOPSIS"
+ .SH "SYNOPSIS"
.sp
.ft B
.nf
#include <lwres/netdb\&.h>
.fi
.ft
+.sp
.HP \w'char\ *\ gai_strerror('u
.BI "char * gai_strerror(int\ " "ecode" ");"
-.SH "DESCRIPTION"
-.PP
+ .SH "DESCRIPTION"
+ .PP
\fBlwres_gai_strerror()\fR
returns an error message corresponding to an error code returned by
\fBgetaddrinfo()\fR\&. The following error codes and their meaning are defined in
include/lwres/netdb\&.h\&.
-.PP
+ .PP
\fBEAI_ADDRFAMILY\fR
.RS 4
-address family for hostname not supported
-.RE
-.PP
+ address family for hostname not supported
+ .RE
+ .PP
\fBEAI_AGAIN\fR
.RS 4
-temporary failure in name resolution
-.RE
-.PP
+ temporary failure in name resolution
+ .RE
+ .PP
\fBEAI_BADFLAGS\fR
.RS 4
-invalid value for
+ invalid value for
\fBai_flags\fR
-.RE
-.PP
+ .RE
+ .PP
\fBEAI_FAIL\fR
.RS 4
-non\-recoverable failure in name resolution
-.RE
-.PP
+ non\-recoverable failure in name resolution
+ .RE
+ .PP
\fBEAI_FAMILY\fR
.RS 4
-\fBai_family\fR
+ \fBai_family\fR
not supported
-.RE
-.PP
+ .RE
+ .PP
\fBEAI_MEMORY\fR
.RS 4
-memory allocation failure
-.RE
-.PP
+ memory allocation failure
+ .RE
+ .PP
\fBEAI_NODATA\fR
.RS 4
-no address associated with hostname
-.RE
-.PP
+ no address associated with hostname
+ .RE
+ .PP
\fBEAI_NONAME\fR
.RS 4
-hostname or servname not provided, or not known
-.RE
-.PP
+ hostname or servname not provided, or not known
+ .RE
+ .PP
\fBEAI_SERVICE\fR
.RS 4
-servname not supported for
+ servname not supported for
\fBai_socktype\fR
-.RE
-.PP
+ .RE
+ .PP
\fBEAI_SOCKTYPE\fR
.RS 4
-\fBai_socktype\fR
+ \fBai_socktype\fR
not supported
-.RE
-.PP
+ .RE
+ .PP
\fBEAI_SYSTEM\fR
.RS 4
-system error returned in errno
-.RE
-The message
+ system error returned in errno
+ .RE
+ The message
invalid error code
is returned if
\fIecode\fR
is out of range\&.
-.PP
+ .PP
\fBai_flags\fR,
\fBai_family\fR
and
\fBstruct addrinfo\fR
used by
\fBlwres_getaddrinfo()\fR\&.
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBstrerror\fR(3),
\fBlwres_getaddrinfo\fR(3),
\fBgetaddrinfo\fR(3),
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>lwres_gai_strerror</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="id-1"></a><div class="titlepage"></div>
'\" t
.\" Title: lwres_getaddrinfo
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2007-06-18
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
lwres_getaddrinfo, lwres_freeaddrinfo \- socket address structure to host and service name
-.SH "SYNOPSIS"
+ .SH "SYNOPSIS"
.sp
.ft B
.nf
#include <lwres/netdb\&.h>
.fi
.ft
+.sp
.HP \w'int\ lwres_getaddrinfo('u
.BI "int lwres_getaddrinfo(const\ char\ *" "hostname" ", const\ char\ *" "servname" ", const\ struct\ addrinfo\ *" "hints" ", struct\ addrinfo\ **" "res" ");"
.HP \w'void\ lwres_freeaddrinfo('u
.BI "void lwres_freeaddrinfo(struct\ addrinfo\ *" "ai" ");"
-.PP
+ .PP
If the operating system does not provide a
\fBstruct addrinfo\fR, the following structure is used:
-.PP
+ .PP
.nf
struct addrinfo {
int ai_flags; /* AI_PASSIVE, AI_CANONNAME */
};
.fi
.sp
-.SH "DESCRIPTION"
-.PP
+ .SH "DESCRIPTION"
+ .PP
\fBlwres_getaddrinfo()\fR
is used to get a list of IP addresses and port numbers for host
\fIhostname\fR
\fIservname\fR
is either a decimal port number or a service name as listed in
/etc/services\&.
-.PP
+ .PP
\fIhints\fR
is an optional pointer to a
\fBstruct addrinfo\fR\&. This structure can be used to provide hints concerning the type of socket that the caller supports or wishes to use\&. The caller can supply the following structure elements in
\fI*hints\fR:
-.PP
+ .PP
\fBai_family\fR
.RS 4
-The protocol family that should be used\&. When
+ The protocol family that should be used\&. When
\fBai_family\fR
is set to
\fBPF_UNSPEC\fR, it means the caller will accept any protocol family supported by the operating system\&.
-.RE
-.PP
+ .RE
+ .PP
\fBai_socktype\fR
.RS 4
-denotes the type of socket \(em
+ denotes the type of socket \(em
\fBSOCK_STREAM\fR,
\fBSOCK_DGRAM\fR
or
\(em that is wanted\&. When
\fBai_socktype\fR
is zero the caller will accept any socket type\&.
-.RE
-.PP
+ .RE
+ .PP
\fBai_protocol\fR
.RS 4
-indicates which transport protocol is wanted: IPPROTO_UDP or IPPROTO_TCP\&. If
+ indicates which transport protocol is wanted: IPPROTO_UDP or IPPROTO_TCP\&. If
\fBai_protocol\fR
is zero the caller will accept any protocol\&.
-.RE
-.PP
+ .RE
+ .PP
\fBai_flags\fR
.RS 4
-Flag bits\&. If the
+ Flag bits\&. If the
\fBAI_CANONNAME\fR
bit is set, a successful call to
\fBlwres_getaddrinfo()\fR
\fBIN6ADDR_ANY_INIT\fR
for an IPv6 address\&.
.sp
-When
+ When
\fBai_flags\fR
does not set the
\fBAI_PASSIVE\fR
is not set in
\fBai_flags\fR\&.
.sp
-If
+ If
\fBai_flags\fR
is set to
\fBAI_NUMERICHOST\fR
it indicates that
\fIhostname\fR
should be treated as a numeric string defining an IPv4 or IPv6 address and no name resolution should be attempted\&.
-.RE
-.PP
+ .RE
+ .PP
All other elements of the
\fBstruct addrinfo\fR
passed via
\fIhints\fR
must be zero\&.
-.PP
+ .PP
A
\fIhints\fR
of
initialized to zero with
\fBai_family\fRset to
\fBPF_UNSPEC\fR\&.
-.PP
+ .PP
After a successful call to
\fBlwres_getaddrinfo()\fR,
\fI*res\fR
\fBai_addr\fR
member points to a filled\-in socket address structure of length
\fBai_addrlen\fR\&.
-.PP
+ .PP
All of the information returned by
\fBlwres_getaddrinfo()\fR
is dynamically allocated: the addrinfo structures, and the socket address structures and canonical host name strings pointed to by the
\fBstruct addrinfo\fR
created by a call to
\fBlwres_getaddrinfo()\fR\&.
-.SH "RETURN VALUES"
-.PP
+ .SH "RETURN VALUES"
+ .PP
\fBlwres_getaddrinfo()\fR
returns zero on success or one of the error codes listed in
\fBgai_strerror\fR(3)
and
\fIservname\fR
are
-\fBNULL\fR\fBlwres_getaddrinfo()\fR
+\fBNULL\fR
+\fBlwres_getaddrinfo()\fR
returns
\fBEAI_NONAME\fR\&.
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBlwres\fR(3),
\fBlwres_getaddrinfo\fR(3),
\fBlwres_freeaddrinfo\fR(3),
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>lwres_getaddrinfo</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="id-1"></a><div class="titlepage"></div>
'\" t
.\" Title: lwres_gethostent
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2007-06-18
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
lwres_gethostbyname, lwres_gethostbyname2, lwres_gethostbyaddr, lwres_gethostent, lwres_sethostent, lwres_endhostent, lwres_gethostbyname_r, lwres_gethostbyaddr_r, lwres_gethostent_r, lwres_sethostent_r, lwres_endhostent_r \- lightweight resolver get network host entry
-.SH "SYNOPSIS"
+ .SH "SYNOPSIS"
.sp
.ft B
.nf
#include <lwres/netdb\&.h>
.fi
.ft
+.sp
.HP \w'struct\ hostent\ *\ lwres_gethostbyname('u
.BI "struct hostent * lwres_gethostbyname(const\ char\ *" "name" ");"
.HP \w'struct\ hostent\ *\ lwres_gethostbyname2('u
.BI "void lwres_sethostent_r(int\ " "stayopen" ");"
.HP \w'void\ lwres_endhostent_r('u
.BI "void lwres_endhostent_r(void);"
-.SH "DESCRIPTION"
-.PP
+ .SH "DESCRIPTION"
+ .PP
These functions provide hostname\-to\-address and address\-to\-hostname lookups by means of the lightweight resolver\&. They are similar to the standard
\fBgethostent\fR(3)
functions provided by most operating systems\&. They use a
\fBstruct hostent\fR
which is usually defined in
<namedb\&.h>\&.
-.PP
+ .PP
.if n \{\
.RS 4
.\}
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
The members of this structure are:
-.PP
+ .PP
\fBh_name\fR
.RS 4
-The official (canonical) name of the host\&.
-.RE
-.PP
+ The official (canonical) name of the host\&.
+ .RE
+ .PP
\fBh_aliases\fR
.RS 4
-A NULL\-terminated array of alternate names (nicknames) for the host\&.
-.RE
-.PP
+ A NULL\-terminated array of alternate names (nicknames) for the host\&.
+ .RE
+ .PP
\fBh_addrtype\fR
.RS 4
-The type of address being returned \(em
+ The type of address being returned \(em
\fBPF_INET\fR
or
\fBPF_INET6\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\fBh_length\fR
.RS 4
-The length of the address in bytes\&.
-.RE
-.PP
+ The length of the address in bytes\&.
+ .RE
+ .PP
\fBh_addr_list\fR
.RS 4
-A
+ A
\fBNULL\fR
terminated array of network addresses for the host\&. Host addresses are returned in network byte order\&.
-.RE
-.PP
+ .RE
+ .PP
For backward compatibility with very old software,
\fBh_addr\fR
is the first address in
\fBh_addr_list\&.\fR
-.PP
+ .PP
\fBlwres_gethostent()\fR,
\fBlwres_sethostent()\fR,
\fBlwres_endhostent()\fR,
provide iteration over the known host entries on systems that provide such functionality through facilities like
/etc/hosts
or NIS\&. The lightweight resolver does not currently implement these functions; it only provides them as stub functions that always return failure\&.
-.PP
+ .PP
\fBlwres_gethostbyname()\fR
and
\fBlwres_gethostbyname2()\fR
or
\fBlwres_gethostbyname2()\fR
fail\&.
-.PP
+ .PP
Reverse lookups of addresses are performed by
\fBlwres_gethostbyaddr()\fR\&.
\fIaddr\fR
\fIresbuf\fR, which is a pointer to the
\fBstruct hostent\fR
it created\&.
-.PP
+ .PP
\fBlwres_gethostbyaddr_r()\fR
is a thread\-safe function that performs a reverse lookup of address
\fIaddr\fR
\fIresbuf\fR, which is a pointer to the
\fBstruct hostent()\fR
it created\&.
-.SH "RETURN VALUES"
-.PP
+ .SH "RETURN VALUES"
+ .PP
The functions
\fBlwres_gethostbyname()\fR,
\fBlwres_gethostbyname2()\fR,
\fBlwres_h_errno\fR
will contain one of the following error codes defined in
<lwres/netdb\&.h>:
-.PP
+ .PP
\fBHOST_NOT_FOUND\fR
.RS 4
-The host or address was not found\&.
-.RE
-.PP
+ The host or address was not found\&.
+ .RE
+ .PP
\fBTRY_AGAIN\fR
.RS 4
-A recoverable error occurred, e\&.g\&., a timeout\&. Retrying the lookup may succeed\&.
-.RE
-.PP
+ A recoverable error occurred, e\&.g\&., a timeout\&. Retrying the lookup may succeed\&.
+ .RE
+ .PP
\fBNO_RECOVERY\fR
.RS 4
-A non\-recoverable error occurred\&.
-.RE
-.PP
+ A non\-recoverable error occurred\&.
+ .RE
+ .PP
\fBNO_DATA\fR
.RS 4
-The name exists, but has no address information associated with it (or vice versa in the case of a reverse lookup)\&. The code NO_ADDRESS is accepted as a synonym for NO_DATA for backwards compatibility\&.
-.RE
-.PP
+ The name exists, but has no address information associated with it (or vice versa in the case of a reverse lookup)\&. The code NO_ADDRESS is accepted as a synonym for NO_DATA for backwards compatibility\&.
+ .RE
+ .PP
\fBlwres_hstrerror\fR(3)
translates these error codes to suitable error messages\&.
-.PP
+ .PP
\fBlwres_gethostent()\fR
and
\fBlwres_gethostent_r()\fR
always return
\fBNULL\fR\&.
-.PP
+ .PP
Successful calls to
\fBlwres_gethostbyname_r()\fR
and
\fBerrno\fR
to
\fBERANGE\fR\&.
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBgethostent\fR(3),
\fBlwres_getipnode\fR(3),
\fBlwres_hstrerror\fR(3)
-.SH "BUGS"
-.PP
+ .SH "BUGS"
+ .PP
\fBlwres_gethostbyname()\fR,
\fBlwres_gethostbyname2()\fR,
\fBlwres_gethostbyaddr()\fR
\fBlwres_gethostbyname_r()\fR, and
\fBlwres_gethostbyaddr_r()\fR
respectively\&.
-.PP
+ .PP
The resolver daemon does not currently support any non\-DNS name services such as
/etc/hosts
or
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>lwres_gethostent</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="id-1"></a><div class="titlepage"></div>
'\" t
.\" Title: lwres_getipnode
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2007-06-18
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
lwres_getipnodebyname, lwres_getipnodebyaddr, lwres_freehostent \- lightweight resolver nodename / address translation API
-.SH "SYNOPSIS"
+ .SH "SYNOPSIS"
.sp
.ft B
.nf
#include <lwres/netdb\&.h>
.fi
.ft
+.sp
.HP \w'struct\ hostent\ *\ lwres_getipnodebyname('u
.BI "struct hostent * lwres_getipnodebyname(const\ char\ *" "name" ", int\ " "af" ", int\ " "flags" ", int\ *" "error_num" ");"
.HP \w'struct\ hostent\ *\ lwres_getipnodebyaddr('u
.BI "struct hostent * lwres_getipnodebyaddr(const\ void\ *" "src" ", size_t\ " "len" ", int\ " "af" ", int\ *" "error_num" ");"
.HP \w'void\ lwres_freehostent('u
.BI "void lwres_freehostent(struct\ hostent\ *" "he" ");"
-.SH "DESCRIPTION"
-.PP
+ .SH "DESCRIPTION"
+ .PP
These functions perform thread safe, protocol independent nodename\-to\-address and address\-to\-nodename translation as defined in RFC2553\&.
-.PP
+ .PP
They use a
\fBstruct hostent\fR
which is defined in
namedb\&.h:
-.PP
+ .PP
.if n \{\
.RS 4
.\}
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
The members of this structure are:
-.PP
+ .PP
\fBh_name\fR
.RS 4
-The official (canonical) name of the host\&.
-.RE
-.PP
+ The official (canonical) name of the host\&.
+ .RE
+ .PP
\fBh_aliases\fR
.RS 4
-A NULL\-terminated array of alternate names (nicknames) for the host\&.
-.RE
-.PP
+ A NULL\-terminated array of alternate names (nicknames) for the host\&.
+ .RE
+ .PP
\fBh_addrtype\fR
.RS 4
-The type of address being returned \- usually
+ The type of address being returned \- usually
\fBPF_INET\fR
or
\fBPF_INET6\fR\&.
-.RE
-.PP
+ .RE
+ .PP
\fBh_length\fR
.RS 4
-The length of the address in bytes\&.
-.RE
-.PP
+ The length of the address in bytes\&.
+ .RE
+ .PP
\fBh_addr_list\fR
.RS 4
-A
+ A
\fBNULL\fR
terminated array of network addresses for the host\&. Host addresses are returned in network byte order\&.
-.RE
-.PP
+ .RE
+ .PP
\fBlwres_getipnodebyname()\fR
looks up addresses of protocol family
\fIaf\fR
\fIname\fR\&. The
\fIflags\fR
parameter contains ORed flag bits to specify the types of addresses that are searched for, and the types of addresses that are returned\&. The flag bits are:
-.PP
+ .PP
\fBAI_V4MAPPED\fR
.RS 4
-This is used with an
+ This is used with an
\fIaf\fR
of AF_INET6, and causes IPv4 addresses to be returned as IPv4\-mapped IPv6 addresses\&.
-.RE
-.PP
+ .RE
+ .PP
\fBAI_ALL\fR
.RS 4
-This is used with an
+ This is used with an
\fIaf\fR
of AF_INET6, and causes all known addresses (IPv6 and IPv4) to be returned\&. If AI_V4MAPPED is also set, the IPv4 addresses are return as mapped IPv6 addresses\&.
-.RE
-.PP
+ .RE
+ .PP
\fBAI_ADDRCONFIG\fR
.RS 4
-Only return an IPv6 or IPv4 address if here is an active network interface of that type\&. This is not currently implemented in the BIND 9 lightweight resolver, and the flag is ignored\&.
-.RE
-.PP
+ Only return an IPv6 or IPv4 address if here is an active network interface of that type\&. This is not currently implemented in the BIND 9 lightweight resolver, and the flag is ignored\&.
+ .RE
+ .PP
\fBAI_DEFAULT\fR
.RS 4
-This default sets the
+ This default sets the
\fBAI_V4MAPPED\fR
and
\fBAI_ADDRCONFIG\fR
flag bits\&.
-.RE
-.PP
+ .RE
+ .PP
\fBlwres_getipnodebyaddr()\fR
performs a reverse lookup of address
\fIsrc\fR
\fBPF_INET\fR
or
\fBPF_INET6\fR\&.
-.PP
+ .PP
\fBlwres_freehostent()\fR
releases all the memory associated with the
\fBstruct hostent\fR
is freed, as is the memory for the
\fBhostent\fR
structure itself\&.
-.SH "RETURN VALUES"
-.PP
+ .SH "RETURN VALUES"
+ .PP
If an error occurs,
\fBlwres_getipnodebyname()\fR
and
\fBNULL\fR
pointer\&. The error codes and their meanings are defined in
<lwres/netdb\&.h>:
-.PP
+ .PP
\fBHOST_NOT_FOUND\fR
.RS 4
-No such host is known\&.
-.RE
-.PP
+ No such host is known\&.
+ .RE
+ .PP
\fBNO_ADDRESS\fR
.RS 4
-The server recognised the request and the name but no address is available\&. Another type of request to the name server for the domain might return an answer\&.
-.RE
-.PP
+ The server recognised the request and the name but no address is available\&. Another type of request to the name server for the domain might return an answer\&.
+ .RE
+ .PP
\fBTRY_AGAIN\fR
.RS 4
-A temporary and possibly transient error occurred, such as a failure of a server to respond\&. The request may succeed if retried\&.
-.RE
-.PP
+ A temporary and possibly transient error occurred, such as a failure of a server to respond\&. The request may succeed if retried\&.
+ .RE
+ .PP
\fBNO_RECOVERY\fR
.RS 4
-An unexpected failure occurred, and retrying the request is pointless\&.
-.RE
-.PP
+ An unexpected failure occurred, and retrying the request is pointless\&.
+ .RE
+ .PP
\fBlwres_hstrerror\fR(3)
translates these error codes to suitable error messages\&.
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBRFC2553\fR(),
\fBlwres\fR(3),
\fBlwres_gethostent\fR(3),
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>lwres_getipnode</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="id-1"></a><div class="titlepage"></div>
'\" t
.\" Title: lwres_getnameinfo
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2007-06-18
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
lwres_getnameinfo \- lightweight resolver socket address structure to hostname and service name
-.SH "SYNOPSIS"
+ .SH "SYNOPSIS"
.sp
.ft B
.nf
#include <lwres/netdb\&.h>
.fi
.ft
+.sp
.HP \w'int\ lwres_getnameinfo('u
.BI "int lwres_getnameinfo(const\ struct\ sockaddr\ *" "sa" ", size_t\ " "salen" ", char\ *" "host" ", size_t\ " "hostlen" ", char\ *" "serv" ", size_t\ " "servlen" ", int\ " "flags" ");"
-.SH "DESCRIPTION"
-.PP
+ .SH "DESCRIPTION"
+ .PP
This function is equivalent to the
\fBgetnameinfo\fR(3)
function defined in RFC2133\&.
\fBlwres_getnameinfo()\fR
returns the hostname for the
-\fBstruct sockaddr\fR\fIsa\fR
+\fBstruct sockaddr\fR
+\fIsa\fR
which is
\fIsalen\fR
bytes long\&. The hostname is of length
\fI*host\&.\fR
The maximum length of the hostname is 1025 bytes:
\fBNI_MAXHOST\fR\&.
-.PP
+ .PP
The name of the service associated with the port number in
\fIsa\fR
is returned in
bytes long\&. The maximum length of the service name is
\fBNI_MAXSERV\fR
\- 32 bytes\&.
-.PP
+ .PP
The
\fIflags\fR
argument sets the following bits:
-.PP
+ .PP
\fBNI_NOFQDN\fR
.RS 4
-A fully qualified domain name is not required for local hosts\&. The local part of the fully qualified domain name is returned instead\&.
-.RE
-.PP
+ A fully qualified domain name is not required for local hosts\&. The local part of the fully qualified domain name is returned instead\&.
+ .RE
+ .PP
\fBNI_NUMERICHOST\fR
.RS 4
-Return the address in numeric form, as if calling inet_ntop(), instead of a host name\&.
-.RE
-.PP
+ Return the address in numeric form, as if calling inet_ntop(), instead of a host name\&.
+ .RE
+ .PP
\fBNI_NAMEREQD\fR
.RS 4
-A name is required\&. If the hostname cannot be found in the DNS and this flag is set, a non\-zero error code is returned\&. If the hostname is not found and the flag is not set, the address is returned in numeric form\&.
-.RE
-.PP
+ A name is required\&. If the hostname cannot be found in the DNS and this flag is set, a non\-zero error code is returned\&. If the hostname is not found and the flag is not set, the address is returned in numeric form\&.
+ .RE
+ .PP
\fBNI_NUMERICSERV\fR
.RS 4
-The service name is returned as a digit string representing the port number\&.
-.RE
-.PP
+ The service name is returned as a digit string representing the port number\&.
+ .RE
+ .PP
\fBNI_DGRAM\fR
.RS 4
-Specifies that the service being looked up is a datagram service, and causes getservbyport() to be called with a second argument of "udp" instead of its default of "tcp"\&. This is required for the few ports (512\-514) that have different services for UDP and TCP\&.
-.RE
-.SH "RETURN VALUES"
-.PP
+ Specifies that the service being looked up is a datagram service, and causes getservbyport() to be called with a second argument of "udp" instead of its default of "tcp"\&. This is required for the few ports (512\-514) that have different services for UDP and TCP\&.
+ .RE
+ .SH "RETURN VALUES"
+ .PP
\fBlwres_getnameinfo()\fR
returns 0 on success or a non\-zero error code if an error occurs\&.
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBRFC2133\fR(),
\fBgetservbyport\fR(3),
\fBlwres\fR(3),
\fBlwres_getnameinfo\fR(3),
\fBlwres_getnamebyaddr\fR(3)\&.
\fBlwres_net_ntop\fR(3)\&.
-.SH "BUGS"
-.PP
+ .SH "BUGS"
+ .PP
RFC2133 fails to define what the nonzero return values of
\fBgetnameinfo\fR(3)
are\&.
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>lwres_getnameinfo</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="id-1"></a><div class="titlepage"></div>
'\" t
.\" Title: lwres_getrrsetbyname
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2007-06-18
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
lwres_getrrsetbyname, lwres_freerrset \- retrieve DNS records
-.SH "SYNOPSIS"
+ .SH "SYNOPSIS"
.sp
.ft B
.nf
#include <lwres/netdb\&.h>
.fi
.ft
+.sp
.HP \w'int\ lwres_getrrsetbyname('u
.BI "int lwres_getrrsetbyname(const\ char\ *" "hostname" ", unsigned\ int\ " "rdclass" ", unsigned\ int\ " "rdtype" ", unsigned\ int\ " "flags" ", struct\ rrsetinfo\ **" "res" ");"
.HP \w'void\ lwres_freerrset('u
.BI "void lwres_freerrset(struct\ rrsetinfo\ *" "rrset" ");"
-.PP
+ .PP
The following structures are used:
-.PP
+ .PP
.nf
struct rdatainfo {
unsigned int rdi_length; /* length of data */
unsigned char *rdi_data; /* record data */
};
.fi
-.PP
+.sp
+ .PP
.nf
struct rrsetinfo {
unsigned int rri_flags; /* RRSET_VALIDATED\&.\&.\&. */
};
.fi
.sp
-.SH "DESCRIPTION"
-.PP
+ .SH "DESCRIPTION"
+ .PP
\fBlwres_getrrsetbyname()\fR
gets a set of resource records associated with a
\fIhostname\fR,
is a pointer a to null\-terminated string\&. The
\fIflags\fR
field is currently unused and must be zero\&.
-.PP
+ .PP
After a successful call to
\fBlwres_getrrsetbyname()\fR,
\fI*res\fR
are in uncompressed DNS wire format\&. Properties of the rdataset are represented in the
\fBrri_flags\fR
bitfield\&. If the RRSET_VALIDATED bit is set, the data has been DNSSEC validated and the signatures verified\&.
-.PP
+ .PP
All of the information returned by
\fBlwres_getrrsetbyname()\fR
is dynamically allocated: the
\fBstruct rrset\fR
created by a call to
\fBlwres_getrrsetbyname()\fR\&.
-.PP
-.SH "RETURN VALUES"
-.PP
+ .PP
+ .SH "RETURN VALUES"
+ .PP
\fBlwres_getrrsetbyname()\fR
returns zero on success, and one of the following error codes if an error occurred:
-.PP
+ .PP
\fBERRSET_NONAME\fR
.RS 4
-the name does not exist
-.RE
-.PP
+ the name does not exist
+ .RE
+ .PP
\fBERRSET_NODATA\fR
.RS 4
-the name exists, but does not have data of the desired type
-.RE
-.PP
+ the name exists, but does not have data of the desired type
+ .RE
+ .PP
\fBERRSET_NOMEMORY\fR
.RS 4
-memory could not be allocated
-.RE
-.PP
+ memory could not be allocated
+ .RE
+ .PP
\fBERRSET_INVAL\fR
.RS 4
-a parameter is invalid
-.RE
-.PP
+ a parameter is invalid
+ .RE
+ .PP
\fBERRSET_FAIL\fR
.RS 4
-other failure
-.RE
-.PP
+ other failure
+ .RE
+ .PP
.RS 4
-.RE
-.SH "SEE ALSO"
-.PP
+ .RE
+ .SH "SEE ALSO"
+ .PP
\fBlwres\fR(3)\&.
.SH "AUTHOR"
.PP
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>lwres_getrrsetbyname</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="id-1"></a><div class="titlepage"></div>
'\" t
.\" Title: lwres_gnba
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2007-06-18
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
lwres_gnbarequest_render, lwres_gnbaresponse_render, lwres_gnbarequest_parse, lwres_gnbaresponse_parse, lwres_gnbaresponse_free, lwres_gnbarequest_free \- lightweight resolver getnamebyaddress message handling
-.SH "SYNOPSIS"
+ .SH "SYNOPSIS"
.sp
.ft B
.nf
#include <lwres/lwres\&.h>
.fi
.ft
+.sp
.HP \w'lwres_result_t\ lwres_gnbarequest_render('u
.BI "lwres_result_t lwres_gnbarequest_render(lwres_context_t\ *" "ctx" ", lwres_gnbarequest_t\ *" "req" ", lwres_lwpacket_t\ *" "pkt" ", lwres_buffer_t\ *" "b" ");"
.HP \w'lwres_result_t\ lwres_gnbaresponse_render('u
.BI "void lwres_gnbaresponse_free(lwres_context_t\ *" "ctx" ", lwres_gnbaresponse_t\ **" "structp" ");"
.HP \w'void\ lwres_gnbarequest_free('u
.BI "void lwres_gnbarequest_free(lwres_context_t\ *" "ctx" ", lwres_gnbarequest_t\ **" "structp" ");"
-.SH "DESCRIPTION"
-.PP
+ .SH "DESCRIPTION"
+ .PP
These are low\-level routines for creating and parsing lightweight resolver address\-to\-name lookup request and response messages\&.
-.PP
+ .PP
There are four main functions for the getnamebyaddr opcode\&. One render function converts a getnamebyaddr request structure \(em
\fBlwres_gnbarequest_t\fR
\(em to the lightweight resolver\*(Aqs canonical format\&. It is complemented by a parse function that converts a packet in this canonical format to a getnamebyaddr request structure\&. Another render function converts the getnamebyaddr response structure \(em
\fBlwres_gnbaresponse_t\fR
to the canonical format\&. This is complemented by a parse function which converts a packet in canonical format to a getnamebyaddr response structure\&.
-.PP
+ .PP
These structures are defined in
lwres/lwres\&.h\&. They are shown below\&.
-.PP
+ .PP
.if n \{\
.RS 4
.\}
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
.if n \{\
.RS 4
.\}
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
.if n \{\
.RS 4
.\}
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
\fBlwres_gnbarequest_render()\fR
uses resolver context
\fIctx\fR
performs the same task, except it converts a getnamebyaddr response structure
\fBlwres_gnbaresponse_t\fR
to the lightweight resolver\*(Aqs canonical format\&.
-.PP
+ .PP
\fBlwres_gnbarequest_parse()\fR
uses context
\fIctx\fR
except it yields a
\fBlwres_gnbaresponse_t\fR
structure\&.
-.PP
+ .PP
\fBlwres_gnbaresponse_free()\fR
and
\fBlwres_gnbarequest_free()\fR
\fBlwres_gnbarequest_t\fR
structures referenced via
\fIstructp\fR\&. Any memory associated with ancillary buffers and strings for those structures is also discarded\&.
-.SH "RETURN VALUES"
-.PP
+ .SH "RETURN VALUES"
+ .PP
The getnamebyaddr opcode functions
\fBlwres_gnbarequest_render()\fR,
-\fBlwres_gnbaresponse_render()\fR\fBlwres_gnbarequest_parse()\fR
+\fBlwres_gnbaresponse_render()\fR
+\fBlwres_gnbarequest_parse()\fR
and
\fBlwres_gnbaresponse_parse()\fR
all return
in the packet header structure
\fBlwres_lwpacket_t\fR
indicate that the packet is not a response to an earlier query\&.
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBlwres_packet\fR(3)\&.
.SH "AUTHOR"
.PP
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>lwres_gnba</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="id-1"></a><div class="titlepage"></div>
'\" t
.\" Title: lwres_hstrerror
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2007-06-18
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
lwres_herror, lwres_hstrerror \- lightweight resolver error message generation
-.SH "SYNOPSIS"
+ .SH "SYNOPSIS"
.sp
.ft B
.nf
#include <lwres/netdb\&.h>
.fi
.ft
+.sp
.HP \w'void\ lwres_herror('u
.BI "void lwres_herror(const\ char\ *" "s" ");"
.HP \w'const\ char\ *\ lwres_hstrerror('u
.BI "const char * lwres_hstrerror(int\ " "err" ");"
-.SH "DESCRIPTION"
-.PP
+ .SH "DESCRIPTION"
+ .PP
\fBlwres_herror()\fR
prints the string
\fIs\fR
\fBlwres_hstrerror()\fR
for the error code stored in the global variable
\fBlwres_h_errno\fR\&.
-.PP
+ .PP
\fBlwres_hstrerror()\fR
returns an appropriate string for the error code gievn by
\fIerr\fR\&. The values of the error codes and messages are as follows:
-.PP
+ .PP
\fBNETDB_SUCCESS\fR
.RS 4
-Resolver Error 0 (no error)
-.RE
-.PP
+ Resolver Error 0 (no error)
+ .RE
+ .PP
\fBHOST_NOT_FOUND\fR
.RS 4
-Unknown host
-.RE
-.PP
+ Unknown host
+ .RE
+ .PP
\fBTRY_AGAIN\fR
.RS 4
-Host name lookup failure
-.RE
-.PP
+ Host name lookup failure
+ .RE
+ .PP
\fBNO_RECOVERY\fR
.RS 4
-Unknown server error
-.RE
-.PP
+ Unknown server error
+ .RE
+ .PP
\fBNO_DATA\fR
.RS 4
-No address associated with name
-.RE
-.SH "RETURN VALUES"
-.PP
+ No address associated with name
+ .RE
+ .SH "RETURN VALUES"
+ .PP
The string
Unknown resolver error
is returned by
when the value of
\fBlwres_h_errno\fR
is not a valid error code\&.
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBherror\fR(3),
\fBlwres_hstrerror\fR(3)\&.
.SH "AUTHOR"
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>lwres_hstrerror</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="id-1"></a><div class="titlepage"></div>
'\" t
.\" Title: lwres_inetntop
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2007-06-18
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
lwres_net_ntop \- lightweight resolver IP address presentation
-.SH "SYNOPSIS"
+ .SH "SYNOPSIS"
.sp
.ft B
.nf
#include <lwres/net\&.h>
.fi
.ft
+.sp
.HP \w'const\ char\ *\ lwres_net_ntop('u
.BI "const char * lwres_net_ntop(int\ " "af" ", const\ void\ *" "src" ", char\ *" "dst" ", size_t\ " "size" ");"
-.SH "DESCRIPTION"
-.PP
+ .SH "DESCRIPTION"
+ .PP
\fBlwres_net_ntop()\fR
converts an IP address of protocol family
\fIaf\fR
\(em IPv4 or IPv6 \(em at location
\fIsrc\fR
from network format to its conventional representation as a string\&. For IPv4 addresses, that string would be a dotted\-decimal\&. An IPv6 address would be represented in colon notation as described in RFC1884\&.
-.PP
+ .PP
The generated string is copied to
\fIdst\fR
provided
\fIsize\fR
indicates it is long enough to store the ASCII representation of the address\&.
-.SH "RETURN VALUES"
-.PP
+ .SH "RETURN VALUES"
+ .PP
If successful, the function returns
\fIdst\fR: a pointer to a string containing the presentation format of the address\&.
\fBlwres_net_ntop()\fR
if the protocol family given in
\fIaf\fR
is not supported\&.
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBRFC1884\fR(),
\fBinet_ntop\fR(3),
\fBerrno\fR(3)\&.
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>lwres_inetntop</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="id-1"></a><div class="titlepage"></div>
'\" t
.\" Title: lwres_noop
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2007-06-18
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
lwres_nooprequest_render, lwres_noopresponse_render, lwres_nooprequest_parse, lwres_noopresponse_parse, lwres_noopresponse_free, lwres_nooprequest_free \- lightweight resolver no\-op message handling
-.SH "SYNOPSIS"
+ .SH "SYNOPSIS"
.sp
.ft B
.nf
#include <lwres/lwres\&.h>
.fi
.ft
+.sp
.HP \w'lwres_result_t\ lwres_nooprequest_render('u
.BI "lwres_result_t lwres_nooprequest_render(lwres_context_t\ *" "ctx" ", lwres_nooprequest_t\ *" "req" ", lwres_lwpacket_t\ *" "pkt" ", lwres_buffer_t\ *" "b" ");"
.HP \w'lwres_result_t\ lwres_noopresponse_render('u
.BI "void lwres_noopresponse_free(lwres_context_t\ *" "ctx" ", lwres_noopresponse_t\ **" "structp" ");"
.HP \w'void\ lwres_nooprequest_free('u
.BI "void lwres_nooprequest_free(lwres_context_t\ *" "ctx" ", lwres_nooprequest_t\ **" "structp" ");"
-.SH "DESCRIPTION"
-.PP
+ .SH "DESCRIPTION"
+ .PP
These are low\-level routines for creating and parsing lightweight resolver no\-op request and response messages\&.
-.PP
+ .PP
The no\-op message is analogous to a
\fBping\fR
packet: a packet is sent to the resolver daemon and is simply echoed back\&. The opcode is intended to allow a client to determine if the server is operational or not\&.
-.PP
+ .PP
There are four main functions for the no\-op opcode\&. One render function converts a no\-op request structure \(em
\fBlwres_nooprequest_t\fR
\(em to the lightweight resolver\*(Aqs canonical format\&. It is complemented by a parse function that converts a packet in this canonical format to a no\-op request structure\&. Another render function converts the no\-op response structure \(em
\fBlwres_noopresponse_t\fR
to the canonical format\&. This is complemented by a parse function which converts a packet in canonical format to a no\-op response structure\&.
-.PP
+ .PP
These structures are defined in
lwres/lwres\&.h\&. They are shown below\&.
-.PP
+ .PP
.if n \{\
.RS 4
.\}
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
.if n \{\
.RS 4
.\}
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
.if n \{\
.RS 4
.\}
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
Although the structures have different types, they are identical\&. This is because the no\-op opcode simply echos whatever data was sent: the response is therefore identical to the request\&.
-.PP
+ .PP
\fBlwres_nooprequest_render()\fR
uses resolver context
\fIctx\fR
performs the same task, except it converts a no\-op response structure
\fBlwres_noopresponse_t\fR
to the lightweight resolver\*(Aqs canonical format\&.
-.PP
+ .PP
\fBlwres_nooprequest_parse()\fR
uses context
\fIctx\fR
except it yields a
\fBlwres_noopresponse_t\fR
structure\&.
-.PP
+ .PP
\fBlwres_noopresponse_free()\fR
and
\fBlwres_nooprequest_free()\fR
\fBlwres_nooprequest_t\fR
structures referenced via
\fIstructp\fR\&.
-.SH "RETURN VALUES"
-.PP
+ .SH "RETURN VALUES"
+ .PP
The no\-op opcode functions
\fBlwres_nooprequest_render()\fR,
-\fBlwres_noopresponse_render()\fR\fBlwres_nooprequest_parse()\fR
+\fBlwres_noopresponse_render()\fR
+\fBlwres_nooprequest_parse()\fR
and
\fBlwres_noopresponse_parse()\fR
all return
in the packet header structure
\fBlwres_lwpacket_t\fR
indicate that the packet is not a response to an earlier query\&.
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBlwres_packet\fR(3)
.SH "AUTHOR"
.PP
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>lwres_noop</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="id-1"></a><div class="titlepage"></div>
'\" t
.\" Title: lwres_packet
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2007-06-18
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
lwres_lwpacket_renderheader, lwres_lwpacket_parseheader \- lightweight resolver packet handling functions
-.SH "SYNOPSIS"
+ .SH "SYNOPSIS"
.sp
.ft B
.nf
#include <lwres/lwpacket\&.h>
.fi
.ft
+.sp
.HP \w'lwres_result_t\ lwres_lwpacket_renderheader('u
.BI "lwres_result_t lwres_lwpacket_renderheader(lwres_buffer_t\ *" "b" ", lwres_lwpacket_t\ *" "pkt" ");"
.HP \w'lwres_result_t\ lwres_lwpacket_parseheader('u
.BI "lwres_result_t lwres_lwpacket_parseheader(lwres_buffer_t\ *" "b" ", lwres_lwpacket_t\ *" "pkt" ");"
-.SH "DESCRIPTION"
-.PP
+ .SH "DESCRIPTION"
+ .PP
These functions rely on a
\fBstruct lwres_lwpacket\fR
which is defined in
lwres/lwpacket\&.h\&.
-.PP
+ .PP
.if n \{\
.RS 4
.\}
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
.if n \{\
.RS 4
.\}
.if n \{\
.RE
.\}
-.PP
+.sp
+ .PP
The elements of this structure are:
-.PP
+ .PP
\fBlength\fR
.RS 4
-the overall packet length, including the entire packet header\&. This field is filled in by the lwres_gabn_*() and lwres_gnba_*() calls\&.
-.RE
-.PP
+ the overall packet length, including the entire packet header\&. This field is filled in by the lwres_gabn_*() and lwres_gnba_*() calls\&.
+ .RE
+ .PP
\fBversion\fR
.RS 4
-the header format\&. There is currently only one format,
+ the header format\&. There is currently only one format,
\fBLWRES_LWPACKETVERSION_0\fR\&. This field is filled in by the lwres_gabn_*() and lwres_gnba_*() calls\&.
-.RE
-.PP
+ .RE
+ .PP
\fBpktflags\fR
.RS 4
-library\-defined flags for this packet: for instance whether the packet is a request or a reply\&. Flag values can be set, but not defined by the caller\&. This field is filled in by the application with the exception of the LWRES_LWPACKETFLAG_RESPONSE bit, which is set by the library in the lwres_gabn_*() and lwres_gnba_*() calls\&.
-.RE
-.PP
+ library\-defined flags for this packet: for instance whether the packet is a request or a reply\&. Flag values can be set, but not defined by the caller\&. This field is filled in by the application with the exception of the LWRES_LWPACKETFLAG_RESPONSE bit, which is set by the library in the lwres_gabn_*() and lwres_gnba_*() calls\&.
+ .RE
+ .PP
\fBserial\fR
.RS 4
-is set by the requestor and is returned in all replies\&. If two or more packets from the same source have the same serial number and are from the same source, they are assumed to be duplicates and the latter ones may be dropped\&. This field must be set by the application\&.
-.RE
-.PP
+ is set by the requestor and is returned in all replies\&. If two or more packets from the same source have the same serial number and are from the same source, they are assumed to be duplicates and the latter ones may be dropped\&. This field must be set by the application\&.
+ .RE
+ .PP
\fBopcode\fR
.RS 4
-indicates the operation\&. Opcodes between 0x00000000 and 0x03ffffff are reserved for use by the lightweight resolver library\&. Opcodes between 0x04000000 and 0xffffffff are application defined\&. This field is filled in by the lwres_gabn_*() and lwres_gnba_*() calls\&.
-.RE
-.PP
+ indicates the operation\&. Opcodes between 0x00000000 and 0x03ffffff are reserved for use by the lightweight resolver library\&. Opcodes between 0x04000000 and 0xffffffff are application defined\&. This field is filled in by the lwres_gabn_*() and lwres_gnba_*() calls\&.
+ .RE
+ .PP
\fBresult\fR
.RS 4
-is only valid for replies\&. Results between 0x04000000 and 0xffffffff are application defined\&. Results between 0x00000000 and 0x03ffffff are reserved for library use\&. This field is filled in by the lwres_gabn_*() and lwres_gnba_*() calls\&.
-.RE
-.PP
+ is only valid for replies\&. Results between 0x04000000 and 0xffffffff are application defined\&. Results between 0x00000000 and 0x03ffffff are reserved for library use\&. This field is filled in by the lwres_gabn_*() and lwres_gnba_*() calls\&.
+ .RE
+ .PP
\fBrecvlength\fR
.RS 4
-is the maximum buffer size that the receiver can handle on requests and the size of the buffer needed to satisfy a request when the buffer is too large for replies\&. This field is supplied by the application\&.
-.RE
-.PP
+ is the maximum buffer size that the receiver can handle on requests and the size of the buffer needed to satisfy a request when the buffer is too large for replies\&. This field is supplied by the application\&.
+ .RE
+ .PP
\fBauthtype\fR
.RS 4
-defines the packet level authentication that is used\&. Authorisation types between 0x1000 and 0xffff are application defined and types between 0x0000 and 0x0fff are reserved for library use\&. Currently these are not used and must be zero\&.
-.RE
-.PP
+ defines the packet level authentication that is used\&. Authorisation types between 0x1000 and 0xffff are application defined and types between 0x0000 and 0x0fff are reserved for library use\&. Currently these are not used and must be zero\&.
+ .RE
+ .PP
\fBauthlen\fR
.RS 4
-gives the length of the authentication data\&. Since packet authentication is currently not used, this must be zero\&.
-.RE
-.PP
+ gives the length of the authentication data\&. Since packet authentication is currently not used, this must be zero\&.
+ .RE
+ .PP
The following opcodes are currently defined:
-.PP
+ .PP
\fBNOOP\fR
.RS 4
-Success is always returned and the packet contents are echoed\&. The lwres_noop_*() functions should be used for this type\&.
-.RE
-.PP
+ Success is always returned and the packet contents are echoed\&. The lwres_noop_*() functions should be used for this type\&.
+ .RE
+ .PP
\fBGETADDRSBYNAME\fR
.RS 4
-returns all known addresses for a given name\&. The lwres_gabn_*() functions should be used for this type\&.
-.RE
-.PP
+ returns all known addresses for a given name\&. The lwres_gabn_*() functions should be used for this type\&.
+ .RE
+ .PP
\fBGETNAMEBYADDR\fR
.RS 4
-return the hostname for the given address\&. The lwres_gnba_*() functions should be used for this type\&.
-.RE
-.PP
+ return the hostname for the given address\&. The lwres_gnba_*() functions should be used for this type\&.
+ .RE
+ .PP
\fBlwres_lwpacket_renderheader()\fR
transfers the contents of lightweight resolver packet structure
-\fBlwres_lwpacket_t\fR\fI*pkt\fR
+\fBlwres_lwpacket_t\fR
+\fI*pkt\fR
in network byte order to the lightweight resolver buffer,
\fI*b\fR\&.
-.PP
+ .PP
\fBlwres_lwpacket_parseheader()\fR
performs the converse operation\&. It transfers data in network byte order from buffer
\fI*b\fR
\fIb\fR
should correspond to a
\fBlwres_lwpacket_t\fR\&.
-.SH "RETURN VALUES"
-.PP
+ .SH "RETURN VALUES"
+ .PP
Successful calls to
\fBlwres_lwpacket_renderheader()\fR
and
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>lwres_packet</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="id-1"></a><div class="titlepage"></div>
'\" t
.\" Title: lwres_resutil
.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
+.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 2007-06-18
.\" Manual: BIND9
.\" Source: ISC
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
-.SH "NAME"
+ .SH "NAME"
lwres_string_parse, lwres_addr_parse, lwres_getaddrsbyname, lwres_getnamebyaddr \- lightweight resolver utility functions
-.SH "SYNOPSIS"
+ .SH "SYNOPSIS"
.sp
.ft B
.nf
#include <lwres/lwres\&.h>
.fi
.ft
+.sp
.HP \w'lwres_result_t\ lwres_string_parse('u
.BI "lwres_result_t lwres_string_parse(lwres_buffer_t\ *" "b" ", char\ **" "c" ", uint16_t\ *" "len" ");"
.HP \w'lwres_result_t\ lwres_addr_parse('u
.BI "lwres_result_t lwres_getaddrsbyname(lwres_context_t\ *" "ctx" ", const\ char\ *" "name" ", uint32_t\ " "addrtypes" ", lwres_gabnresponse_t\ **" "structp" ");"
.HP \w'lwres_result_t\ lwres_getnamebyaddr('u
.BI "lwres_result_t lwres_getnamebyaddr(lwres_context_t\ *" "ctx" ", uint32_t\ " "addrtype" ", uint16_t\ " "addrlen" ", const\ unsigned\ char\ *" "addr" ", lwres_gnbaresponse_t\ **" "structp" ");"
-.SH "DESCRIPTION"
-.PP
+ .SH "DESCRIPTION"
+ .PP
\fBlwres_string_parse()\fR
retrieves a DNS\-encoded string starting the current pointer of lightweight resolver buffer
\fIb\fR: i\&.e\&.
\fI*len\fR\&. The buffer\*(Aqs current pointer is advanced to point at the character following the string length, the encoded string, and the trailing
\fBNULL\fR
character\&.
-.PP
+ .PP
\fBlwres_addr_parse()\fR
extracts an address from the buffer
\fIb\fR\&. The buffer\*(Aqs current pointer
indicates the size in bytes of the address that was copied\&.
\fBb\->current\fR
is advanced to point at the next byte of available data in the buffer following the encoded address\&.
-.PP
+ .PP
\fBlwres_getaddrsbyname()\fR
and
\fBlwres_getnamebyaddr()\fR
.if n \{\
.RE
.\}
-.PP
+ .PP
The contents of this structure are not manipulated directly but they are controlled through the
\fBlwres_gabn\fR(3)
functions\&.
-.PP
+ .PP
The lightweight resolver uses
\fBlwres_getaddrsbyname()\fR
to perform forward lookups\&. Hostname
\fBLWRES_ADDRTYPE_V6\fR
for IPv6 addresses\&. Results of the lookup are returned in
\fI*structp\fR\&.
-.PP
+ .PP
\fBlwres_getnamebyaddr()\fR
performs reverse lookups\&. Resolver context
\fIctx\fR
\fIaddrlen\fR
bytes\&. The result of the function call is made available through
\fI*structp\fR\&.
-.SH "RETURN VALUES"
-.PP
+ .SH "RETURN VALUES"
+ .PP
Successful calls to
\fBlwres_string_parse()\fR
and
if the buffer is corrupt or
\fBLWRES_R_UNEXPECTEDEND\fR
if the buffer has less space than expected for the components of the encoded string or address\&.
-.PP
+ .PP
\fBlwres_getaddrsbyname()\fR
returns
\fBLWRES_R_SUCCESS\fR
if the hostname
\fIname\fR
could not be found\&.
-.PP
+ .PP
\fBLWRES_R_SUCCESS\fR
is returned by a successful call to
\fBlwres_getnamebyaddr()\fR\&.
-.PP
+ .PP
Both
\fBlwres_getaddrsbyname()\fR
and
when memory allocation requests fail and
\fBLWRES_R_UNEXPECTEDEND\fR
if the buffers used for sending queries and receiving replies are too small\&.
-.SH "SEE ALSO"
-.PP
+ .SH "SEE ALSO"
+ .PP
\fBlwres_buffer\fR(3),
\fBlwres_gabn\fR(3)\&.
.SH "AUTHOR"
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>lwres_resutil</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry">
<a name="id-1"></a><div class="titlepage"></div>
DESCRIPTION="(Extended Support Version)"
MAJORVER=9
MINORVER=11
-PATCHVER=24
+PATCHVER=25
RELEASETYPE=
RELEASEVER=
EXTENSIONS=
projects / thirdparty / bind9.git / commitdiff
