From b96d0b74187757909006c14942550e922e87f9f9 Mon Sep 17 00:00:00 2001
From: "Internet Software Consortium, Inc" <@isc.org>
Date: Sat, 20 Aug 2011 17:00:04 -0600
Subject: 9.8.1b2
---
doc/arm/Bv9ARM-book.xml | 73 +-
doc/arm/Bv9ARM.ch03.html | 24 +-
doc/arm/Bv9ARM.ch04.html | 162 +-
doc/arm/Bv9ARM.ch05.html | 6 +-
doc/arm/Bv9ARM.ch06.html | 207 +-
doc/arm/Bv9ARM.ch07.html | 14 +-
doc/arm/Bv9ARM.ch08.html | 18 +-
doc/arm/Bv9ARM.ch09.html | 220 +-
doc/arm/Bv9ARM.html | 162 +-
doc/arm/Bv9ARM.pdf | 11830 ++++++++++++++++-----------------
doc/arm/man.arpaname.html | 8 +-
doc/arm/man.ddns-confgen.html | 10 +-
doc/arm/man.dig.html | 20 +-
doc/arm/man.dnssec-dsfromkey.html | 16 +-
doc/arm/man.dnssec-keyfromlabel.html | 14 +-
doc/arm/man.dnssec-keygen.html | 16 +-
doc/arm/man.dnssec-revoke.html | 10 +-
doc/arm/man.dnssec-settime.html | 14 +-
doc/arm/man.dnssec-signzone.html | 12 +-
doc/arm/man.genrandom.html | 10 +-
doc/arm/man.host.html | 10 +-
doc/arm/man.isc-hmac-fixup.html | 10 +-
doc/arm/man.named-checkconf.html | 12 +-
doc/arm/man.named-checkzone.html | 12 +-
doc/arm/man.named-journalprint.html | 8 +-
doc/arm/man.named.html | 16 +-
doc/arm/man.nsec3hash.html | 10 +-
doc/arm/man.nsupdate.html | 14 +-
doc/arm/man.rndc-confgen.html | 12 +-
doc/arm/man.rndc.conf.html | 12 +-
doc/arm/man.rndc.html | 12 +-
doc/misc/options | 4 +-
32 files changed, 6501 insertions(+), 6477 deletions(-)
(limited to 'doc')
diff --git a/doc/arm/Bv9ARM-book.xml b/doc/arm/Bv9ARM-book.xml
index d11a1ac0..f6ea92ea 100644
--- a/doc/arm/Bv9ARM-book.xml
+++ b/doc/arm/Bv9ARM-book.xml
@@ -18,7 +18,7 @@
- PERFORMANCE OF THIS SOFTWARE.
-->
-
+
This command requires that the
- auto-dnssec zone option to be set
- to allow
,
- maintain
, or
- create
, and also requires
- the zone to be configured to allow dynamic DNS.
+ auto-dnssec zone option be set
+ to allow
or
+ maintain
,
+ and also requires the zone to be configured to
+ allow dynamic DNS.
See the section called “Dynamic Update Policies” for
more details.
This command requires that the
- auto-dnssec zone option to
- be set to maintain
or
- create
, and also requires
- the zone to be configured to allow dynamic DNS.
+ auto-dnssec zone option
+ be set to maintain
,
+ and also requires the zone to be configured to
+ allow dynamic DNS.
See the section called “Dynamic Update Policies” for
more details.
Certain UNIX signals cause the name server to take specific actions, as described in the following table. These signals can diff --git a/doc/arm/Bv9ARM.ch04.html b/doc/arm/Bv9ARM.ch04.html index 67d98d44..b1165d04 100644 --- a/doc/arm/Bv9ARM.ch04.html +++ b/doc/arm/Bv9ARM.ch04.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - +
@@ -49,59 +49,59 @@Setting up different views, or visibility, of the DNS space to internal and external resolvers is usually referred to as a @@ -286,7 +286,7 @@
Let's say a company named Example, Inc.
(example.com
)
@@ -543,7 +543,7 @@ nameserver 172.16.72.4
A shared secret is generated to be shared between host1 and host2. An arbitrary key name is chosen: "host1-host2.". The key name must @@ -551,7 +551,7 @@ nameserver 172.16.72.4
The following command will generate a 128-bit (16 byte) HMAC-SHA256 key as described above. Longer keys are better, but shorter keys @@ -575,7 +575,7 @@ nameserver 172.16.72.4
The shared secret is simply a random sequence of bits, encoded in base-64. Most ASCII strings are valid base-64 strings (assuming @@ -590,7 +590,7 @@ nameserver 172.16.72.4
This is beyond the scope of DNS. A secure transport mechanism should be used. This could be secure FTP, ssh, telephone, etc. @@ -598,7 +598,7 @@ nameserver 172.16.72.4
Imagine host1 and host 2 are @@ -625,7 +625,7 @@ key host1-host2. {
Since keys are shared between two hosts only, the server must
be told when keys are to be used. The following is added to the named.conf
file
@@ -657,7 +657,7 @@ server 10.1.2.3 {
BIND allows IP addresses and ranges to be specified in ACL @@ -684,7 +684,7 @@ allow-update { key host1-host2. ;};
The processing of TSIG signed messages can result in several errors. If a signed message is sent to a non-TSIG aware @@ -710,7 +710,7 @@ allow-update { key host1-host2. ;};
TKEY is a mechanism for automatically generating a shared secret between two hosts. There are several "modes" of @@ -746,7 +746,7 @@ allow-update { key host1-host2. ;};
BIND 9 partially supports DNSSEC SIG(0) transaction signatures as specified in RFC 2535 and RFC 2931. @@ -807,7 +807,7 @@ allow-update { key host1-host2. ;};
The dnssec-keygen program is used to generate keys. @@ -863,7 +863,7 @@ allow-update { key host1-host2. ;};
The dnssec-signzone program is used to sign a zone. @@ -905,7 +905,7 @@ allow-update { key host1-host2. ;};
To enable named to respond appropriately to DNS requests from DNSSEC aware clients, @@ -1065,7 +1065,7 @@ options { from insecure to signed and back again. A secure zone can use either NSEC or NSEC3 chains.
+Converting from insecure to secureChanging a zone from insecure to secure can be done in two ways: using a dynamic DNS update, or the auto-dnssec zone option.
@@ -1091,7 +1091,7 @@ options { well. An NSEC chain will be generated as part of the initial signing process. +Dynamic DNS update methodTo insert the keys via dynamic update:
% nsupdate @@ -1127,7 +1127,7 @@ options {While the initial signing and NSEC/NSEC3 chain generation is happening, other updates are possible as well.
+Fully automatic zone signingTo enable automatic signing, add the auto-dnssec option to the zone statement in
+Private-type recordsnamed.conf
. @@ -1162,7 +1162,7 @@ options { configuration. If this has not been done, the configuration will fail.The 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 @@ -1203,12 +1203,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 methodTo perform key rollovers via dynamic update, you need to add the
+Automatic key rolloversK*
files for the new keys so that named can find them. You can then add the new @@ -1230,7 +1230,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 @@ -1245,27 +1245,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, @@ -1280,14 +1280,14 @@ options { allow instead (or it will re-sign).
+Periodic re-signingIn any secure zone which supports dynamic updates, named will periodically re-sign RRsets which have not been re-signed as a result of some update action. The signature lifetimes will be adjusted so as to spread the re-sign load over time rather than all at once.
+NSEC3 and OPTOUTnamed only supports creating new NSEC3 chains where all the NSEC3 records in the zone have the same OPTOUT @@ -1309,7 +1309,7 @@ options { configuration files.
To configure a validating resolver to use RFC 5011 to maintain a trust anchor, configure the trust anchor using a managed-keys statement. Information about @@ -1320,7 +1320,7 @@ options {
To set up an authoritative zone for RFC 5011 trust anchor maintenance, generate two (or more) key signing keys (KSKs) for the zone. Sign the zone with one of them; this is the "active" @@ -1394,7 +1394,7 @@ $
dnssec-signzone -S -K keys example.net
< Debian Linux, Solaris x86 and Windows Server 2003.See the HSM vendor documentation for information about installing, initializing, testing and troubleshooting the HSM.
@@ -1468,7 +1468,7 @@ $patch -p1 -d openssl-0.9.8l \ when we configure BIND 9.
The AEP Keyper is a highly secure key storage device, but does not provide hardware cryptographic acceleration. It can carry out cryptographic operations, but it is probably @@ -1500,7 +1500,7 @@ $
./Configure linux-generic32 -m32 -pthread \
The SCA-6000 PKCS #11 provider is installed as a system library, libpkcs11. It is a true crypto accelerator, up to 4 times faster than any CPU, so the flavor shall be @@ -1544,12 +1544,12 @@ $
./Configure solaris64-x86_64-cc \
When building BIND 9, the location of the custom-built OpenSSL library must be specified via configure.
To link with the PKCS #11 provider, threads must be enabled in the BIND 9 build.
The PKCS #11 library for the AEP Keyper is currently @@ -1565,7 +1565,7 @@ $
./configure CC="gcc -m32" --enable-threads \
To link with the PKCS #11 provider, threads must be enabled in the BIND 9 build.
@@ -1588,7 +1588,7 @@ $./configure CC="cc -xarch=amd64" --enable-thre
BIND 9 includes a minimal set of tools to operate the HSM, including pkcs11-keygen to generate a new key pair @@ -1606,7 +1606,7 @@ $
./configure CC="cc -xarch=amd64" --enable-thre
First, we must set up the runtime environment so the OpenSSL and PKCS #11 libraries can be loaded:
@@ -1694,7 +1694,7 @@ example.net.signedThe OpenSSL engine can be specified in named and all of the BIND dnssec-* tools by using the "-E @@ -1715,7 +1715,7 @@ $
dnssec-signzone -E '' -S example.net
If you want named to dynamically re-sign zones using HSM keys, and/or to to sign new records inserted via nsupdate, then @@ -1751,7 +1751,7 @@ $
dnssec-signzone -E '' -S example.net
BIND 9 fully supports all currently defined forms of IPv6 name to address and address to name @@ -1789,7 +1789,7 @@ $
+dnssec-signzone -E '' -S example.net
The IPv6 AAAA record is a parallel to the IPv4 A record, and, unlike the deprecated A6 record, specifies the entire @@ -1808,7 +1808,7 @@ host 3600 IN AAAA 2001:db8::1
When looking up an address in nibble format, the address components are simply reversed, just as in IPv4, and diff --git a/doc/arm/Bv9ARM.ch05.html b/doc/arm/Bv9ARM.ch05.html index 3b60755f..99e2a9db 100644 --- a/doc/arm/Bv9ARM.ch05.html +++ b/doc/arm/Bv9ARM.ch05.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - +
@@ -45,13 +45,13 @@Table of Contents
Traditionally applications have been linked with a stub resolver library that sends recursive DNS queries to a local caching name diff --git a/doc/arm/Bv9ARM.ch06.html b/doc/arm/Bv9ARM.ch06.html index 1b1a3dd5..69637538 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. --> - +
@@ -48,58 +48,58 @@Configuration File Elements Configuration File Grammar - -
- acl Statement Grammar
+- acl Statement Grammar
- acl Statement Definition and Usage
-- controls Statement Grammar
+- controls Statement Grammar
- controls Statement Definition and Usage
-- include Statement Grammar
-- include Statement Definition and +
- include Statement Grammar
+- include Statement Definition and Usage
-- key Statement Grammar
-- key Statement Definition and Usage
-- logging Statement Grammar
-- logging Statement Definition and +
- key Statement Grammar
+- key Statement Definition and Usage
+- logging Statement Grammar
+- logging Statement Definition and Usage
-- lwres Statement Grammar
-- lwres Statement Definition and Usage
-- masters Statement Grammar
-- masters Statement Definition and +
- lwres Statement Grammar
+- lwres Statement Definition and Usage
+- masters Statement Grammar
+- masters Statement Definition and Usage
-- options Statement Grammar
+- options Statement Grammar
- options Statement Definition and Usage
- server Statement Grammar
- server Statement Definition and Usage
- statistics-channels Statement Grammar
-- statistics-channels Statement Definition and +
- statistics-channels Statement Definition and Usage
- trusted-keys Statement Grammar
-- trusted-keys Statement Definition +
- trusted-keys Statement Definition and Usage
-- managed-keys Statement Grammar
+- managed-keys Statement Grammar
- managed-keys Statement Definition and Usage
- view Statement Grammar
-- view Statement Definition and Usage
+- view Statement Definition and Usage
- zone Statement Grammar
-- zone Statement Definition and Usage
+- zone Statement Definition and Usage
Zone File +Zone File
- Types of Resource Records and When to Use Them
-- Discussion of MX Records
+- Discussion of MX Records
- Setting TTLs
-- Inverse Mapping in IPv4
-- Other Zone File Directives
-- BIND Master File Extension: the $GENERATE Directive
+- Inverse Mapping in IPv4
+- Other Zone File Directives
+- BIND Master File Extension: the $GENERATE Directive
- Additional File Formats
BIND9 Statistics @@ -477,7 +477,7 @@ Address Match Listsaddress_match_list
= address_match_list_element ; [ address_match_list_element; ... ]address_match_list_element
= [ ! ] (ip_address [/length] | @@ -486,7 +486,7 @@Address match lists are primarily used to determine access control for various server operations. They are also used in @@ -570,7 +570,7 @@
The BIND 9 comment syntax allows for comments to appear @@ -580,7 +580,7 @@
/* This is a BIND comment as in C */@@ -596,7 +596,7 @@Comments may appear anywhere that whitespace may appear in a BIND configuration file. @@ -848,7 +848,7 @@
acl acl-name { address_match_list }; @@ -930,7 +930,7 @@controls { [ inet ( ip_addr | * ) [ port ip_port ] allow {address_match_list
} @@ -1054,12 +1054,12 @@includefilename
;The include statement inserts the @@ -1074,7 +1074,7 @@
keykey_id
{ algorithmstring
; secretstring
; @@ -1083,7 +1083,7 @@The key statement defines a shared secret key for use with TSIG (see the section called “TSIG”) @@ -1130,7 +1130,7 @@
logging { [ channelchannel_name
{ ( filepath_name
@@ -1154,7 +1154,7 @@The logging statement configures a @@ -1188,7 +1188,7 @@
All log output goes to one or more channels; you can make as many of them as you want. @@ -1753,7 +1753,7 @@ category notify { null; };
The query-errors category is specifically intended for debugging purposes: To identify @@ -1981,7 +1981,7 @@ badresp:1,adberr:0,findfail:0,valfail:0]
This is the grammar of the lwres statement in the
named.conf
file: @@ -1997,7 +1997,7 @@ badresp:1,adberr:0,findfail:0,valfail:0]The lwres statement configures the name @@ -2048,7 +2048,7 @@ badresp:1,adberr:0,findfail:0,valfail:0]
mastersname
[portip_port
] { (masters_list
|ip_addr
[portip_port
] [keykey
] ) ; [...] }; @@ -2056,7 +2056,7 @@ badresp:1,adberr:0,findfail:0,valfail:0]masters lists allow for a common set of masters to be easily used by @@ -2065,7 +2065,7 @@ badresp:1,adberr:0,findfail:0,valfail:0]
This is the grammar of the options statement in the
named.conf
file: @@ -3649,7 +3649,7 @@ options {The forwarding facility can be used to create a large site-wide cache on a few servers, reducing traffic over links to external @@ -3693,7 +3693,7 @@ options {
Dual-stack servers are used as servers of last resort to work around @@ -3904,7 +3904,7 @@ options {
The interfaces and ports that the server will answer queries from may be specified using the listen-on option. listen-on takes @@ -4178,19 +4178,26 @@ avoid-v6-udp-ports {}; hour). The maximum value is 28 days (40320 minutes).
serial-query-rate -+ - Slave servers will periodically query master servers - to find out if zone serial numbers have changed. Each such - query uses - a minute amount of the slave server's network bandwidth. To - limit the - amount of bandwidth used, BIND 9 limits the rate at which - queries are - sent. The value of the serial-query-rate option, - an integer, is the maximum number of queries sent per - second. - The default is 20. -
+ + Slave servers will periodically query master + servers to find out if zone serial numbers have + changed. Each such query uses a minute amount of + the slave server's network bandwidth. To limit + the amount of bandwidth used, BIND 9 limits the + rate at which queries are sent. The value of the + serial-query-rate option, an + integer, is the maximum number of queries sent + per second. The default is 20. +
++ In addition to controlling the rate SOA refresh + queries are issued at + serial-query-rate also controls + the rate at which NOTIFY messages are sent from + both master and slave zones. +
+serial-queries In BIND 8, the serial-queries @@ -4356,7 +4363,7 @@ avoid-v6-udp-ports {};
use-v4-udp-ports, avoid-v4-udp-ports, @@ -4398,7 +4405,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
The server's usage of many system resources can be limited. Scaled values are allowed when specifying resource limits. For @@ -5120,10 +5127,16 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
notify-delay -+
+ +The delay, in seconds, between sending sets of notify messages for a zone. The default is five (5) seconds. -
+ The overall rate that NOTIFY messages are sent for all + zones is controlled by serial-query-rate. +
+@@ -5375,7 +5388,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };BIND 9 provides the ability to filter out DNS responses from external DNS servers containing @@ -5498,7 +5511,7 @@ deny-answer-aliases { "example.net"; };
BIND 9 includes an intentionally limited mechanism to modify DNS responses for recursive requests @@ -5510,8 +5523,8 @@ deny-answer-aliases { "example.net"; };
The rules encoded in a response policy zone (RPZ) are applied only to responses to queries that ask for recursion (RD=1). - RPZs are normal DNS zones containing largely valid RRsets - that can be queried normal if allowed. + RPZs are normal DNS zones containing RRsets + that can be queried normally if allowed. It is usually best to restrict those queries with something like allow-query {none; }; or allow-query { 127.0.0.1; };. @@ -5522,6 +5535,8 @@ deny-answer-aliases { "example.net"; }; records resolved in the process of generating the response. The owner name of a QNAME rule is the query name relativized to the RPZ. + The records in a rewrite rule are usually A, AAAA, or special + CNAMEs, but can be any type except DNAME.
IP rules are triggered by addresses in A and AAAA records. @@ -5614,6 +5629,7 @@ nodata.domain.com CNAME *. bad.domain.com A 10.0.0.1 AAAA 2001:2::1 ok.domain.com CNAME ok.domain.com. +*.badzone.domain.com CNAME garden.example.com. ; IP rules rewriting all answers for 127/8 except 127.0.0.1 8.0.0.0.127.ip CNAME . @@ -5833,7 +5849,7 @@ ns.domain.com.rpz-nsdname CNAME .
The statistics-channels statement @@ -5893,7 +5909,7 @@ ns.domain.com.rpz-nsdname CNAME .
The trusted-keys statement defines @@ -5933,7 +5949,7 @@ ns.domain.com.rpz-nsdname CNAME .
managed-keys {string
initial-keynumber
number
number
string
; [string
initial-keynumber
number
number
string
; [...]] @@ -6068,7 +6084,7 @@ ns.domain.com.rpz-nsdname CNAME .The view statement is a powerful feature @@ -6234,7 +6250,7 @@ view "external" { [ min-retry-time
number
; ] [ max-retry-timenumber
; ] [ key-directorypath_name
; ] - [ auto-dnssecallow
|maintain
|create
|off
; ] + [ auto-dnssecallow
|maintain
|off
; ] [ zero-no-soa-ttlyes_or_no
; ] }; @@ -6246,6 +6262,7 @@ zonezone_name
[ allow-transfer {address_match_list
}; ] [ allow-update-forwarding {address_match_list
}; ] [ update-check-kskyes_or_no
; ] + [ dnssec-update-mode (maintain
|no-resign
); ] [ dnssec-dnskey-kskonlyyes_or_no
; ] [ dnssec-secure-to-insecureyes_or_no
; ] [ try-tcp-refreshyes_or_no
; ] @@ -6356,10 +6373,10 @@ zonezone_name
[
@@ -6619,7 +6636,7 @@ zone zone_name
[The zone's name may optionally be followed by a class. If a class is not specified, class
IN
(forInternet
), @@ -6641,7 +6658,7 @@ zonezone_name
[
- allow-notify
@@ -7040,7 +7057,7 @@ example.com. NS ns2.example.net.
Zones configured for dynamic DNS may also use this option to allow varying levels of automatic DNSSEC key - management. There are four possible settings: + management. There are three possible settings:
auto-dnssec allow; permits @@ -7518,7 +7535,7 @@ example.com. NS ns2.example.net.
@@ -7531,7 +7548,7 @@ example.com. NS ns2.example.net.A domain name identifies a node. Each node has a set of resource information, which may be empty. The set of resource @@ -8268,7 +8285,7 @@ example.com. NS ns2.example.net.
RRs are represented in binary form in the packets of the DNS protocol, and are usually represented in highly encoded form @@ -8471,7 +8488,7 @@ example.com. NS ns2.example.net.
As described above, domain servers store information as a series of resource records, each of which contains a particular @@ -8727,7 +8744,7 @@ example.com. NS ns2.example.net.
Reverse name resolution (that is, translation from IP address to name) is achieved by means of the in-addr.arpa domain @@ -8788,7 +8805,7 @@ example.com. NS ns2.example.net.
The Master File Format was initially defined in RFC 1035 and has subsequently been extended. While the Master File Format @@ -8803,7 +8820,7 @@ example.com. NS ns2.example.net.
When used in the label (or name) field, the asperand or at-sign (@) symbol represents the current origin. @@ -8814,7 +8831,7 @@ example.com. NS ns2.example.net.
Syntax: $ORIGIN
domain-name
@@ -8843,7 +8860,7 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.Syntax: $INCLUDE
filename
@@ -8879,7 +8896,7 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.Syntax: $TTL
default-ttl
@@ -8898,7 +8915,7 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.Syntax: $GENERATE
range
@@ -9322,7 +9339,7 @@ HOST-127.EXAMPLE. MX 0 .
@@ -9879,7 +9896,7 @@ HOST-127.EXAMPLE. MX 0 .
@@ -10033,7 +10050,7 @@ HOST-127.EXAMPLE. MX 0 .
@@ -10416,7 +10433,7 @@ HOST-127.EXAMPLE. MX 0 . Socket I/O statistics counters are defined per socket types, which are @@ -10571,7 +10588,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 6c7dda43..d230af89 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. --> - +
@@ -46,10 +46,10 @@Table of Contents
@@ -122,7 +122,7 @@ zone "example.com" {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 af43671b..8353ca5a 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. --> - +
@@ -45,18 +45,18 @@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 @@ -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 217c485a..679ed4fb 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. --> - +
@@ -45,31 +45,31 @@Table of Contents
@@ -278,42 +278,42 @@Standards
-[RFC974] Mail Routing and the Domain System. January 1986.
+[RFC974] Mail Routing and the Domain System. January 1986.
Proposed Standards
-[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.
-@@ -322,19 +322,19 @@[RFC3645] Generic Security Service Algorithm for Secret +
[RFC3645] Generic Security Service Algorithm for Secret Key Transaction Authentication for DNS (GSS-TSIG). October 2003.
DNS Security Proposed Standards
-[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.
-@@ -342,146 +342,146 @@[RFC4035] Protocol Modifications for the DNS +
[RFC4035] Protocol Modifications for the DNS Security Extensions. March 2005.
Other Important RFCs About DNS Implementation
-[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.
Resource Record Types
-[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.
DNS and the Internet
-[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.
DNS Operations
-[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.
Internationalized Domain Names
-[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.
-@@ -497,47 +497,47 @@[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.
@@ -551,39 +551,39 @@Obsolete and Unimplemented Experimental RFC
-[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.
-@@ -604,14 +604,14 @@[RFC3845] DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format. August 2004.
+[RFC3845] DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format. August 2004.
-@@ -648,7 +648,7 @@DNS and BIND. Copyright © 1998 Sebastopol, CA: O'Reilly and Associates.
+DNS and BIND. Copyright © 1998 Sebastopol, CA: O'Reilly and Associates.
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 @@ -657,7 +657,7 @@
$./configure --enable-exportlib
$[other flags]
make
@@ -672,7 +672,7 @@ $make
$cd lib/export
$make install
@@ -694,7 +694,7 @@ $make install
Currently, win32 is not supported for the export library. (Normal BIND 9 application can be built as @@ -734,7 +734,7 @@ $
make
The IRS library supports an "advanced" configuration file related to the DNS library for configuration parameters that would be beyond the capability of the @@ -752,14 +752,14 @@ $
make
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 @@ -823,7 +823,7 @@ $
make
Similar to "sample", but accepts a list of (query) domain names as a separate file and resolves the names @@ -864,7 +864,7 @@ $
make
It sends a query to a specified server, and prints the response with minimal processing. It doesn't act as a @@ -905,7 +905,7 @@ $
make
This is a test program to check getaddrinfo() and getnameinfo() behavior. It takes a @@ -922,7 +922,7 @@ $
make
It accepts a single update command as a command-line argument, sends an update request message to the @@ -1017,7 +1017,7 @@ $
sample-update -a sample-update -k Kxxx.+nnn+mm
It checks a set of domains to see the name servers of the domains behave @@ -1074,7 +1074,7 @@ $
sample-update -a sample-update -k Kxxx.+nnn+mm
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 cccfabc0..d88bc93d 100644 --- a/doc/arm/Bv9ARM.html +++ b/doc/arm/Bv9ARM.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - +
@@ -83,7 +83,7 @@Name Server Operations 4. Advanced DNS Features @@ -92,64 +92,64 @@Dynamic Update Incremental Zone Transfers (IXFR) -Split DNS -+ Split DNS +TSIG - -
- Generate Shared Keys for Each Pair of Hosts
-- Copying the Shared Secret to Both Machines
-- Informing the Servers of the Key's Existence
-- Instructing the Server to Use the Key
-- TSIG Key Based Access Control
-- Errors
+- Generate Shared Keys for Each Pair of Hosts
+- Copying the Shared Secret to Both Machines
+- Informing the Servers of the Key's Existence
+- Instructing the Server to Use the Key
+- TSIG Key Based Access Control
+- Errors
TKEY -SIG(0) +TKEY +SIG(0) DNSSEC DNSSEC, Dynamic Zones, and Automatic Signing -
- Converting from insecure to secure
-- Dynamic DNS update method
-- Fully automatic zone signing
-- Private-type records
-- DNSKEY rollovers
-- Dynamic DNS update method
-- Automatic key rollovers
-- NSEC3PARAM rollovers via UPDATE
-- Converting from NSEC to NSEC3
-- Converting from NSEC3 to NSEC
-- Converting from secure to insecure
-- Periodic re-signing
-- NSEC3 and OPTOUT
+- Converting from insecure to secure
+- Dynamic DNS update method
+- Fully automatic zone signing
+- Private-type records
+- DNSKEY rollovers
+- Dynamic DNS update method
+- Automatic key rollovers
+- NSEC3PARAM rollovers via UPDATE
+- Converting from NSEC to NSEC3
+- Converting from NSEC3 to NSEC
+- Converting from secure to insecure
+- Periodic re-signing
+- NSEC3 and OPTOUT
Dynamic Trust Anchor Management PKCS #11 (Cryptoki) support - -
- Prerequisites
-- Building BIND 9 with PKCS#11
-- PKCS #11 Tools
-- Using the HSM
-- Specifying the engine on the command line
-- Running named with automatic zone re-signing
+- Prerequisites
+- Building BIND 9 with PKCS#11
+- PKCS #11 Tools
+- Using the HSM
+- Specifying the engine on the command line
+- Running named with automatic zone re-signing
IPv6 Support in BIND 9 +IPv6 Support in BIND 9 5. The BIND 9 Lightweight Resolver 6. BIND 9 Configuration Reference @@ -157,58 +157,58 @@Configuration File Elements Configuration File Grammar - -
- acl Statement Grammar
+- acl Statement Grammar
- acl Statement Definition and Usage
-- controls Statement Grammar
+- controls Statement Grammar
- controls Statement Definition and Usage
-- include Statement Grammar
-- include Statement Definition and +
- include Statement Grammar
+- include Statement Definition and Usage
-- key Statement Grammar
-- key Statement Definition and Usage
-- logging Statement Grammar
-- logging Statement Definition and +
- key Statement Grammar
+- key Statement Definition and Usage
+- logging Statement Grammar
+- logging Statement Definition and Usage
-- lwres Statement Grammar
-- lwres Statement Definition and Usage
-- masters Statement Grammar
-- masters Statement Definition and +
- lwres Statement Grammar
+- lwres Statement Definition and Usage
+- masters Statement Grammar
+- masters Statement Definition and Usage
-- options Statement Grammar
+- options Statement Grammar
- options Statement Definition and Usage
- server Statement Grammar
- server Statement Definition and Usage
- statistics-channels Statement Grammar
-- statistics-channels Statement Definition and +
- statistics-channels Statement Definition and Usage
- trusted-keys Statement Grammar
-- trusted-keys Statement Definition +
- trusted-keys Statement Definition and Usage
-- managed-keys Statement Grammar
+- managed-keys Statement Grammar
- managed-keys Statement Definition and Usage
- view Statement Grammar
-- view Statement Definition and Usage
+- view Statement Definition and Usage
- zone Statement Grammar
-- zone Statement Definition and Usage
+- zone Statement Definition and Usage
Zone File +Zone File
- Types of Resource Records and When to Use Them
-- Discussion of MX Records
+- Discussion of MX Records
- Setting TTLs
-- Inverse Mapping in IPv4
-- Other Zone File Directives
-- BIND Master File Extension: the $GENERATE Directive
+- Inverse Mapping in IPv4
+- Other Zone File Directives
+- BIND Master File Extension: the $GENERATE Directive
- Additional File Formats
BIND9 Statistics @@ -217,41 +217,41 @@7. BIND 9 Security Considerations 8. Troubleshooting A. Appendices I. Manual pages diff --git a/doc/arm/Bv9ARM.pdf b/doc/arm/Bv9ARM.pdf index 11555d35..cc588b4d 100755 --- a/doc/arm/Bv9ARM.pdf +++ b/doc/arm/Bv9ARM.pdf @@ -3307,7 +3307,7 @@ endobj /ProcSet [ /PDF /Text ] >> endobj 1078 0 obj << -/Length 3421 +/Length 3424 /Filter /FlateDecode >> stream @@ -3320,9 +3320,13 @@ E ‹ÓÉ´ýÍ«ß©¢Ço?ø?X¨V~^LšÊ´dòÞwëáë‹1qazm…9&.ê=\) (.™;bÛA\¦X@=zãÁ n¶yzÐËQÈt1GÀã*iû‹”¹80ŽPï‰#Ɖ4” ìq´ycµuÛPxŠ-æb¼@ÅlÉ2Æê=ñB)QT“ÛÌ‹a²\MÆËáø|4›UÓÜ®|«ˆTÖmh„$7[p²9f±˜`ˆ1U²ýÅÉ\#¨÷Ȉ°Þ@ÈT„âô{0²¹Qî"ÑÇBÌV)Ða¡£ÂB.„Ü{bÁh¢tƒò͇ÜW‹«åª:þY}í»ÛMƒ+·v@RZÌK²Ãp‚a´ÜƒsXÑ’(jUœß),›®ÄÃ|ÄÃ1: D¶u#Æê=¢¸ƒ§r¿Íqõ™—²í§ÒJˆ ‰–rûš‘ÌbT€!† C%† ê=¡Rß´¤X*†qy§¨ÜbvCͽo=BÒŠ‘ †P‰L¨÷„DFvDbó ôO“êsî†é¿Ÿ[ã†â,¤öÂÒ]0Ä`‚rÚþ¥Ó\L¨÷S½³ŸºTãúN`ÚÜ®h§·ç’¦˜Öbh€! ” ƒ& ê=AC%1\·Ã7mëÅõ<4Ô¸M`(kñòNLw1LÀƒ ÊiûÏåâÀ`B½G˜¸ãÄhª,öN`ÚÜŶ§ÛŠi-…"Ðtdsýk‚¹8hpïqM[JŒG‘|X,{@íëeµ>…$ëΰ^@B -‹† P"L ¨÷ˆŸåXpÞGÕÞ˜ñb:ZŸb} eÜ“ „!ŸÅ°$;Œ –ë_:Ì‘‚¹N (M¬R’"®·$ñ–ÁŸ(ZÈ\1Àƒ*ƒQ‘‰Ãõž¸Ò8$‡\´×iì.±§÷—§~˜öŸLêþF*µµ²‡ÄË1Ùaâ]ÿÔ&&;êÝù—Vˆœ8&B¹Í7ŒvZ‚—“i½ §Üƒï<îåàU]Ï¢·e¬µBÃc×?¿–™ÑþŽ¹@0ÈP÷iÊÃ)q’‡¢‹¨‡®ŒÓΈµ†mþ±ïxíq5ž7gb–×æ2ÿ>¯ÚéÍjf7a<|^À6FÜ£Šm$d¤Xp`ˆ 3Ž -ž uŸ:j‰3L'Á×’‹ÍÚZÁÕØ"èVÌ0Äx€‚