named-checkconf — named configuration file syntax checking tool
@@ -32,14 +32,14 @@named-checkconf [-v] [-j] [-t ] {filename} [directory-z]
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, named-compilezone — zone file validity checking or converting tool
@@ -33,7 +33,7 @@named-compilezone [-d] [-j] [-q] [-v] [-c ] [class-f ] [format-F ] [format-i ] [mode-k ] [mode-m ] [mode-n ] [mode-o ] [filename-s ] [style-t ] [directory-w ] [directory-D] [-W ] {zonename} {filename}mode
named-checkzone checks the syntax and integrity of a zone file. It performs the same checks as named does when loading a @@ -53,7 +53,7 @@
named-checkzone returns an exit status of 1 if errors were detected and 0 otherwise.
dig — DNS lookup utility
@@ -34,7 +34,7 @@dig [global-queryopt...] [query...]
dig (domain information groper) is a flexible tool for interrogating DNS name servers. It performs DNS lookups and @@ -73,7 +73,7 @@
The -b option sets the source IP address of the query
to address. This must be a valid
@@ -213,7 +213,7 @@
dig provides a number of query options which affect the way in which lookups are made and the results displayed. Some of @@ -517,7 +517,7 @@
The BIND 9 implementation of dig supports @@ -563,14 +563,14 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
host(1), named(8), dnssec-keygen(8), @@ -578,7 +578,7 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
There are probably too many query options.
diff --git a/bin/dig/host.html b/bin/dig/host.html index ea0aedd1f7..2e208f221e 100644 --- a/bin/dig/host.html +++ b/bin/dig/host.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - + @@ -22,7 +22,7 @@host — DNS lookup utility
@@ -32,7 +32,7 @@host [-aCdlnrTwv] [-c ] [class-N ] [ndots-R ] [number-t ] [type-W ] [wait-m ] [flag-4] [-6] {name} [server]
host is a simple utility for performing DNS lookups. It is normally used to convert names to IP addresses and vice versa. @@ -178,12 +178,12 @@
dig(1), named(8).
diff --git a/bin/dig/nslookup.html b/bin/dig/nslookup.html index 31df531faa..24dfc6a012 100644 --- a/bin/dig/nslookup.html +++ b/bin/dig/nslookup.html @@ -13,7 +13,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - + @@ -21,7 +21,7 @@nslookup — query Internet name servers interactively
@@ -31,7 +31,7 @@nslookup [-option] [name | -] [server]
Nslookup is a program to query Internet domain name servers. Nslookup has two modes: interactive and non-interactive. Interactive mode allows @@ -43,7 +43,7 @@
Interactive mode is entered in the following cases:
@@ -76,7 +76,7 @@ nslookup -query=hinfo -timeout=10Andrew Cherenson
diff --git a/bin/dnssec/dnssec-keygen.html b/bin/dnssec/dnssec-keygen.html index 4791fd258f..e1869d19a1 100644 --- a/bin/dnssec/dnssec-keygen.html +++ b/bin/dnssec/dnssec-keygen.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - + @@ -22,7 +22,7 @@dnssec-keygen — DNSSEC key generation tool
@@ -32,7 +32,7 @@dnssec-keygen {-a algorithm} {-b keysize} {-n nametype} [-c ] [class-e] [-f ] [flag-g ] [generator-h] [-k] [-p ] [protocol-r ] [randomdev-s ] [strength-t ] [type-v ] {name}level
dnssec-keygen generates keys for DNSSEC (Secure DNS), as defined in RFC 2535 and RFC <TBA\>. It can also generate keys for use with @@ -40,7 +40,7 @@
To generate a 768-bit DSA key for the domain
example.com, the following command would be
@@ -216,7 +216,7 @@
dnssec-signzone(8), BIND 9 Administrator Reference Manual, RFC 2535, @@ -225,7 +225,7 @@
dnssec-signzone — DNSSEC zone signing tool
@@ -32,7 +32,7 @@dnssec-signzone [-a] [-c ] [class-d ] [directory-e ] [end-time-f ] [output-file-g] [-h] [-k ] [key-l ] [domain-i ] [interval-I ] [input-format-j ] [jitter-n ] [nthreads-o ] [origin-O ] [output-format-p] [-r ] [randomdev-s ] [start-time-t] [-v ] [level-z] {zonefile} [key...]
dnssec-signzone signs a zone. It generates NSEC and RRSIG records and produces a signed version of the @@ -43,7 +43,7 @@
The following command signs the example.com
zone with the DSA key generated in the dnssec-keygen
@@ -246,14 +246,14 @@
lwresd — lightweight resolver daemon
@@ -32,7 +32,7 @@lwresd [-C ] [config-file-d ] [debug-level-f] [-g] [-i ] [pid-file-n ] [#cpus-P ] [port-p ] [port-s] [-t ] [directory-u ] [user-v]
lwresd is the daemon providing name lookup services to clients that use the BIND 9 lightweight resolver @@ -67,7 +67,7 @@
named.conf — configuration file for named
named.conf
named.conf is the configuration file
for
named. Statements are enclosed
@@ -50,14 +50,14 @@
masters string [ port integer ] {
( masters | ipv4_address [port integer] |
@@ -75,7 +75,7 @@ masters
server ( ipv4_address[/prefixlen] | ipv6_address[/prefixlen] ) {
bogus boolean;
@@ -96,7 +96,7 @@ server
trusted-keys {
domain_name flags protocol algorithm key; ...
@@ -104,7 +104,7 @@ trusted-keys
controls {
inet ( ipv4_address | ipv6_address | * )
@@ -116,7 +116,7 @@ controls
view string optional_class {
match-clients { address_match_element; ... };
@@ -424,7 +424,7 @@ view
zone string optional_class {
type ( master | slave | stub | hint |
@@ -504,12 +504,12 @@ zone
named(8), rndc(8), BIND 9 Administrator Reference Manual. diff --git a/bin/named/named.html b/bin/named/named.html index ae9bcbe827..b3d6cc1fe7 100644 --- a/bin/named/named.html +++ b/bin/named/named.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - +
@@ -22,7 +22,7 @@named — Internet domain name server
@@ -32,7 +32,7 @@named [-4] [-6] [-c ] [config-file-d ] [debug-level-f] [-g] [-n ] [#cpus-p ] [port-s] [-t ] [directory-u ] [user-v] [-x ]cache-file
named is a Domain Name System (DNS) server, part of the BIND 9 distribution from ISC. For more @@ -47,7 +47,7 @@
In routine operation, signals should not be used to control the nameserver; rndc should be used @@ -201,7 +201,7 @@
The named configuration file is too complex to describe in detail here. A complete description is provided @@ -210,7 +210,7 @@
nsupdate — Dynamic DNS update utility
@@ -32,7 +32,7 @@nsupdate [-d] [[-y ] | [keyname:secret-k ]] [keyfile-t ] [timeout-u ] [udptimeout-r ] [udpretries-v] [filename]
nsupdate is used to submit Dynamic DNS Update requests as defined in RFC2136 to a name server. @@ -164,7 +164,7 @@
The TSIG key is redundantly stored in two separate files. This is a consequence of nsupdate using the DST library diff --git a/bin/rndc/rndc-confgen.html b/bin/rndc/rndc-confgen.html index 9e4623de73..ee31c056d6 100644 --- a/bin/rndc/rndc-confgen.html +++ b/bin/rndc/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. --> - +
@@ -22,7 +22,7 @@rndc-confgen — rndc key generation tool
@@ -32,7 +32,7 @@rndc-confgen [-a] [-b ] [keysize-c ] [keyfile-h] [-k ] [keyname-p ] [port-r ] [randomfile-s ] [address-t ] [chrootdir-u ]user
rndc-confgen generates configuration files for rndc. It can be used as a @@ -48,7 +48,7 @@
rndc.conf — rndc configuration file
rndc.conf
rndc.conf is the configuration file
for rndc, the BIND 9 name server control
utility. This file has a similar structure and syntax to
@@ -117,7 +117,7 @@
The name server must be configured to accept rndc connections and
to recognize the key specified in the rndc.conf
@@ -201,7 +201,7 @@
rndc — name server control utility
@@ -32,7 +32,7 @@rndc [-b ] [source-address-c ] [config-file-k ] [key-file-s ] [server-p ] [port-V] [-y ] {command}key_id
rndc controls the operation of a name server. It supersedes the ndc utility @@ -61,7 +61,7 @@
source-address@@ -134,7 +134,7 @@
rndc does not yet support all the commands of the BIND 8 ndc utility. @@ -148,7 +148,7 @@
The Berkeley Internet Name Domain (BIND) implements an @@ -88,7 +88,7 @@
In this document, Section 1 introduces the basic DNS and BIND concepts. Section 2 @@ -117,7 +117,7 @@
In this document, we use the following general typographic conventions: @@ -244,7 +244,7 @@
The purpose of this document is to explain the installation and upkeep of the BIND software @@ -254,7 +254,7 @@
The Domain Name System (DNS) is the hierarchical, distributed database. It stores information for mapping Internet host names to @@ -274,7 +274,7 @@
The data stored in the DNS is identified by domain names that are organized as a tree according to organizational or administrative boundaries. Each node of the tree, @@ -320,7 +320,7 @@
To properly operate a name server, it is important to understand the difference between a zone @@ -373,7 +373,7 @@
Each zone is served by at least one authoritative name server, @@ -389,7 +389,7 @@
The authoritative server where the master copy of the zone data is maintained is @@ -405,7 +405,7 @@
The other authoritative servers, the slave servers (also known as secondary servers) @@ -421,7 +421,7 @@
Usually all of the zone's authoritative servers are listed in NS records in the parent zone. These NS records constitute @@ -456,7 +456,7 @@
The resolver libraries provided by most operating systems are stub resolvers, meaning that they are not @@ -483,7 +483,7 @@
Even a caching name server does not necessarily perform the complete recursive lookup itself. Instead, it can @@ -514,7 +514,7 @@
The BIND name server can simultaneously act as diff --git a/doc/arm/Bv9ARM.ch02.html b/doc/arm/Bv9ARM.ch02.html index c6dd9147c4..dc1ec19fdd 100644 --- a/doc/arm/Bv9ARM.ch02.html +++ b/doc/arm/Bv9ARM.ch02.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - +
@@ -45,16 +45,16 @@Table of Contents
DNS hardware requirements have traditionally been quite modest. @@ -73,7 +73,7 @@
CPU requirements for BIND 9 range from i486-class machines @@ -84,7 +84,7 @@
The memory of the server has to be large enough to fit the cache and zones loaded off disk. The max-cache-size @@ -107,7 +107,7 @@
For name server intensive environments, there are two alternative configurations that may be used. The first is where clients and @@ -124,7 +124,7 @@
ISC BIND 9 compiles and runs on a large number diff --git a/doc/arm/Bv9ARM.ch03.html b/doc/arm/Bv9ARM.ch03.html index abc6c39704..4b59618316 100644 --- a/doc/arm/Bv9ARM.ch03.html +++ b/doc/arm/Bv9ARM.ch03.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - +
@@ -47,14 +47,14 @@The following sample configuration is appropriate for a caching-only name server for use by clients internal to a corporation. All @@ -95,7 +95,7 @@ zone "0.0.127.in-addr.arpa" {
This sample configuration is for an authoritative-only server
that is the master server for "example.com"
@@ -137,7 +137,7 @@ zone "eng.example.com" {
A primitive form of load balancing can be achieved in the DNS by using multiple A records for @@ -284,10 +284,10 @@ zone "eng.example.com" {
There are several indispensable diagnostic, administrative and monitoring tools available to the system administrator for @@ -784,7 +784,7 @@ controls {
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 e07c110688..02e41d3ca0 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,28 +49,28 @@Setting up different views, or visibility, of the DNS space to internal and external resolvers is usually referred to as a Split DNS setup. There are several reasons an organization @@ -467,7 +467,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 @@ -475,7 +475,7 @@ nameserver 172.16.72.4
The following command will generate a 128 bit (16 byte) HMAC-MD5 key as described above. Longer keys are better, but shorter keys @@ -500,7 +500,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 @@ -515,7 +515,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. @@ -523,7 +523,7 @@ nameserver 172.16.72.4
Imagine host1 and host 2 are @@ -552,7 +552,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
@@ -584,7 +584,7 @@ server 10.1.2.3 {
BIND allows IP addresses and ranges to be specified in ACL @@ -612,7 +612,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 @@ -638,7 +638,7 @@ allow-update { key host1-host2. ;};
TKEY is a mechanism for automatically generating a shared secret between two hosts. There are several "modes" of @@ -674,7 +674,7 @@ allow-update { key host1-host2. ;};
BIND 9 partially supports DNSSEC SIG(0) transaction signatures as specified in RFC 2535 and RFC2931. @@ -736,7 +736,7 @@ allow-update { key host1-host2. ;};
The dnssec-keygen program is used to generate keys. @@ -787,7 +787,7 @@ allow-update { key host1-host2. ;};
The dnssec-signzone program is used to @@ -831,7 +831,7 @@ allow-update { key host1-host2. ;};
Unlike BIND 8, BIND 9 does not verify signatures on @@ -848,7 +848,7 @@ allow-update { key host1-host2. ;};
BIND 9 fully supports all currently defined forms of IPv6 @@ -892,7 +892,7 @@ allow-update { key host1-host2. ;};
The AAAA record is a parallel to the IPv4 A record. It specifies the entire address in a single record. For @@ -912,7 +912,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 9745b5ca77..9a3889a54c 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 2d434000ab..744830d300 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,52 +48,52 @@address_match_list= address_match_list_element ; [ address_match_list_element; ... ]address_match_list_element= [ ! ] (ip_address [/length] | @@ -421,7 +421,7 @@Address match lists are primarily used to determine access control for various server operations. They are also used in @@ -498,7 +498,7 @@
The BIND 9 comment syntax allows for comments to appear @@ -508,7 +508,7 @@
/* This is a BIND comment as in C */@@ -523,7 +523,7 @@Comments may appear anywhere that whitespace may appear in a BIND configuration file. @@ -757,7 +757,7 @@
acl acl-name { address_match_list }; @@ -840,7 +840,7 @@controls { inet ( ip_addr | * ) [ port ip_port ] allow {address_match_list} keys {key_list}; @@ -980,12 +980,12 @@includefilename;The include statement inserts the @@ -1000,7 +1000,7 @@
keykey_id{ algorithmstring; secretstring; @@ -1009,7 +1009,7 @@The key statement defines a shared secret key for use with TSIG (see the section called “TSIG”) @@ -1052,7 +1052,7 @@
logging { [ channelchannel_name{ ( filepath name@@ -1076,7 +1076,7 @@The logging statement configures a @@ -1110,7 +1110,7 @@
All log output goes to one or more channels; you can make as many of them as you want. @@ -1629,7 +1629,7 @@ category notify { null; };
This is the grammar of the lwres statement in the
named.conffile: @@ -1644,7 +1644,7 @@ category notify { null; };The lwres statement configures the name @@ -1695,14 +1695,14 @@ category notify { null; };
mastersname[portip_port] { (masters_list|ip_addr[portip_port] [keykey] ) ; [...] } ;masters lists allow for a common set of masters to be easily used by @@ -1711,7 +1711,7 @@ category notify { null; };
This is the grammar of the options statement in the
named.conffile: @@ -2697,7 +2697,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 @@ -2741,7 +2741,7 @@ options {
Dual-stack servers are used as servers of last resort to work around @@ -2906,7 +2906,7 @@ options {
The interfaces and ports that the server will answer queries from may be specified using the listen-on option. listen-on takes @@ -2986,7 +2986,7 @@ listen-on-v6 port 1234 { !2001:db8::/32; any; };
If the server doesn't know the answer to a question, it will query other name servers. query-source specifies @@ -3241,7 +3241,7 @@ query-source-v6 address * port *;
avoid-v4-udp-ports and avoid-v6-udp-ports specify a list of IPv4 and IPv6 UDP ports that will not be used as system @@ -3255,7 +3255,7 @@ query-source-v6 address * port *;
The server's usage of many system resources can be limited. Scaled values are allowed when specifying resource limits. For @@ -3315,7 +3315,7 @@ query-source-v6 address * port *;
The following options set limits on the server's resource consumption that are enforced internally by the @@ -3394,7 +3394,7 @@ query-source-v6 address * port *;
- cleaning-interval
@@ -4251,7 +4251,7 @@ query-source-v6 address * port *;
trusted-keys {stringnumbernumbernumberstring; [stringnumbernumbernumberstring; [...]] @@ -4260,7 +4260,7 @@ query-source-v6 address * port *;The trusted-keys statement defines @@ -4299,7 +4299,7 @@ query-source-v6 address * port *;
The view statement is a powerful new feature @@ -4472,10 +4472,10 @@ view "external" {
@@ -4684,7 +4684,7 @@ view "external" { The zone's name may optionally be followed by a class. If a class is not specified, class
IN(forInternet), @@ -4706,7 +4706,7 @@ view "external" {
- journal
@@ -5145,7 +5145,7 @@ view "external" {
@@ -5158,7 +5158,7 @@ view "external" {A domain name identifies a node. Each node has a set of resource information, which may be empty. The set of resource @@ -5747,7 +5747,7 @@ view "external" {
RRs are represented in binary form in the packets of the DNS protocol, and are usually represented in highly encoded form @@ -5954,7 +5954,7 @@ view "external" {
As described above, domain servers store information as a series of resource records, each of which contains a particular @@ -6211,7 +6211,7 @@ view "external" {
Reverse name resolution (that is, translation from IP address to name) is achieved by means of the in-addr.arpa domain @@ -6272,7 +6272,7 @@ view "external" {
The Master File Format was initially defined in RFC 1035 and has subsequently been extended. While the Master File Format @@ -6287,7 +6287,7 @@ view "external" {
Syntax: $ORIGIN
domain-name@@ -6315,7 +6315,7 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.Syntax: $INCLUDE
filename@@ -6351,7 +6351,7 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.Syntax: $TTL
default-ttl@@ -6370,7 +6370,7 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.Syntax: $GENERATE
@@ -46,11 +46,11 @@rangediff --git a/doc/arm/Bv9ARM.ch07.html b/doc/arm/Bv9ARM.ch07.html index 0dbcde1121..79482a56c0 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
@@ -114,7 +114,7 @@ zone "example.com" {
- Access Control Lists
-- chroot and setuid (for +
- chroot and setuid (for UNIX servers)
- Dynamic Update Security
On UNIX servers, it is possible to run BIND in a chrooted environment @@ -138,7 +138,7 @@ zone "example.com" {
In order for a chroot() environment to @@ -166,7 +166,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 72d7b95432..e138c77bd4 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 represents a @@ -95,7 +95,7 @@
The Internet Software Consortium (ISC) offers a wide range diff --git a/doc/arm/Bv9ARM.ch09.html b/doc/arm/Bv9ARM.ch09.html index 047704849d..80ea8cbbde 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. --> - +
@@ -43,24 +43,24 @@Table of Contents
Although the "official" beginning of the Domain Name System occurred in 1984 with the publication of RFC 920, the @@ -469,7 +469,7 @@
Standards
@@ -592,11 +592,11 @@[RFC974] Mail Routing and the Domain System. January 1986.
diff --git a/doc/arm/Bv9ARM.html b/doc/arm/Bv9ARM.html index b09944ca1d..7c23427241 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. --> - + @@ -40,7 +40,7 @@DNS and BIND. Copyright © 1998 Sebastopol, CA: O'Reilly and Associates.
@@ -51,39 +51,39 @@Copyright © 2004, 2005 Internet Systems Consortium, Inc. ("ISC")
Copyright © 2000-2003 Internet Software Consortium.
- 1. Introduction
- 2. BIND Resource Requirements
- 3. Name Server Configuration
- 4. Advanced DNS Features
@@ -92,33 +92,33 @@- 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
- -
- IPv6 Support in BIND 9
+- IPv6 Support in BIND 9
5. The BIND 9 Lightweight Resolver 6. BIND 9 Configuration Reference @@ -126,84 +126,84 @@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
-- trusted-keys Statement Grammar
-- trusted-keys Statement Definition +
- trusted-keys Statement Grammar
+- trusted-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
7. BIND 9 Security Considerations 8. Troubleshooting A. Appendices diff --git a/lib/lwres/man/lwres.html b/lib/lwres/man/lwres.html index 417c660202..c3839357ea 100644 --- a/lib/lwres/man/lwres.html +++ b/lib/lwres/man/lwres.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - + @@ -22,7 +22,7 @@ - +Name
lwres — introduction to the lightweight resolver library
@@ -32,7 +32,7 @@#include <lwres/lwres.h>-DESCRIPTION
+DESCRIPTION
The BIND 9 lightweight resolver library is a simple, name service independent stub resolver library. It provides hostname-to-address @@ -47,7 +47,7 @@
-OVERVIEW
+OVERVIEW
The lwresd library implements multiple name service APIs. The standard @@ -101,7 +101,7 @@
-CLIENT-SIDE LOW-LEVEL API CALL FLOW
+CLIENT-SIDE LOW-LEVEL API CALL FLOW
When a client program wishes to make an lwres request using the native low-level API, it typically performs the following @@ -149,7 +149,7 @@
-SERVER-SIDE LOW-LEVEL API CALL FLOW
+SERVER-SIDE LOW-LEVEL API CALL FLOW
When implementing the server side of the lightweight resolver protocol using the lwres library, a sequence of actions like the @@ -191,7 +191,7 @@
-SEE ALSO
+SEE ALSO
lwres_gethostent(3), lwres_getipnode(3), diff --git a/lib/lwres/man/lwres_buffer.html b/lib/lwres/man/lwres_buffer.html index 1ad8daa170..e84b506215 100644 --- a/lib/lwres/man/lwres_buffer.html +++ b/lib/lwres/man/lwres_buffer.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - +
@@ -22,7 +22,7 @@- +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
@@ -262,7 +262,7 @@ void-DESCRIPTION
+DESCRIPTION
These functions provide bounds checked access to a region of memory where data is being read or written. diff --git a/lib/lwres/man/lwres_config.html b/lib/lwres/man/lwres_config.html index 212b746b11..02ad87aed9 100644 --- a/lib/lwres/man/lwres_config.html +++ b/lib/lwres/man/lwres_config.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - +
@@ -22,7 +22,7 @@- +Name
lwres_conf_init, lwres_conf_clear, lwres_conf_parse, lwres_conf_print, lwres_conf_get — lightweight resolver configuration
@@ -90,7 +90,7 @@ lwres_conf_t *-DESCRIPTION
+DESCRIPTION
lwres_conf_init()creates an empty lwres_conf_t @@ -123,7 +123,7 @@ lwres_conf_t *-diff --git a/lib/lwres/man/lwres_context.html b/lib/lwres/man/lwres_context.html index 8abc79fc5a..a533a5486f 100644 --- a/lib/lwres/man/lwres_context.html +++ b/lib/lwres/man/lwres_context.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - + @@ -22,7 +22,7 @@RETURN VALUES
+RETURN VALUES
lwres_conf_parse()returns LWRES_R_SUCCESS if it successfully read and parsed @@ -142,13 +142,13 @@ lwres_conf_t *- +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
@@ -172,7 +172,7 @@ void *-DESCRIPTION
+DESCRIPTION
lwres_context_create()creates a lwres_context_t structure for use in lightweight resolver operations. It holds a socket and other @@ -258,7 +258,7 @@ void *-RETURN VALUES
+RETURN VALUES
lwres_context_create()returns LWRES_R_NOMEMORY if memory for the struct lwres_context could not be allocated, @@ -283,7 +283,7 @@ void *-SEE ALSO
+SEE ALSO
lwres_conf_init(3), malloc(3), diff --git a/lib/lwres/man/lwres_gabn.html b/lib/lwres/man/lwres_gabn.html index a17ac029fd..d74e6bb550 100644 --- a/lib/lwres/man/lwres_gabn.html +++ b/lib/lwres/man/lwres_gabn.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - +
@@ -22,7 +22,7 @@- +Name
lwres_gabnrequest_render, lwres_gabnresponse_render, lwres_gabnrequest_parse, lwres_gabnresponse_parse, lwres_gabnresponse_free, lwres_gabnrequest_free — lightweight resolver getaddrbyname message handling
@@ -178,7 +178,7 @@ void-DESCRIPTION
+DESCRIPTION
These are low-level routines for creating and parsing lightweight resolver name-to-address lookup request and @@ -278,7 +278,7 @@ typedef struct {
-diff --git a/lib/lwres/man/lwres_gai_strerror.html b/lib/lwres/man/lwres_gai_strerror.html index 183a63dd06..7d44788af2 100644 --- a/lib/lwres/man/lwres_gai_strerror.html +++ b/lib/lwres/man/lwres_gai_strerror.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - + @@ -22,7 +22,7 @@RETURN VALUES
+RETURN VALUES
The getaddrbyname opcode functions
lwres_gabnrequest_render(), @@ -316,7 +316,7 @@ typedef struct {-DESCRIPTION
+DESCRIPTION
lwres_gai_strerror()returns an error message corresponding to an error code returned bygetaddrinfo(). @@ -105,7 +105,7 @@ char *-SEE ALSO
+SEE ALSO
strerror(3), lwres_getaddrinfo(3), diff --git a/lib/lwres/man/lwres_getaddrinfo.html b/lib/lwres/man/lwres_getaddrinfo.html index 74bdbfd00c..1694c6bc79 100644 --- a/lib/lwres/man/lwres_getaddrinfo.html +++ b/lib/lwres/man/lwres_getaddrinfo.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - +
@@ -22,7 +22,7 @@- +Name
lwres_getaddrinfo, lwres_freeaddrinfo — socket address structure to host and service name
@@ -89,7 +89,7 @@ struct addrinfo {-DESCRIPTION
+DESCRIPTION
lwres_getaddrinfo()is used to get a list of IP addresses and port numbers for hosthostnameand service @@ -283,7 +283,7 @@ struct addrinfo {-RETURN VALUES
+RETURN VALUES
lwres_getaddrinfo()returns zero on success or one of the error codes listed in gai_strerror(3) @@ -294,7 +294,7 @@ struct addrinfo {-SEE ALSO
+SEE ALSO
lwres(3), lwres_getaddrinfo(3), diff --git a/lib/lwres/man/lwres_gethostent.html b/lib/lwres/man/lwres_gethostent.html index a1839fbd00..e8ca51ed7a 100644 --- a/lib/lwres/man/lwres_gethostent.html +++ b/lib/lwres/man/lwres_gethostent.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - +
@@ -22,7 +22,7 @@- +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
@@ -203,7 +203,7 @@ void-DESCRIPTION
+DESCRIPTION
These functions provide hostname-to-address and address-to-hostname lookups by means of the lightweight resolver. @@ -341,7 +341,7 @@ struct hostent {
-RETURN VALUES
+RETURN VALUES
The functions
lwres_gethostbyname(), @@ -405,7 +405,7 @@ struct hostent {-BUGS
+BUGS
@@ -22,7 +22,7 @@
lwres_gethostbyname(),lwres_gethostbyname2(),lwres_gethostbyaddr()diff --git a/lib/lwres/man/lwres_getipnode.html b/lib/lwres/man/lwres_getipnode.html index a83d97cdfe..997838c831 100644 --- a/lib/lwres/man/lwres_getipnode.html +++ b/lib/lwres/man/lwres_getipnode.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - +- +Name
lwres_getipnodebyname, lwres_getipnodebyaddr, lwres_freehostent — lightweight resolver nodename / address translation API
@@ -98,7 +98,7 @@ void-DESCRIPTION
+DESCRIPTION
These functions perform thread safe, protocol independent nodename-to-address and address-to-nodename @@ -217,7 +217,7 @@ struct hostent {
-RETURN VALUES
+RETURN VALUES
If an error occurs,
lwres_getipnodebyname()@@ -261,7 +261,7 @@ struct hostent {-SEE ALSO
+SEE ALSO
RFC2553, lwres(3), diff --git a/lib/lwres/man/lwres_getnameinfo.html b/lib/lwres/man/lwres_getnameinfo.html index 0ede27a468..ba37fab651 100644 --- a/lib/lwres/man/lwres_getnameinfo.html +++ b/lib/lwres/man/lwres_getnameinfo.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - +
@@ -22,7 +22,7 @@- +Name
lwres_getnameinfo — lightweight resolver socket address structure to hostname and @@ -82,7 +82,7 @@ int
-DESCRIPTION
+DESCRIPTION
This function is equivalent to the getnameinfo(3) function defined in RFC2133. @@ -149,13 +149,13 @@ int
-RETURN VALUES
+RETURN VALUES
lwres_getnameinfo()returns 0 on success or a non-zero error code if an error occurs.-BUGS
+BUGS
RFC2133 fails to define what the nonzero return values of getnameinfo(3) diff --git a/lib/lwres/man/lwres_getrrsetbyname.html b/lib/lwres/man/lwres_getrrsetbyname.html index 21f630bf79..2363f2cef5 100644 --- a/lib/lwres/man/lwres_getrrsetbyname.html +++ b/lib/lwres/man/lwres_getrrsetbyname.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - +
@@ -22,7 +22,7 @@- +Name
lwres_getrrsetbyname, lwres_freerrset — retrieve DNS records
@@ -102,7 +102,7 @@ struct rrsetinfo {-DESCRIPTION
+DESCRIPTION
lwres_getrrsetbyname()gets a set of resource records associated with ahostname,class, @@ -150,7 +150,7 @@ struct rrsetinfo {-diff --git a/lib/lwres/man/lwres_gnba.html b/lib/lwres/man/lwres_gnba.html index bcba813ae0..1a669200f9 100644 --- a/lib/lwres/man/lwres_gnba.html +++ b/lib/lwres/man/lwres_gnba.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - + @@ -22,7 +22,7 @@RETURN VALUES
+RETURN VALUES
lwres_getrrsetbyname()returns zero on success, and one of the following error codes if an error occurred: @@ -184,7 +184,7 @@ struct rrsetinfo {- +Name
lwres_gnbarequest_render, lwres_gnbaresponse_render, lwres_gnbarequest_parse, lwres_gnbaresponse_parse, lwres_gnbaresponse_free, lwres_gnbarequest_free — lightweight resolver getnamebyaddress message handling
@@ -183,7 +183,7 @@ void-DESCRIPTION
+DESCRIPTION
These are low-level routines for creating and parsing lightweight resolver address-to-name lookup request and @@ -270,7 +270,7 @@ typedef struct {
-diff --git a/lib/lwres/man/lwres_hstrerror.html b/lib/lwres/man/lwres_hstrerror.html index 139fea0ebb..8a33d2b890 100644 --- a/lib/lwres/man/lwres_hstrerror.html +++ b/lib/lwres/man/lwres_hstrerror.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - + @@ -22,7 +22,7 @@RETURN VALUES
+RETURN VALUES
The getnamebyaddr opcode functions
lwres_gnbarequest_render(), @@ -308,7 +308,7 @@ typedef struct {- +Name
lwres_herror, lwres_hstrerror — lightweight resolver error message generation
@@ -40,7 +40,7 @@ const char *-DESCRIPTION
+DESCRIPTION
lwres_herror()prints the stringson stderr followed by the string generated by @@ -74,7 +74,7 @@ const char *-RETURN VALUES
+RETURN VALUES
The string Unknown resolver error is returned by
lwres_hstrerror()@@ -84,7 +84,7 @@ const char *-SEE ALSO
+SEE ALSO
herror(3), lwres_hstrerror(3). diff --git a/lib/lwres/man/lwres_inetntop.html b/lib/lwres/man/lwres_inetntop.html index de48f90538..de4f080128 100644 --- a/lib/lwres/man/lwres_inetntop.html +++ b/lib/lwres/man/lwres_inetntop.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - +
@@ -22,7 +22,7 @@- +Name
lwres_net_ntop — lightweight resolver IP address presentation
@@ -62,7 +62,7 @@ const char *-DESCRIPTION
+DESCRIPTION
lwres_net_ntop()converts an IP address of protocol familyaf— IPv4 or IPv6 — at @@ -80,7 +80,7 @@ const char *-RETURN VALUES
+RETURN VALUES
If successful, the function returns
dst: a pointer to a string containing the presentation format of the @@ -93,7 +93,7 @@ const char *-SEE ALSO
+SEE ALSO
RFC1884, inet_ntop(3), errno(3). diff --git a/lib/lwres/man/lwres_noop.html b/lib/lwres/man/lwres_noop.html index 29abba2f55..f79ced557a 100644 --- a/lib/lwres/man/lwres_noop.html +++ b/lib/lwres/man/lwres_noop.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - +
@@ -22,7 +22,7 @@- +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
@@ -179,7 +179,7 @@ void-DESCRIPTION
+DESCRIPTION
These are low-level routines for creating and parsing lightweight resolver no-op request and response messages. @@ -270,7 +270,7 @@ typedef struct {
-diff --git a/lib/lwres/man/lwres_packet.html b/lib/lwres/man/lwres_packet.html index b3dfbd1f43..d9e1bb56f7 100644 --- a/lib/lwres/man/lwres_packet.html +++ b/lib/lwres/man/lwres_packet.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - + @@ -22,7 +22,7 @@RETURN VALUES
+RETURN VALUES
The no-op opcode functions
lwres_nooprequest_render(), @@ -309,7 +309,7 @@ typedef struct {- +Name
lwres_lwpacket_renderheader, lwres_lwpacket_parseheader — lightweight resolver packet handling functions
@@ -66,7 +66,7 @@ lwres_result_t-DESCRIPTION
+DESCRIPTION
These functions rely on a struct lwres_lwpacket @@ -219,7 +219,7 @@ struct lwres_lwpacket {
-RETURN VALUES
+RETURN VALUES
Successful calls to
@@ -22,7 +22,7 @@lwres_lwpacket_renderheader()and diff --git a/lib/lwres/man/lwres_resutil.html b/lib/lwres/man/lwres_resutil.html index 235c79e01e..b2ad2770ad 100644 --- a/lib/lwres/man/lwres_resutil.html +++ b/lib/lwres/man/lwres_resutil.html @@ -14,7 +14,7 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - +- +Name
lwres_string_parse, lwres_addr_parse, lwres_getaddrsbyname, lwres_getnamebyaddr — lightweight resolver utility functions
@@ -134,7 +134,7 @@ lwres_result_t-DESCRIPTION
+DESCRIPTION
lwres_string_parse()retrieves a DNS-encoded string starting the current pointer of lightweight resolver bufferb: i.e. @@ -210,7 +210,7 @@ typedef struct {