From 089c63b69cdf6803aa8901aae3f2fbae58969511 Mon Sep 17 00:00:00 2001
From: Automatic Updater
Only sign the DNSKEY RRset with key-signing keys, and omit
signatures from zone-signing keys. (This is similar to the
- dnskey-ksk-only yes; zone option in
+ dnssec-dnskey-kskonly yes; zone option in
named.)
address_match_element; ... };
allow-update-forwarding { address_match_element; ... };
update-check-ksk boolean;
- dnskey-ksk-only boolean;
+ dnssec-dnskey-kskonly boolean;
masterfile-format ( text | raw );
notify notifytype;
@@ -321,7 +321,7 @@ options
try-tcp-refresh boolean;
zero-no-soa-ttl boolean;
zero-no-soa-ttl-cache boolean;
- secure-to-insecure boolean;
+ dnssec-secure-to-insecure boolean;
deny-answer-addresses {
address_match_list
} [ except-from { namelist } ];
@@ -443,7 +443,7 @@ view
allow-update { address_match_element; ... };
allow-update-forwarding { address_match_element; ... };
update-check-ksk boolean;
- dnskey-ksk-only boolean;
+ dnssec-dnskey-kskonly boolean;
masterfile-format ( text | raw );
notify notifytype;
@@ -488,7 +488,7 @@ view
key-directory quoted_string;
zero-no-soa-ttl boolean;
zero-no-soa-ttl-cache boolean;
- secure-to-insecure boolean;
+ dnssec-secure-to-insecure boolean;
allow-v6-synthesis { address_match_element; ... }; // obsolete
fetch-glue boolean; // obsolete
@@ -522,7 +522,7 @@ zone
ixfr-from-differences boolean;
journal quoted_string;
zero-no-soa-ttl boolean;
- secure-to-insecure boolean;
+ dnssec-secure-to-insecure boolean;
allow-query { address_match_element; ... };
allow-query-on { address_match_element; ... };
@@ -538,7 +538,7 @@ zone
[...]
};
update-check-ksk boolean;
- dnskey-ksk-only boolean;
+ dnssec-dnskey-kskonly boolean;
masterfile-format ( text | raw );
notify notifytype;
diff --git a/doc/arm/Bv9ARM.ch06.html b/doc/arm/Bv9ARM.ch06.html
index 514144597a..496380ff7e 100644
--- a/doc/arm/Bv9ARM.ch06.html
+++ b/doc/arm/Bv9ARM.ch06.html
@@ -14,7 +14,7 @@
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
+
@@ -92,14 +92,14 @@
Statement Grammar
address_match_list }; ]
[ allow-update-forwarding { address_match_list }; ]
[ update-check-ksk yes_or_no; ]
- [ dnskey-ksk-only yes_or_no; ]
- [ secure-to-insecure yes_or_no ;]
+ [ dnssec-dnskey-kskonly yes_or_no; ]
+ [ dnssec-secure-to-insecure yes_or_no ;]
[ try-tcp-refresh yes_or_no; ]
[ allow-v6-synthesis { address_match_list }; ]
[ blackhole { address_match_list }; ]
@@ -3448,7 +3448,7 @@ options {
for that algorithm.
When this option and update-check-ksk @@ -3472,7 +3472,7 @@ options { For BIND 8 compatibility, the default is yes.
Allow a zone to transition from secure to insecure by
deleting all DNSKEY records. The default is
@@ -5918,8 +5918,8 @@ zone
The zone's name may optionally be followed by a class. If
a class is not specified, class
@@ -6353,10 +6353,10 @@ zone
See the description of
- dnskey-ksk-only in the section called “Boolean Options”.
+ dnssec-dnskey-kskonly in the section called “Boolean Options”.
@@ -6619,10 +6619,10 @@ zone
See the description of
- secure-to-insecure in the section called “Boolean Options”.
+ dnssec-secure-to-insecure in the section called “Boolean Options”.
A domain name identifies a node. Each node has a set of
resource information, which may be empty. The set of resource
@@ -7677,7 +7677,7 @@ zone
RRs are represented in binary form in the packets of the DNS
protocol, and are usually represented in highly encoded form
@@ -7880,7 +7880,7 @@ zone
As described above, domain servers store information as a
series of resource records, each of which contains a particular
@@ -8197,7 +8197,7 @@ zone
The Master File Format was initially defined in RFC 1035 and
has subsequently been extended. While the Master File Format
@@ -8212,7 +8212,7 @@ zone
When used in the label (or name) field, the asperand or
at-sign (@) symbol represents the current origin.
@@ -8223,7 +8223,7 @@ zone
Syntax: $ORIGIN
Syntax: $INCLUDE
Syntax: $TTL
Syntax: $GENERATE
Socket I/O statistics counters are defined per socket
types, which are
@@ -9980,7 +9980,7 @@ HOST-127.EXAMPLE. MX 0 .
Most statistics counters that were available
in BIND 8 are also supported in
diff --git a/doc/arm/Bv9ARM.ch07.html b/doc/arm/Bv9ARM.ch07.html
index 8597599d69..b37723064a 100644
--- a/doc/arm/Bv9ARM.ch07.html
+++ b/doc/arm/Bv9ARM.ch07.html
@@ -14,7 +14,7 @@
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
+
Table of Contents
On UNIX servers, it is possible to run BIND
@@ -148,7 +148,7 @@ zone "example.com" {
In order for a chroot environment
to
@@ -176,7 +176,7 @@ zone "example.com" {
Prior to running the named daemon,
use
diff --git a/doc/arm/Bv9ARM.ch08.html b/doc/arm/Bv9ARM.ch08.html
index f6d6148b87..3051cdb95c 100644
--- a/doc/arm/Bv9ARM.ch08.html
+++ b/doc/arm/Bv9ARM.ch08.html
@@ -14,7 +14,7 @@
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
+
Table of Contents
The best solution to solving installation and
configuration issues is to take preventative measures by setting
@@ -68,7 +68,7 @@
Zone serial numbers are just numbers — they aren't
date related. A lot of people set them to a number that
diff --git a/doc/arm/Bv9ARM.ch09.html b/doc/arm/Bv9ARM.ch09.html
index c9ab3a3870..e4798232e9 100644
--- a/doc/arm/Bv9ARM.ch09.html
+++ b/doc/arm/Bv9ARM.ch09.html
@@ -14,7 +14,7 @@
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
+
[RFC974] Mail Routing and the Domain System. January 1986. [RFC974] Mail Routing and the Domain System. January 1986. [RFC1995] Incremental Zone Transfer in DNS. August 1996. [RFC1995] Incremental Zone Transfer in DNS. August 1996. [RFC1996] A Mechanism for Prompt Notification of Zone Changes. August 1996. [RFC1996] A Mechanism for Prompt Notification of Zone Changes. August 1996. [RFC2136] Dynamic Updates in the Domain Name System. April 1997. [RFC2136] Dynamic Updates in the Domain Name System. April 1997. [RFC2671] Extension Mechanisms for DNS (EDNS0). August 1997. [RFC2671] Extension Mechanisms for DNS (EDNS0). August 1997. [RFC2672] Non-Terminal DNS Name Redirection. August 1999. [RFC2672] Non-Terminal DNS Name Redirection. August 1999. [RFC2845] Secret Key Transaction Authentication for DNS (TSIG). May 2000. [RFC2845] Secret Key Transaction Authentication for DNS (TSIG). May 2000. [RFC2930] Secret Key Establishment for DNS (TKEY RR). September 2000. [RFC2930] Secret Key Establishment for DNS (TKEY RR). September 2000. [RFC2931] DNS Request and Transaction Signatures (SIG(0)s). September 2000. [RFC2931] DNS Request and Transaction Signatures (SIG(0)s). September 2000. [RFC3007] Secure Domain Name System (DNS) Dynamic Update. November 2000. [RFC3007] Secure Domain Name System (DNS) Dynamic Update. November 2000. [RFC3645] Generic Security Service Algorithm for Secret
+ [RFC3645] Generic Security Service Algorithm for Secret
Key Transaction Authentication for DNS
(GSS-TSIG). October 2003. [RFC3225] Indicating Resolver Support of DNSSEC. December 2001. [RFC3225] Indicating Resolver Support of DNSSEC. December 2001. [RFC3833] Threat Analysis of the Domain Name System (DNS). August 2004. [RFC3833] Threat Analysis of the Domain Name System (DNS). August 2004. [RFC4033] DNS Security Introduction and Requirements. March 2005. [RFC4033] DNS Security Introduction and Requirements. March 2005. [RFC4034] Resource Records for the DNS Security Extensions. March 2005. [RFC4034] Resource Records for the DNS Security Extensions. March 2005. [RFC4035] Protocol Modifications for the DNS
+ [RFC4035] Protocol Modifications for the DNS
Security Extensions. March 2005. [RFC1535] A Security Problem and Proposed Correction With Widely
+ [RFC1535] A Security Problem and Proposed Correction With Widely
Deployed DNS Software.. October 1993. [RFC1536] Common DNS Implementation
+ [RFC1536] Common DNS Implementation
Errors and Suggested Fixes. October 1993. [RFC4074] Common Misbehaviour Against DNS
+ [RFC4074] Common Misbehaviour Against DNS
Queries for IPv6 Addresses. May 2005. [RFC1706] DNS NSAP Resource Records. October 1994. [RFC1706] DNS NSAP Resource Records. October 1994. [RFC2168] Resolution of Uniform Resource Identifiers using
+ [RFC2168] Resolution of Uniform Resource Identifiers using
the Domain Name System. June 1997. [RFC1876] A Means for Expressing Location Information in the
+ [RFC1876] A Means for Expressing Location Information in the
Domain
Name System. January 1996. [RFC2052] A DNS RR for Specifying the
+ [RFC2052] A DNS RR for Specifying the
Location of
Services.. October 1996. [RFC2163] Using the Internet DNS to
+ [RFC2163] Using the Internet DNS to
Distribute MIXER
Conformant Global Address Mapping. January 1998. [RFC2230] Key Exchange Delegation Record for the DNS. October 1997. [RFC2230] Key Exchange Delegation Record for the DNS. October 1997. [RFC2536] DSA KEYs and SIGs in the Domain Name System (DNS). March 1999. [RFC2536] DSA KEYs and SIGs in the Domain Name System (DNS). March 1999. [RFC2537] RSA/MD5 KEYs and SIGs in the Domain Name System (DNS). March 1999. [RFC2537] RSA/MD5 KEYs and SIGs in the Domain Name System (DNS). March 1999. [RFC2538] Storing Certificates in the Domain Name System (DNS). March 1999. [RFC2538] Storing Certificates in the Domain Name System (DNS). March 1999. [RFC2539] Storage of Diffie-Hellman Keys in the Domain Name System (DNS). March 1999. [RFC2539] Storage of Diffie-Hellman Keys in the Domain Name System (DNS). March 1999. [RFC2540] Detached Domain Name System (DNS) Information. March 1999. [RFC2540] Detached Domain Name System (DNS) Information. March 1999. [RFC2782] A DNS RR for specifying the location of services (DNS SRV). February 2000. [RFC2782] A DNS RR for specifying the location of services (DNS SRV). February 2000. [RFC2915] The Naming Authority Pointer (NAPTR) DNS Resource Record. September 2000. [RFC2915] The Naming Authority Pointer (NAPTR) DNS Resource Record. September 2000. [RFC3110] RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS). May 2001. [RFC3110] RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS). May 2001. [RFC3123] A DNS RR Type for Lists of Address Prefixes (APL RR). June 2001. [RFC3123] A DNS RR Type for Lists of Address Prefixes (APL RR). June 2001. [RFC1101] DNS Encoding of Network Names
+ [RFC1101] DNS Encoding of Network Names
and Other Types. April 1989. [RFC1123] Requirements for Internet Hosts - Application and
+ [RFC1123] Requirements for Internet Hosts - Application and
Support. October 1989. [RFC1591] Domain Name System Structure and Delegation. March 1994. [RFC1591] Domain Name System Structure and Delegation. March 1994. [RFC2317] Classless IN-ADDR.ARPA Delegation. March 1998. [RFC2317] Classless IN-ADDR.ARPA Delegation. March 1998. [RFC1033] Domain administrators operations guide.. November 1987. [RFC1033] Domain administrators operations guide.. November 1987. [RFC1912] Common DNS Operational and
+ [RFC1912] Common DNS Operational and
Configuration Errors. February 1996. [RFC2825] A Tangled Web: Issues of I18N, Domain Names,
+ [RFC2825] A Tangled Web: Issues of I18N, Domain Names,
and the Other Internet protocols. May 2000. [RFC3490] Internationalizing Domain Names in Applications (IDNA). March 2003. [RFC3490] Internationalizing Domain Names in Applications (IDNA). March 2003. [RFC1464] Using the Domain Name System To Store Arbitrary String
+ [RFC1464] Using the Domain Name System To Store Arbitrary String
Attributes. May 1993. [RFC1713] Tools for DNS Debugging. November 1994. [RFC1713] Tools for DNS Debugging. November 1994. [RFC2240] A Legal Basis for Domain Name Allocation. November 1997. [RFC2240] A Legal Basis for Domain Name Allocation. November 1997. [RFC2345] Domain Names and Company Name Retrieval. May 1998. [RFC2345] Domain Names and Company Name Retrieval. May 1998. [RFC2352] A Convention For Using Legal Names as Domain Names. May 1998. [RFC2352] A Convention For Using Legal Names as Domain Names. May 1998. [RFC3071] Reflections on the DNS, RFC 1591, and Categories of Domains. February 2001. [RFC3071] Reflections on the DNS, RFC 1591, and Categories of Domains. February 2001. [RFC3258] Distributing Authoritative Name Servers via
+ [RFC3258] Distributing Authoritative Name Servers via
Shared Unicast Addresses. April 2002. [RFC3901] DNS IPv6 Transport Operational Guidelines. September 2004. [RFC3901] DNS IPv6 Transport Operational Guidelines. September 2004. [RFC1712] DNS Encoding of Geographical
+ [RFC1712] DNS Encoding of Geographical
Location. November 1994. [RFC2065] Domain Name System Security Extensions. January 1997. [RFC2065] Domain Name System Security Extensions. January 1997. [RFC2137] Secure Domain Name System Dynamic Update. April 1997. [RFC2137] Secure Domain Name System Dynamic Update. April 1997. [RFC2535] Domain Name System Security Extensions. March 1999. [RFC2535] Domain Name System Security Extensions. March 1999. [RFC3008] Domain Name System Security (DNSSEC)
+ [RFC3008] Domain Name System Security (DNSSEC)
Signing Authority. November 2000. [RFC3090] DNS Security Extension Clarification on Zone Status. March 2001. [RFC3090] DNS Security Extension Clarification on Zone Status. March 2001. [RFC3445] Limiting the Scope of the KEY Resource Record (RR). December 2002. [RFC3445] Limiting the Scope of the KEY Resource Record (RR). December 2002. [RFC3655] Redefinition of DNS Authenticated Data (AD) bit. November 2003. [RFC3655] Redefinition of DNS Authenticated Data (AD) bit. November 2003. [RFC3658] Delegation Signer (DS) Resource Record (RR). December 2003. [RFC3658] Delegation Signer (DS) Resource Record (RR). December 2003. [RFC3755] Legacy Resolver Compatibility for Delegation Signer (DS). May 2004. [RFC3755] Legacy Resolver Compatibility for Delegation Signer (DS). May 2004. [RFC3757] Domain Name System KEY (DNSKEY) Resource Record
+ [RFC3757] Domain Name System KEY (DNSKEY) Resource Record
(RR) Secure Entry Point (SEP) Flag. April 2004. [RFC3845] DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format. August 2004. [RFC3845] DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format. August 2004. DNS and BIND. Copyright © 1998 Sebastopol, CA: O'Reilly and Associates. DNS and BIND. Copyright © 1998 Sebastopol, CA: O'Reilly and Associates. ddns-confgen
generates a key for use by nsupdate
and named. It simplifies configuration
@@ -75,7 +75,7 @@
When dnssec-keyfromlabel completes
successfully,
@@ -260,7 +260,7 @@
dnssec-keygen(8),
dnssec-signzone(8),
BIND 9 Administrator Reference Manual,
@@ -268,7 +268,7 @@
Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
If the argument begins with a '+' or '-', it is interpreted as
@@ -303,7 +303,7 @@
To generate a 768-bit DSA key for the domain
dnssec-signzone(8),
BIND 9 Administrator Reference Manual,
RFC 2539,
@@ -379,7 +379,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
@@ -151,7 +151,7 @@
dnssec-settime can also be used to print the
timing metadata associated with a key.
@@ -177,7 +177,7 @@
dnssec-keygen(8),
dnssec-signzone(8),
BIND 9 Administrator Reference Manual,
@@ -185,7 +185,7 @@
dnssec-signzone
signs a zone. It generates
NSEC and RRSIG records and produces a signed version of the
@@ -61,7 +61,7 @@
@@ -346,7 +346,7 @@
Only sign the DNSKEY RRset with key-signing keys, and omit
signatures from zone-signing keys. (This is similar to the
- dnskey-ksk-only yes; zone option in
+ dnssec-dnskey-kskonly yes; zone option in
named.)
The following command signs the host
is a simple utility for performing DNS lookups.
It is normally used to convert names to IP addresses and vice versa.
@@ -202,7 +202,7 @@
If host has been built with IDN (internationalized
domain name) support, it can accept and display non-ASCII domain names.
@@ -216,12 +216,12 @@
dig(1),
named(8).
named-checkconf
checks the syntax, but not the semantics, of a named
configuration file.
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
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
@@ -267,7 +267,7 @@
The named configuration file is too complex
to describe in detail here. A complete description is provided
@@ -284,7 +284,7 @@
nsupdate
is used to submit Dynamic DNS Update requests as defined in RFC 2136
to a name server.
@@ -210,7 +210,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 64dac5db2b..2db761df7b 100644
--- a/doc/arm/man.rndc-confgen.html
+++ b/doc/arm/man.rndc-confgen.html
@@ -14,7 +14,7 @@
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
+
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
@@ -79,7 +79,7 @@
@@ -151,7 +151,7 @@
rndc
does not yet support all the commands of
the BIND 8 ndc utility.
@@ -165,7 +165,7 @@
zone_name [ allow-transfer { address_match_list }; ]
[ allow-update-forwarding { address_match_list }; ]
[ update-check-ksk yes_or_no; ]
- [ dnskey-ksk-only yes_or_no; ]
- [ secure-to-insecure yes_or_no ; ]
+ [ dnssec-dnskey-kskonly yes_or_no; ]
+ [ dnssec-secure-to-insecure yes_or_no ; ]
[ try-tcp-refresh yes_or_no; ]
[ also-notify { ip_addr [port ip_port] ;
[ ip_addr [port ip_port] ; ... ] }; ]
@@ -6234,7 +6234,7 @@ zone zone_name [
IN (for Internet),
@@ -6256,7 +6256,7 @@ zone zone_name [
zone_name [update-check-ksk in the section called “Boolean Options”.
zone_name [masterfile-format
in the section called “Tuning”.
zone_name [
zone_name [
zone_name [
zone_name [
zone_name [
zone_name [
zone_name [
domain-name
@@ -8252,7 +8252,7 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
filename
@@ -8288,7 +8288,7 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
default-ttl
@@ -8307,7 +8307,7 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
range
@@ -8731,7 +8731,7 @@ HOST-127.EXAMPLE. MX 0 .
Standards
Proposed Standards
DNS Security Proposed Standards
Other Important RFCs About DNS
Implementation
Resource Record Types
DNS and the Internet
DNS Operations
Internationalized Domain Names
Obsolete and Unimplemented Experimental RFC
ddns-confgen [-a ] [algorithm-h] [-k ] [keyname-r ] [ -s randomfilename | -z zone ] [-q] [name]DESCRIPTION
+DESCRIPTION
GENERATED KEY FILES
+GENERATED KEY FILES
SEE ALSO
+SEE ALSO
TIMING OPTIONS
+TIMING OPTIONS
EXAMPLE
+EXAMPLE
example.com, the following command would be
@@ -370,7 +370,7 @@
SEE ALSO
+SEE ALSO
dnssec-revoke [-hr] [-v ] [level-K ] [directory-E ] [engine-f] {keyfile}DESCRIPTION
+DESCRIPTION
dnssec-settime [-f] [-K ] [directory-P ] [date/offset-A ] [date/offset-R ] [date/offset-I ] [date/offset-D ] [date/offset-h] [-v ] [level-E ] {keyfile}engineDESCRIPTION
+DESCRIPTION
-P, -A,
@@ -75,7 +75,7 @@
TIMING OPTIONS
+TIMING OPTIONS
PRINTING OPTIONS
+PRINTING OPTIONS
SEE ALSO
+SEE ALSO
dnssec-signzone [-a] [-c ] [class-d ] [directory-E ] [engine-e ] [end-time-f ] [output-file-g] [-h] [-K ] [directory-k ] [key-l ] [domain-i ] [interval-I ] [input-format-j ] [jitter-N ] [soa-serial-format-o ] [origin-O ] [output-format-p] [-P] [-r ] [randomdev-S] [-s ] [start-time-T ] [ttl-t] [-u] [-v ] [level-x] [-z] [-3 ] [salt-H ] [iterations-A] {zonefile} [key...]DESCRIPTION
+DESCRIPTION
OPTIONS
+OPTIONS
EXAMPLE
+EXAMPLE
example.com
zone with the DSA key generated by dnssec-keygen
@@ -427,14 +427,14 @@ db.example.com.signed
%
host [-aCdlnrsTwv] [-c ] [class-N ] [ndots-R ] [number-t ] [type-W ] [wait-m ] [flag-4] [-6] {name} [server]DESCRIPTION
+DESCRIPTION
IDN SUPPORT
+IDN SUPPORT
SEE ALSO
+SEE ALSO
named-checkconf [-h] [-v] [-j] [-t ] {filename} [directory-p] [-z]DESCRIPTION
+DESCRIPTION
RETURN VALUES
+RETURN VALUES
named-compilezone [-d] [-j] [-q] [-v] [-c ] [class-C ] [mode-f ] [format-F ] [format-i ] [mode-k ] [mode-m ] [mode-n ] [mode-o ] [filename-s ] [style-t ] [directory-w ] [directory-D] [-W ] {mode-o } {zonename} {filename}filenameDESCRIPTION
+DESCRIPTION
RETURN VALUES
+RETURN VALUES
named [-4] [-6] [-c ] [config-file-d ] [debug-level-E ] [engine-name-f] [-g] [-m ] [flag-n ] [#cpus-p ] [port-s] [-S ] [#max-socks-t ] [directory-u ] [user-v] [-V] [-x ]cache-fileDESCRIPTION
+DESCRIPTION
SIGNALS
+SIGNALS
CONFIGURATION
+CONFIGURATION
nsupdate [-d] [-D] [[-g] | [-o] | [-l] | [-y ] | [[hmac:]keyname:secret-k ]] [keyfile-t ] [timeout-u ] [udptimeout-r ] [udpretries-R ] [randomdev-v] [filename]DESCRIPTION
+DESCRIPTION
BUGS
+BUGS
rndc-confgen [-a] [-b ] [keysize-c ] [keyfile-h] [-k ] [keyname-p ] [port-r ] [randomfile-s ] [address-t ] [chrootdir-u ]userDESCRIPTION
+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
@@ -135,7 +135,7 @@
NAME SERVER CONFIGURATION
+NAME SERVER CONFIGURATION
rndc.conf
@@ -219,7 +219,7 @@
rndc [-b ] [source-address-c ] [config-file-k ] [key-file-s ] [server-p ] [port-V] [-y ] {command}key_idDESCRIPTION
+DESCRIPTION
OPTIONS
+OPTIONS
source-addressLIMITATIONS
+LIMITATIONS