From c60ee6edf129596fa04db86c6865d75b5a412598 Mon Sep 17 00:00:00 2001
From: Tinderbox User
-
-
@@ -1080,7 +1080,7 @@ options {
from insecure to signed and back again. A secure zone can use
either NSEC or NSEC3 chains.
Changing a zone from insecure to secure can be done in two ways: using a dynamic DNS update, or the auto-dnssec zone option.
@@ -1198,7 +1198,7 @@ options { configuration. If this has not been done, the configuration will fail. +Private-type recordsThe state of the signing process is signaled by private-type records (with a default type value of 65534). When signing is complete, these records will have a nonzero value for @@ -1239,12 +1239,12 @@ options {
+DNSKEY rollovers
As with insecure-to-secure conversions, rolling DNSSEC keys can be done in two ways: using a dynamic DNS update, or the auto-dnssec zone option.
+Dynamic DNS update method To perform key rollovers via dynamic update, you need to add
the K*
files for the new keys so that
named can find them. You can then add the new
@@ -1266,7 +1266,7 @@ options {
named will clean out any signatures generated
by the old key after the update completes.
When a new key reaches its activation date (as set by dnssec-keygen or dnssec-settime), if the auto-dnssec zone option is set to @@ -1281,27 +1281,27 @@ options { completes in 30 days, after which it will be safe to remove the old key from the DNSKEY RRset.
+NSEC3PARAM rollovers via UPDATEAdd the new NSEC3PARAM record via dynamic update. When the new NSEC3 chain has been generated, the NSEC3PARAM flag field will be zero. At this point you can remove the old NSEC3PARAM record. The old chain will be removed after the update request completes.
+Converting from NSEC to NSEC3To do this, you just need to add an NSEC3PARAM record. When the conversion is complete, the NSEC chain will have been removed and the NSEC3PARAM record will have a zero flag field. The NSEC3 chain will be generated before the NSEC chain is destroyed.
+Converting from NSEC3 to NSECTo do this, use nsupdate to remove all NSEC3PARAM records with a zero flag field. The NSEC chain will be generated before the NSEC3 chain is removed.
+Converting from secure to insecureTo convert a signed zone to unsigned using dynamic DNS,
delete all the DNSKEY records from the zone apex using
nsupdate. All signatures, NSEC or NSEC3 chains,
@@ -1452,7 +1452,7 @@ $ dnssec-signzone -S -K keys example.net
<
See the documentation provided by your HSM vendor for
information about installing, initializing, testing and
@@ -1461,7 +1461,7 @@ $
Native PKCS#11 mode will only work with an HSM capable of carrying
out every cryptographic operation BIND 9 may
@@ -1495,7 +1495,7 @@ $
OpenSSL-based PKCS#11 mode uses a modified version of the
OpenSSL library; stock OpenSSL does not fully support PKCS#11.
@@ -1553,7 +1553,7 @@ $
The AEP Keyper is a highly secure key storage device,
but does not provide hardware cryptographic acceleration. It
@@ -1628,7 +1628,7 @@ $
The SCA-6000 PKCS#11 provider is installed as a system
library, libpkcs11. It is a true crypto accelerator, up to 4
@@ -1657,7 +1657,7 @@ $
SoftHSM is a software library provided by the OpenDNSSEC
project (http://www.opendnssec.org) which provides a PKCS#11
@@ -1730,7 +1730,7 @@ $
To link with the PKCS#11 provider, threads must be
enabled in the BIND 9 build.
@@ -1750,7 +1750,7 @@ $
To link with the PKCS#11 provider, threads must be
enabled in the BIND 9 build.
@@ -1772,7 +1772,7 @@ $
BIND 9 includes a minimal set of tools to operate the
HSM, including
@@ -1816,7 +1816,7 @@ $
For OpenSSL-based PKCS#11, we must first set up the runtime
environment so the OpenSSL and PKCS#11 libraries can be loaded:
@@ -1937,7 +1937,7 @@ example.net.signed
When using OpenSSL-based PKCS#11, the "engine" to be used by
OpenSSL can be specified in named and all of
@@ -1969,7 +1969,7 @@ $
If you want named to dynamically re-sign zones
using HSM keys, and/or to to sign new records inserted via nsupdate,
@@ -2056,7 +2056,7 @@ $
A DLZ database is configured with a dlz
statement in
For guidance in implementation of DLZ modules, the directory
BIND 9 includes a limited
mechanism to modify DNS responses for requests
@@ -6696,7 +6698,7 @@ example.com CNAME rpz-tcp-only.
Excessive almost identical UDP responses
can be controlled by configuring a
@@ -7210,7 +7212,7 @@ example.com CNAME rpz-tcp-only.
The statistics-channels statement
@@ -7326,7 +7328,7 @@ example.com CNAME rpz-tcp-only.
The trusted-keys statement defines
@@ -7370,7 +7372,7 @@ example.com CNAME rpz-tcp-only.
The view statement is a powerful
feature
@@ -7830,10 +7832,10 @@ zone
RRs are represented in binary form in the packets of the DNS
protocol, and are usually represented in highly encoded form
@@ -10108,7 +10110,7 @@ view external {
As described above, domain servers store information as a
series of resource records, each of which contains a particular
@@ -10439,7 +10441,7 @@ view external {
When used in the label (or name) field, the asperand or
at-sign (@) symbol represents the current origin.
@@ -10450,7 +10452,7 @@ view external {
Syntax: $ORIGIN
Syntax: $INCLUDE
Syntax: $TTL
Syntax: $GENERATE
Table of Contents
On UNIX servers, it is possible to run BIND
diff --git a/doc/arm/Bv9ARM.ch08.html b/doc/arm/Bv9ARM.ch08.html
index 89c9e615d3..9b56b846a2 100644
--- a/doc/arm/Bv9ARM.ch08.html
+++ b/doc/arm/Bv9ARM.ch08.html
@@ -47,8 +47,8 @@
Zone serial numbers are just numbers — they aren't
date related. A lot of people set them to a number that
@@ -95,7 +95,7 @@
The Internet Systems Consortium
(ISC) offers a wide range
diff --git a/doc/arm/Bv9ARM.ch09.html b/doc/arm/Bv9ARM.ch09.html
index 4d42ea0595..b5d91ce2a9 100644
--- a/doc/arm/Bv9ARM.ch09.html
+++ b/doc/arm/Bv9ARM.ch09.html
@@ -58,7 +58,7 @@
+ Adjusted max-recursion-queries to accommodate the smaller
+ initial packet sizes used in BIND 9.10 and higher when
+ contacting authoritative servers for the first time.
+ GNU make is required to build the export libraries (other
part of BIND 9 can still be built with other types of make). In
the reminder of this document, "make" means GNU make. Note that
@@ -1024,7 +1029,7 @@
Currently, win32 is not supported for the export
library. (Normal BIND 9 application can be built as
@@ -1101,7 +1106,7 @@ $ The IRS library supports an "advanced" configuration file
related to the DNS library for configuration parameters that
would be beyond the capability of the
@@ -1119,14 +1124,14 @@ $ Some sample application programs using this API are
provided for reference. The following is a brief description of
these applications.
It sends a query of a given name (of a given optional RR type) to a
specified recursive server, and prints the result as a list of
@@ -1190,7 +1195,7 @@ $
Similar to "sample", but accepts a list
of (query) domain names as a separate file and resolves the names
@@ -1231,7 +1236,7 @@ $
It sends a query to a specified server, and
prints the response with minimal processing. It doesn't act as a
@@ -1272,7 +1277,7 @@ $
This is a test program
to check getaddrinfo() and getnameinfo() behavior. It takes a
@@ -1289,7 +1294,7 @@ $
It accepts a single update command as a
command-line argument, sends an update request message to the
@@ -1384,7 +1389,7 @@ $
It checks a set
of domains to see the name servers of the domains behave
@@ -1441,7 +1446,7 @@ $ As of this writing, there is no formal "manual" of the
libraries, except this document, header files (some of them
provide pretty detailed explanations), and sample application
diff --git a/doc/arm/Bv9ARM.html b/doc/arm/Bv9ARM.html
index 65a0506020..a08bbd6957 100644
--- a/doc/arm/Bv9ARM.html
+++ b/doc/arm/Bv9ARM.html
@@ -114,17 +114,17 @@
arpaname translates IP addresses (IPv4 and
IPv6) to the corresponding IN-ADDR.ARPA or IP6.ARPA names.
tsig-keygen and ddns-confgen
are invocation methods for a utility that generates keys for use
@@ -87,7 +87,7 @@
delv
(Domain Entity Lookup & Validation) is a tool for sending
DNS queries and validating the results, using the the same internal
@@ -96,7 +96,7 @@
delv
provides a number of query options which affect the way results are
displayed, and in some cases the way lookups are performed.
@@ -471,12 +471,12 @@
dig(1),
named(8),
RFC4034,
diff --git a/doc/arm/man.dig.html b/doc/arm/man.dig.html
index 359530f95f..f78d39346b 100644
--- a/doc/arm/man.dig.html
+++ b/doc/arm/man.dig.html
@@ -52,7 +52,7 @@
dig
(domain information groper) is a flexible tool
for interrogating DNS name servers. It performs DNS lookups and
@@ -99,7 +99,7 @@
The dig
provides a number of query options which affect
the way in which lookups are made and the results displayed. Some of
@@ -688,7 +688,7 @@
The BIND 9 implementation of dig
supports
@@ -734,7 +734,7 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
If dig has been built with IDN (internationalized
domain name) support, it can accept and display non-ASCII domain names.
@@ -748,14 +748,14 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
host(1),
named(8),
dnssec-keygen(8),
@@ -763,7 +763,7 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
There are probably too many query options.
dnssec-checkds
verifies the correctness of Delegation Signer (DS) or DNSSEC
Lookaside Validation (DLV) resource records for keys in a specified
@@ -59,7 +59,7 @@
dnssec-coverage
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
@@ -78,7 +78,7 @@
dnssec-dsfromkey
outputs the Delegation Signer (DS) resource record (RR), as defined in
RFC 3658 and RFC 4509, for the given key(s).
The keyfile can be designed by the key identification
dnssec-keygen(8),
dnssec-signzone(8),
BIND 9 Administrator Reference Manual,
@@ -189,7 +189,7 @@
dnssec-importkey
reads a public DNSKEY record and generates a pair of
.key/.private files. The DNSKEY record may be read from an
@@ -71,7 +71,7 @@
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
If the argument begins with a '+' or '-', it is interpreted as
@@ -142,7 +142,7 @@
A keyfile can be designed by the key identification
dnssec-keygen(8),
dnssec-signzone(8),
BIND 9 Administrator Reference Manual,
@@ -159,7 +159,7 @@
dnssec-keyfromlabel
generates a key pair of files that referencing a key object stored
in a cryptographic hardware service module (HSM). The private key
@@ -66,7 +66,7 @@
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
If the argument begins with a '+' or '-', it is interpreted as
@@ -315,7 +315,7 @@
When dnssec-keyfromlabel completes
successfully,
@@ -354,7 +354,7 @@
dnssec-keygen(8),
dnssec-signzone(8),
BIND 9 Administrator Reference Manual,
@@ -363,7 +363,7 @@
dnssec-keygen
generates keys for DNSSEC (Secure DNS), as defined in RFC 2535
and RFC 4034. It can also generate keys for use with
@@ -64,7 +64,7 @@
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
If the argument begins with a '+' or '-', it is interpreted as
@@ -359,7 +359,7 @@
To generate a 768-bit DSA key for the domain
dnssec-signzone(8),
BIND 9 Administrator Reference Manual,
RFC 2539,
@@ -435,7 +435,7 @@
dnssec-revoke
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
@@ -58,7 +58,7 @@
dnssec-settime
reads a DNSSEC private key file and sets the key timing metadata
as specified by the
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
If the argument begins with a '+' or '-', it is interpreted as
@@ -210,7 +210,7 @@
dnssec-settime can also be used to print the
timing metadata associated with a key.
@@ -236,7 +236,7 @@
dnssec-keygen(8),
dnssec-signzone(8),
BIND 9 Administrator Reference Manual,
@@ -244,7 +244,7 @@
dnssec-signzone
signs a zone. It generates
NSEC and RRSIG records and produces a signed version of the
@@ -61,7 +61,7 @@
The following command signs the dnssec-verify
verifies that a zone is fully signed for each algorithm found
in the DNSKEY RRset for the zone, and that the NSEC / NSEC3
@@ -58,7 +58,7 @@
genrandom
generates a file or a set of files containing a specified quantity
@@ -59,7 +59,7 @@
host
is a simple utility for performing DNS lookups.
It is normally used to convert names to IP addresses and vice versa.
@@ -214,7 +214,7 @@
If host has been built with IDN (internationalized
domain name) support, it can accept and display non-ASCII domain names.
@@ -228,12 +228,12 @@
dig(1),
named(8).
Versions of BIND 9 up to and including BIND 9.6 had a bug causing
HMAC-SHA* TSIG keys which were longer than the digest length of the
@@ -76,7 +76,7 @@
Secrets that have been converted by isc-hmac-fixup
are shortened, but as this is how the HMAC protocol works in
@@ -87,14 +87,14 @@
named-checkconf
checks the syntax, but not the semantics, of a
named configuration file. The file is parsed
@@ -70,7 +70,7 @@
named-checkconf
returns an exit status of 1 if
errors were detected and 0 otherwise.
named-checkzone
checks the syntax and integrity of a zone file. It performs the
same checks as named does when loading a
@@ -71,7 +71,7 @@
named-checkzone
returns an exit status of 1 if
errors were detected and 0 otherwise.
named-journalprint
prints the contents of a zone journal file in a human-readable
@@ -76,7 +76,7 @@
named-rrchecker
read a individual DNS resource record from standard input and checks if it
is syntactically correct.
@@ -78,7 +78,7 @@
RFC 1034,
RFC 1035,
diff --git a/doc/arm/man.named.html b/doc/arm/man.named.html
index f3e9e77968..51c0d8be37 100644
--- a/doc/arm/man.named.html
+++ b/doc/arm/man.named.html
@@ -50,7 +50,7 @@
named
is a Domain Name System (DNS) server,
part of the BIND 9 distribution from ISC. For more
@@ -65,7 +65,7 @@
In routine operation, signals should not be used to control
the nameserver; rndc should be used
@@ -302,7 +302,7 @@
The named configuration file is too complex
to describe in detail here. A complete description is provided
@@ -319,7 +319,7 @@
nsec3hash generates an NSEC3 hash based on
a set of NSEC3 parameters. This can be used to check the validity
@@ -56,7 +56,7 @@
nsupdate
is used to submit Dynamic DNS Update requests as defined in RFC 2136
to a name server.
@@ -236,7 +236,7 @@
The TSIG key is redundantly stored in two separate files.
This is a consequence of nsupdate using the DST library
diff --git a/doc/arm/man.rndc-confgen.html b/doc/arm/man.rndc-confgen.html
index 1656b68bee..700d2b79da 100644
--- a/doc/arm/man.rndc-confgen.html
+++ b/doc/arm/man.rndc-confgen.html
@@ -50,7 +50,7 @@
rndc-confgen
generates configuration files
for rndc. It can be used as a
@@ -66,7 +66,7 @@
The name server must be configured to accept rndc connections and
to recognize the key specified in the rndc
controls the operation of a name
server. It supersedes the ndc utility
@@ -81,7 +81,7 @@
A list of commands supported by rndc can
be seen by running rndc without arguments.
@@ -609,7 +609,7 @@
+ Adjusted max-recursion-queries to accommodate the smaller
+ initial packet sizes used in BIND 9.10 and higher when
+ contacting authoritative servers for the first time.
+ dnssec-signzone -S -K keys example.net
<
./configure --enable-native-pkcs11 \
./configure --enable-native-pkcs11 \
$
@@ -1586,7 +1586,7 @@ $ wget http://www.openssl.org/source/openssl-0.9.8y.tar.gz
patch -p1 -d openssl-0.9.8y \
./Configure linux-generic32 -m32 -pthread \
./Configure solaris64-x86_64-cc \
./Configure linux-x86_64 -pthread \
./configure CC="gcc -m32" --enable-threads \
./configure CC="cc -xarch=amd64" --enable-thre
$
cd ../bind9
$ ./configure --enable-threads \
@@ -1793,7 +1793,7 @@ $
./configure --enable-threads \
./configure --enable-threads \
dnssec-signzone -E '' -S example.net
dnssec-signzone -E '' -S example.net
named.conf
:
@@ -2105,7 +2105,7 @@ $ dnssec-signzone -E '' -S example.net
contrib/dlz/example
contains a basic
diff --git a/doc/arm/Bv9ARM.ch06.html b/doc/arm/Bv9ARM.ch06.html
index d8b32aa2c3..34d3662a1b 100644
--- a/doc/arm/Bv9ARM.ch06.html
+++ b/doc/arm/Bv9ARM.ch06.html
@@ -78,28 +78,28 @@
managed-keys {
name
initial-key flags
protocol
algorithm
key-data
;
[ name
initial-key flags
protocol
algorithm
key-data
; [...]]
@@ -7508,7 +7510,7 @@ example.com CNAME rpz-tcp-only.
zone_name
[
domain-name
@@ -10479,7 +10481,7 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
filename
@@ -10515,7 +10517,7 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
default-ttl
@@ -10534,7 +10536,7 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
range
@@ -10977,7 +10979,7 @@ HOST-127.EXAMPLE. MX 0 .
@@ -412,6 +412,11 @@
A regression caused nsupdate to use the default recursive servers
rather than the SOA MNAME server when sending the UPDATE.
+
@@ -68,13 +68,13 @@
$
./configure --enable-exportlib
$ [other flags]
make
@@ -1039,7 +1044,7 @@ $ make
$
cd lib/export
$ make install
@@ -1061,7 +1066,7 @@ $ make install
make
make
make
make
make
make
sample-update -a sample-update -k Kxxx.+nnn+mm
sample-update -a sample-update -k Kxxx.+nnn+mm
-
-
@@ -194,28 +194,28 @@
@@ -253,7 +253,7 @@
@@ -263,13 +263,13 @@
arpaname
{ipaddress
...}DESCRIPTION
+DESCRIPTION
ddns-confgen
[-a
] [algorithm
-h
] [-k
] [keyname
-q
] [-r
] [ -s randomfile
name
| -z zone
]DESCRIPTION
+DESCRIPTION
delv
[queryopt...] [query...]DESCRIPTION
+DESCRIPTION
QUERY OPTIONS
+QUERY OPTIONS
SEE ALSO
+SEE ALSO
dig
[global-queryopt...] [query...]DESCRIPTION
+DESCRIPTION
OPTIONS
+OPTIONS
-b
option sets the source IP address of the query
to address
. This must be a valid
@@ -260,7 +260,7 @@
QUERY OPTIONS
+QUERY OPTIONS
MULTIPLE QUERIES
+MULTIPLE QUERIES
IDN SUPPORT
+IDN SUPPORT
SEE ALSO
+SEE ALSO
BUGS
+BUGS
dnssec-dsfromkey
[-l
] [domain
-f
] [file
-d
] [dig path
-D
] {zone}dsfromkey path
DESCRIPTION
+DESCRIPTION
dnssec-coverage
[-K
] [directory
-l
] [length
-f
] [file
-d
] [DNSKEY TTL
-m
] [max TTL
-r
] [interval
-c
] [compilezone path
-k
] [-z
] [zone]DESCRIPTION
+DESCRIPTION
dnssec-dsfromkey
[-h
] [-V
]DESCRIPTION
+DESCRIPTION
FILES
+FILES
Knnnn.+aaa+iiiii
or the full file name
@@ -173,13 +173,13 @@
SEE ALSO
+SEE ALSO
dnssec-importkey
{-f
} [filename
-K
] [directory
-L
] [ttl
-P
] [date/offset
-D
] [date/offset
-h
] [-v
] [level
-V
] [dnsname
]DESCRIPTION
+DESCRIPTION
TIMING OPTIONS
+TIMING OPTIONS
FILES
+FILES
Knnnn.+aaa+iiiii
or the full file name
@@ -151,7 +151,7 @@
SEE ALSO
+SEE ALSO
dnssec-keyfromlabel
{-l label
} [-3
] [-a
] [algorithm
-A
] [date/offset
-c
] [class
-D
] [date/offset
-E
] [engine
-f
] [flag
-G
] [-I
] [date/offset
-i
] [interval
-k
] [-K
] [directory
-L
] [ttl
-n
] [nametype
-P
] [date/offset
-p
] [protocol
-R
] [date/offset
-S
] [key
-t
] [type
-v
] [level
-V
] [-y
] {name}DESCRIPTION
+DESCRIPTION
TIMING OPTIONS
+TIMING OPTIONS
GENERATED KEY FILES
+GENERATED KEY FILES
SEE ALSO
+SEE ALSO
dnssec-keygen
[-a
] [algorithm
-b
] [keysize
-n
] [nametype
-3
] [-A
] [date/offset
-C
] [-c
] [class
-D
] [date/offset
-E
] [engine
-f
] [flag
-G
] [-g
] [generator
-h
] [-I
] [date/offset
-i
] [interval
-K
] [directory
-L
] [ttl
-k
] [-P
] [date/offset
-p
] [protocol
-q
] [-R
] [date/offset
-r
] [randomdev
-S
] [key
-s
] [strength
-t
] [type
-v
] [level
-V
] [-z
] {name}DESCRIPTION
+DESCRIPTION
TIMING OPTIONS
+TIMING OPTIONS
EXAMPLE
+EXAMPLE
example.com
, the following command would be
@@ -426,7 +426,7 @@
SEE ALSO
+SEE ALSO
dnssec-revoke
[-hr
] [-v
] [level
-V
] [-K
] [directory
-E
] [engine
-f
] [-R
] {keyfile}DESCRIPTION
+DESCRIPTION
dnssec-settime
[-f
] [-K
] [directory
-L
] [ttl
-P
] [date/offset
-A
] [date/offset
-R
] [date/offset
-I
] [date/offset
-D
] [date/offset
-h
] [-V
] [-v
] [level
-E
] {keyfile}engine
DESCRIPTION
+DESCRIPTION
-P
, -A
,
@@ -76,7 +76,7 @@
TIMING OPTIONS
+TIMING OPTIONS
PRINTING OPTIONS
+PRINTING OPTIONS
SEE ALSO
+SEE ALSO
dnssec-signzone
[-a
] [-c
] [class
-d
] [directory
-D
] [-E
] [engine
-e
] [end-time
-f
] [output-file
-g
] [-h
] [-K
] [directory
-k
] [key
-L
] [serial
-l
] [domain
-M
] [domain
-i
] [interval
-I
] [input-format
-j
] [jitter
-N
] [soa-serial-format
-o
] [origin
-O
] [output-format
-P
] [-p
] [-Q
] [-R
] [-r
] [randomdev
-S
] [-s
] [start-time
-T
] [ttl
-t
] [-u
] [-v
] [level
-V
] [-X
] [extended end-time
-x
] [-z
] [-3
] [salt
-H
] [iterations
-A
] {zonefile} [key...]DESCRIPTION
+DESCRIPTION
EXAMPLE
+EXAMPLE
example.com
zone with the DSA key generated by dnssec-keygen
@@ -542,14 +542,14 @@ db.example.com.signed
%
dnssec-verify
[-c
] [class
-E
] [engine
-I
] [input-format
-o
] [origin
-v
] [level
-V
] [-x
] [-z
] {zonefile}DESCRIPTION
+DESCRIPTION
genrandom
[-n
] {number
size
} {filename
}DESCRIPTION
+DESCRIPTION
host
[-aCdlnrsTwv
] [-c
] [class
-N
] [ndots
-R
] [number
-t
] [type
-W
] [wait
-m
] [flag
-4
] [-6
] [-v
] [-V
] {name} [server]DESCRIPTION
+DESCRIPTION
IDN SUPPORT
+IDN SUPPORT
SEE ALSO
+SEE ALSO
isc-hmac-fixup
{algorithm
} {secret
}DESCRIPTION
+DESCRIPTION
SECURITY CONSIDERATIONS
+SECURITY CONSIDERATIONS
named-checkconf
[-h
] [-v
] [-j
] [-t
] {filename} [directory
-p
] [-x
] [-z
]DESCRIPTION
+DESCRIPTION
RETURN VALUES
+RETURN VALUES
named-compilezone
[-d
] [-j
] [-q
] [-v
] [-c
] [class
-C
] [mode
-f
] [format
-F
] [format
-J
] [filename
-i
] [mode
-k
] [mode
-m
] [mode
-n
] [mode
-l
] [ttl
-L
] [serial
-r
] [mode
-s
] [style
-t
] [directory
-T
] [mode
-w
] [directory
-D
] [-W
] {mode
-o
} {zonename} {filename}filename
DESCRIPTION
+DESCRIPTION
RETURN VALUES
+RETURN VALUES
named-journalprint
{journal
}DESCRIPTION
+DESCRIPTION
named-rrchecker
[-h
] [-o
] [origin
-p
] [-u
] [-C
] [-T
] [-P
]DESCRIPTION
+DESCRIPTION
SEE ALSO
+SEE ALSO
named
[-4
] [-6
] [-c
] [config-file
-d
] [debug-level
-D
] [string
-E
] [engine-name
-f
] [-g
] [-L
] [logfile
-m
] [flag
-n
] [#cpus
-p
] [port
-s
] [-S
] [#max-socks
-t
] [directory
-U
] [#listeners
-u
] [user
-v
] [-V
] [-x
]cache-file
DESCRIPTION
+DESCRIPTION
SIGNALS
+SIGNALS
CONFIGURATION
+CONFIGURATION
nsec3hash
{salt
} {algorithm
} {iterations
} {domain
}DESCRIPTION
+DESCRIPTION
nsupdate
[-d
] [-D
] [[-g
] | [-o
] | [-l
] | [-y
] | [[hmac:]keyname:secret
-k
]] [keyfile
-t
] [timeout
-u
] [udptimeout
-r
] [udpretries
-R
] [randomdev
-v
] [-T
] [-P
] [-V
] [filename]DESCRIPTION
+DESCRIPTION
BUGS
+BUGS
rndc-confgen
[-a
] [-A
] [algorithm
-b
] [keysize
-c
] [keyfile
-h
] [-k
] [keyname
-p
] [port
-r
] [randomfile
-s
] [address
-t
] [chrootdir
-u
]user
DESCRIPTION
+DESCRIPTION
rndc.conf
DESCRIPTION
+DESCRIPTION
rndc.conf
is the configuration file
for rndc, the BIND 9 name server control
utility. This file has a similar structure and syntax to
@@ -136,7 +136,7 @@
NAME SERVER CONFIGURATION
+NAME SERVER CONFIGURATION
rndc.conf
@@ -220,7 +220,7 @@
rndc
[-b
] [source-address
-c
] [config-file
-k
] [key-file
-s
] [server
-p
] [port
-q
] [-V
] [-y
] {command}key_id
DESCRIPTION
+DESCRIPTION
COMMANDS
+COMMANDS