boolean; // not yet implementedboolean;boolean;querysource4;querysource6;ipv4_address | * ) | [ address ( ipv4_address | * ) ] ) [ port ( integer | * ) ];ipv6_address | * ) | [ address ( ipv6_address | * ) ] ) [ port ( integer | * ) ];integer;integer; // not implementedinteger;
view string optional_class {
match-clients { address_match_element; ... };
@@ -351,8 +351,8 @@ view
rfc2308-type1 boolean; // not yet implemented
additional-from-auth boolean;
additional-from-cache boolean;
- query-source querysource4;
- query-source-v6 querysource6;
+ query-source ( ( ipv4_address | * ) | [ address ( ipv4_address | * ) ] ) [ port ( integer | * ) ];
+ query-source-v6 ( ( ipv6_address | * ) | [ address ( ipv6_address | * ) ] ) [ port ( integer | * ) ];
cleaning-interval integer;
min-roots integer; // not implemented
lame-ttl integer;
@@ -451,7 +451,7 @@ view
zone string optional_class {
type ( master | slave | stub | hint |
@@ -535,12 +535,12 @@ zone
named(8), rndc(8), BIND 9 Administrator Reference Manual. diff --git a/doc/arm/Bv9ARM.ch03.html b/doc/arm/Bv9ARM.ch03.html index d993fa56e3..edd9b03c0c 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. --> - +
@@ -54,7 +54,7 @@rndc [-c config] [-s server] [-p port] [-y key] command [command...]
command +
The command is one of the following:
halt [-p]traceCertain 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 e07692fc08..9fd2c47684 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 @@ -347,7 +347,7 @@
Here is an example configuration for the setup we just described above. Note that this is only configuration information; - for information on how to configure your zone files, see the section called “Sample Configurations” + for information on how to configure your zone files, see the section called “Sample Configurations”.
Internal DNS server config: @@ -479,7 +479,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 @@ -487,7 +487,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 @@ -512,7 +512,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 @@ -527,7 +527,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. @@ -535,7 +535,7 @@ nameserver 172.16.72.4
Imagine host1 and host 2 are @@ -564,7 +564,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
@@ -596,7 +596,7 @@ server 10.1.2.3 {
BIND allows IP addresses and ranges to be specified in ACL @@ -624,11 +624,11 @@ 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 - server, a FORMERR will be returned, since the server will not + server, a FORMERR (format error) will be returned, since the server will not understand the record. This is a result of misconfiguration, since the server must be explicitly configured to send a TSIG signed message to a specific server. @@ -644,13 +644,13 @@ allow-update { key host1-host2. ;}; the TSIG extended error code set to BADTIME, and the time values will be adjusted so that the response can be successfully verified. In any of these cases, the message's rcode is set to - NOTAUTH. + NOTAUTH (not authenticated).
TKEY is a mechanism for automatically generating a shared secret between two hosts. There are several "modes" of @@ -686,7 +686,7 @@ allow-update { key host1-host2. ;};
BIND 9 partially supports DNSSEC SIG(0)
transaction signatures as specified in RFC 2535 and RFC2931.
@@ -735,7 +735,7 @@ allow-update { key host1-host2. ;};
There must also be communication with the administrators of
the parent and/or child zone to transmit keys. A zone's security
status must be indicated by the parent zone for a DNSSEC capable
- resolver to trust its data. This is done through the presense
+ resolver to trust its data. This is done through the presence
or absence of a DS record at the
delegation
point.
@@ -747,7 +747,7 @@ allow-update { key host1-host2. ;};
The dnssec-keygen program is used to generate keys. @@ -798,7 +798,7 @@ allow-update { key host1-host2. ;};
The dnssec-signzone program is used to @@ -842,7 +842,7 @@ allow-update { key host1-host2. ;};
To enable named to respond appropriately
to DNS requests from DNSSEC aware clients
@@ -852,12 +852,12 @@ allow-update { key host1-host2. ;};
To enable named to validate answers from
other servers both dnssec-enable and
dnssec-validate must be set and some
- some trusted-keys must be configured
+ trusted-keys must be configured
into named.conf.
trusted-keys are copies of DNSKEY RRs - for zones that are used to form the first link the the + for zones that are used to form the first link in the cryptographic chain of trust. All keys listed in trusted-keys (and corresponding zones) are deemed to exist and only the listed keys will be used @@ -923,14 +923,14 @@ options {
BIND 9 fully supports all currently defined forms of IPv6 @@ -969,7 +969,7 @@ options {
The IPv6 AAAA record is a parallel to the IPv4 A record, and, unlike the deprecated A6 record, specifies the entire @@ -988,7 +988,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 330444d47a..5fd5d74e00 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 30e859950d..64102846c2 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] | @@ -437,7 +437,7 @@Address match lists are primarily used to determine access control for various server operations. They are also used in @@ -515,7 +515,7 @@
The BIND 9 comment syntax allows for comments to appear @@ -525,7 +525,7 @@
/* This is a BIND comment as in C */@@ -540,9 +540,9 @@- Comments may appear anywhere that whitespace may appear in + Comments may appear anywhere that white space may appear in a BIND configuration file.
@@ -697,7 +697,7 @@
@@ -774,7 +774,7 @@ configures named to - also act as a light weight resolver daemon (lwresd). + also act as a light-weight resolver daemon (lwresd).
acl acl-name { address_match_list }; @@ -857,7 +857,7 @@controls { [ inet ( ip_addr | * ) [ port ip_port ] allow {address_match_list} keys {key_list}; ] @@ -882,7 +882,7 @@ An inet control channel is a TCP socket listening at the specified ip_port on the specified ip_addr, which can be an IPv4 or IPv6 - address. An ip_addr of*is + address. An ip_addr of*(asterisk) is interpreted as the IPv4 wildcard address; connections will be accepted on any of the system's IPv4 addresses. To listen on the IPv6 wildcard address, @@ -892,7 +892,7 @@ or::1) is recommended for maximum security.- If no port is specified, port 953 is used. + If no port is specified, port 953 is used. The asterisk "
*" cannot be used for ip_port.@@ -906,7 +906,7 @@ are ignored.
- An unix control channel is a UNIX domain + A unix control channel is a UNIX domain socket listening at the specified path in the file system. Access to the socket is specified by the perm, owner and group clauses. @@ -979,12 +979,12 @@
includefilename;The include statement inserts the @@ -999,7 +999,7 @@
keykey_id{ algorithmstring; secretstring; @@ -1008,7 +1008,7 @@The key statement defines a shared secret key for use with TSIG (see the section called “TSIG”) @@ -1055,7 +1055,7 @@
logging { [ channelchannel_name{ ( filepath name@@ -1079,7 +1079,7 @@The logging statement configures a @@ -1113,7 +1113,7 @@
All log output goes to one or more channels; you can make as many of them as you want. @@ -1252,7 +1252,7 @@ with the
-dflag followed by a positive integer, or by running rndc trace. The global debug level - can be set to zero, and debugging mode turned off, by running ndc + can be set to zero, and debugging mode turned off, by running rndc notrace. All debugging messages in the server have a debug level, and higher debug levels give more detailed output. Channels that specify a specific debug severity, for example: @@ -1330,7 +1330,7 @@ channel null { special property that it only produces output when the server's debug level is - nonzero. It normally writes to a filenamed.run+ nonzero. It normally writes to a file callednamed.runin the server's working directory.@@ -1557,7 +1557,7 @@ category notify { null; }; Specify where queries should be logged to.
- At startup, specifing the category queries will also + At startup, specifying the category queries will also enable query logging unless querylog option has been specified.
@@ -1632,7 +1632,7 @@ category notify { null; };This is the grammar of the lwres statement in the
named.conffile: @@ -1647,12 +1647,12 @@ category notify { null; };The lwres statement configures the name - server to also act as a lightweight resolver server, see - the section called “Running a Resolver Daemon”. There may be be multiple + server to also act as a lightweight resolver server. (See + the section called “Running a Resolver Daemon”.) There may be be multiple lwres statements configuring lightweight resolver servers with different properties.
@@ -1698,14 +1698,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 @@ -1714,7 +1714,7 @@ category notify { null; };
This is the grammar of the options statement in the
named.conffile: @@ -1972,7 +1972,7 @@ digits" + "tkey-domain". In most cases, If not specified, the default isnamed.statsin the server's current directory. The format of the file is described - in the section called “The Statistics File” + in the section called “The Statistics File”.
@@ -2013,7 +2013,7 @@ digits" + "tkey-domain". In most cases,
- Turn on enforcement of delegation-only in TLDs and root zones + Turn on enforcement of delegation-only in TLDs (top level domains) and root zones with an optional exclude list.
@@ -2329,7 +2329,7 @@ options {
When the nameserver exits due receiving SIGTERM,
- flush / do not flush any pending zone writes. The default
+ flush or do not flush any pending zone writes. The default
is
flush-zones-on-shutdown no.
@@ -2489,7 +2489,7 @@ options { request-ixfr in the section called “server Statement Definition and - Usage” + Usage”.
@@ -2680,7 +2680,7 @@ options { the default is ignore.
- The rules for legal hostnames / mail domains are derived + The rules for legal hostnames or mail domains are derived from RFC 952 and RFC 821 as modified by RFC 1123.
check-names @@ -2743,12 +2743,14 @@ options {
When returning authoritative negative responses to SOA queries set the TTL of the SOA recored returned in - the authority section to zero. Default yes. + the authority section to zero. + The default is yes.
When caching a negative response to a SOA query - set the TTL to zero. Default no. + set the TTL to zero. + The default is no.
@@ -2757,13 +2759,14 @@ options { the DNSKEY RR to determine if this key should be used to generate the RRSIG. This flag is ignored if there are not DNSKEY RRs both with and without - a KSK. Default yes. + a KSK. + The default is yes.
The forwarding facility can be used to create a large site-wide cache on a few servers, reducing traffic over links to external @@ -2807,7 +2810,7 @@ options {
Dual-stack servers are used as servers of last resort to work around @@ -2818,7 +2821,7 @@ options {
- Specifies host names / addresses of machines with access to + Specifies host names or addresses of machines with access to both IPv4 and IPv6 transports. If a hostname is used the server must be able to resolve the name using only the transport it has. If the @@ -2967,7 +2970,7 @@ options {
The interfaces and ports that the server will answer queries from may be specified using the listen-on option. listen-on takes @@ -3047,7 +3050,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 @@ -3188,7 +3191,7 @@ query-source-v6 address * port *; only supported by relatively new slave servers, such as BIND 9, BIND 8.x and BIND 4.9.5 onwards. - The many-answers format also supported by + The many-answers format is also supported by recent Microsoft Windows nameservers. The default is many-answers. transfer-format may be overridden on a @@ -3303,7 +3306,7 @@ query-source-v6 address * port *; server's masters zone clause or in an allow-notify clause. This statement sets the notify-source - for all zones, but can be overridden on a per-zone / + for all zones, but can be overridden on a per-zone or per-view basis by including a notify-source statement within the zone or @@ -3327,7 +3330,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 @@ -3341,7 +3344,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 @@ -3353,8 +3356,7 @@ query-source-v6 address * port *; maximum available amount. default uses the limit that was in force when the server was started. See the description - of - size_spec in the section called “Configuration File Elements”. + of size_spec in the section called “Configuration File Elements”.
The following options set operating system resource limits for @@ -3401,7 +3403,7 @@ query-source-v6 address * port *;
The following options set limits on the server's resource consumption that are enforced internally by the @@ -3418,7 +3420,7 @@ query-source-v6 address * port *;
Sets a maximum size for each journal file - (the section called “The journal file”). When the journal file + (see the section called “The journal file”). When the journal file approaches the specified size, some of the oldest transactions in the journal @@ -3479,7 +3481,7 @@ query-source-v6 address * port *;
@@ -3805,8 +3807,8 @@ query-source-v6 address * port *; be silently truncated to 7 days if set to a greater value.
max-cache-ttl - sets the maximum time for which the server will +
+ Sets the maximum time for which the server will cache ordinary (positive) answers. The default is one week (7 days).
- Not implemented in BIND9. + Not implemented in BIND 9.
masterfile-format specifies +
Specifies
the file format of zone files (see
the section called “Additional File Formats”).
The default value is text, which is the
@@ -3902,7 +3904,7 @@ query-source-v6 address * port *;
specified in the named configuration
file. This statement sets the
masterfile-format for all zones,
- but can be overridden on a per-zone / per-view basis
+ but can be overridden on a per-zone or per-view basis
by including a masterfile-format
statement within the zone or
view block in the configuration
@@ -3912,8 +3914,7 @@ query-source-v6 address * port *;
clients-per-query, max-clients-per-query
clients-per-query - and max-clients-per-query set the +
These set the initial value (minimum) and maximum number of recursive simultanious clients for any given query (<qname,qtype,qclass>) that the server will accept @@ -3939,7 +3940,7 @@ query-source-v6 address * port *;
If max-clients-per-query is set to zero then there is no upper bound other than imposed by - recurive-clients. + recursive-clients.
+ disable-empty-zone "."; ++
If you are using the address ranges covered here you should @@ -4117,8 +4122,13 @@ query-source-v6 address * port *; generated by BIND 8.
- The statistics dump begins with the line +++ Statistics Dump -+++ (973798949), where the number in parentheses is a standard + The statistics dump begins with a line, like: +
++ +++ Statistics Dump +++ (973798949) +
++ The number in parentheses is a standard Unix-style timestamp, measured as seconds since January 1, 1970. Following that line are a series of lines containing a counter type, the @@ -4128,9 +4138,14 @@ query-source-v6 address * port *; the entire server. Lines with a zone and view name for the given view and zone (the view name is - omitted for the default view). The statistics dump ends - with the line --- Statistics Dump --- (973798949), where the - number is identical to the number in the beginning line. + omitted for the default view). +
++ The statistics dump ends with the line where the + number is identical to the number in the beginning line; for example: +
++ --- Statistics Dump --- (973798949)
The following statistics counters are maintained: @@ -4514,7 +4529,7 @@ query-source-v6 address * port *;
trusted-keys {
string number number number string ;
[ string number number number string ; [...]]
@@ -4523,7 +4538,7 @@ query-source-v6 address * port *;
The trusted-keys statement defines
@@ -4566,7 +4581,7 @@ query-source-v6 address * port *;
The view statement is a powerful
feature
@@ -4817,10 +4832,10 @@ zone zone_name [
zone_name [zone_name [
The zone's name may optionally be followed by a class. If
a class is not specified, class IN (for Internet),
@@ -5051,23 +5066,17 @@ zone zone_name [
-- journal
-
- Allow the default journal's file name to be overridden.
- The default is the zone's file with ".jnl" appended.
- This is applicable to master and slave zones.
-
- allow-notify
See the description of
- allow-notify in the section called “Access Control”
+ allow-notify in the section called “Access Control”.
- allow-query
See the description of
- allow-query in the section called “Access Control”
+ allow-query in the section called “Access Control”.
- allow-transfer
@@ -5218,6 +5227,12 @@ zone zone_name [BIND 8.
Ignored in BIND 9.
- journal
+
+ Allow the default journal's file name to be overridden.
+ The default is the zone's file with ".jnl" appended.
+ This is applicable to master and slave zones.
+
- max-transfer-time-in
See the description of
@@ -5268,32 +5283,32 @@ zone zone_name [transfer-source
See the description of
- transfer-source in the section called “Zone Transfers”
+ transfer-source in the section called “Zone Transfers”.
- transfer-source-v6
See the description of
- transfer-source-v6 in the section called “Zone Transfers”
+ transfer-source-v6 in the section called “Zone Transfers”.
- alt-transfer-source
See the description of
- alt-transfer-source in the section called “Zone Transfers”
+ alt-transfer-source in the section called “Zone Transfers”.
- alt-transfer-source-v6
See the description of
- alt-transfer-source-v6 in the section called “Zone Transfers”
+ alt-transfer-source-v6 in the section called “Zone Transfers”.
- use-alt-transfer-source
See the description of
- use-alt-transfer-source in the section called “Zone Transfers”
+ use-alt-transfer-source in the section called “Zone Transfers”.
- notify-source
See the description of
- notify-source in the section called “Zone Transfers”
+ notify-source in the section called “Zone Transfers”.
- notify-source-v6
@@ -5316,7 +5331,7 @@ zone zone_name [key-directory in the section called “options Statement Definition and
- Usage”
+ Usage”.
- multi-master
@@ -5534,7 +5549,7 @@ zone zone_name [
@@ -5547,7 +5562,7 @@ zone zone_name [
A domain name identifies a node. Each node has a set of
resource information, which may be empty. The set of resource
@@ -5870,7 +5885,7 @@ zone zone_name [
- Identifies a mail exchange for the domain.
+ Identifies a mail exchange for the domain with
a 16 bit preference value (lower is better)
followed by the host name of the mail exchange.
Described in RFC 974, RFC 1035.
@@ -6198,7 +6213,7 @@ zone zone_name [
RRs are represented in binary form in the packets of the DNS
protocol, and are usually represented in highly encoded form
@@ -6401,7 +6416,7 @@ zone zone_name [
As described above, domain servers store information as a
series of resource records, each of which contains a particular
@@ -6659,7 +6674,7 @@ zone zone_name [
Reverse name resolution (that is, translation from IP address
to name) is achieved by means of the in-addr.arpa domain
@@ -6720,7 +6735,7 @@ zone zone_name [
The Master File Format was initially defined in RFC 1035 and
has subsequently been extended. While the Master File Format
@@ -6735,7 +6750,7 @@ zone zone_name [
Syntax: $ORIGIN
domain-name
@@ -6763,7 +6778,7 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
Syntax: $INCLUDE
filename
@@ -6799,7 +6814,7 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
Syntax: $TTL
default-ttl
@@ -6818,7 +6833,7 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
Syntax: $GENERATE
range
@@ -6892,10 +6907,10 @@ $GENERATE 1-127 $ CNAME $.0
{ immediately following the
$ as
${offset[,width[,base]]}.
- e.g. ${-20,3,d} which
+ For example, ${-20,3,d}
subtracts 20 from the current value, prints the
result as a decimal in a zero padded field of
- with 3.
+ width 3.
Available output forms are decimal
(d), octal
@@ -6909,7 +6924,7 @@ $GENERATE 1-127 $ CNAME $.0
For compatibility with earlier versions $$ is still
- recognized a indicating a literal $ in the output.
+ recognized as indicating a literal $ in the output.
@@ -6918,8 +6933,8 @@ $GENERATE 1-127 $ CNAME $.0
ttl
- ttl
- specifies the ttl of the generated records. If
+
+ Specifies the time-to-live of the generated records. If
not specified this will be inherited using the
normal ttl inheritance rules.
@@ -6934,8 +6949,8 @@ $GENERATE 1-127 $ CNAME $.0
class
- class
- specifies the class of the generated records.
+
+ Specifies the class of the generated records.
This must match the zone class if it is
specified.
@@ -6962,7 +6977,7 @@ $GENERATE 1-127 $ CNAME $.0
- rhs is a domain name. It is processed
+ A domain name. It is processed
similarly to lhs.
diff --git a/doc/arm/Bv9ARM.ch07.html b/doc/arm/Bv9ARM.ch07.html
index 1b9870af86..1321894ef8 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
@@ -85,6 +85,7 @@ acl bogusnets {
0.0.0.0/8; 1.0.0.0/8; 2.0.0.0/8; 192.0.2.0/24; 224.0.0.0/3;
10.0.0.0/8; 172.16.0.0/12; 192.168.0.0/16;
};
+
// Set up an ACL called our-nets. Replace this with the real IP numbers.
acl our-nets { x.x.x.x/24; x.x.x.x/21; };
options {
@@ -96,6 +97,7 @@ options {
blackhole { bogusnets; };
...
};
+
zone "example.com" {
type master;
file "m/example.com";
@@ -116,7 +118,7 @@ zone "example.com" {
On UNIX servers, it is possible to run BIND in a chrooted environment
(chroot()) by specifying the "-t"
@@ -139,9 +141,9 @@ zone "example.com" {
- In order for a chroot() environment
+ In order for a chroot environment
to
work properly in a particular directory
(for example, /var/named),
@@ -161,13 +163,13 @@ zone "example.com" {
to set up things like
/dev/zero,
/dev/random,
- /dev/log, and/or
+ /dev/log, and
/etc/localtime.
Prior to running the named daemon,
use
diff --git a/doc/arm/Bv9ARM.ch08.html b/doc/arm/Bv9ARM.ch08.html
index 3be206d2b7..19fefb16ee 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 Systems Consortium
(ISC) offers a wide range
diff --git a/doc/arm/Bv9ARM.ch09.html b/doc/arm/Bv9ARM.ch09.html
index e7a061ab3c..88538201a3 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,21 +45,21 @@
Table of Contents
@@ -94,7 +94,10 @@
under
a grant from the US Defense Advanced Research Projects
Administration
- (DARPA). Versions of BIND through
+ (DARPA).
+
+
+ Versions of BIND through
4.8.3 were maintained by the Computer
Systems Research Group (CSRG) at UC Berkeley. Douglas Terry, Mark
Painter, David Riggle and Songnian Zhou made up the initial BIND
@@ -145,7 +148,7 @@
Standards
[RFC974] Mail Routing and the Domain System. January 1986.
@@ -250,7 +253,7 @@
[RFC1995] Incremental Zone Transfer in DNS. August 1996.
[RFC1996] A Mechanism for Prompt Notification of Zone Changes. August 1996.
[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.
[RFC2845] Secret Key Transaction Authentication for DNS (TSIG). May 2000.
[RFC2930] Secret Key Establishment for DNS (TKEY RR). September 2000.
@@ -417,11 +420,11 @@
DNS and BIND. Copyright © 1998 Sebastopol, CA: O'Reilly and Associates.
diff --git a/doc/arm/Bv9ARM.html b/doc/arm/Bv9ARM.html
index 172935810f..8bebaa5916 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,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,83 +126,83 @@
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
I. Manual pages
diff --git a/doc/arm/man.dig.html b/doc/arm/man.dig.html
index 793bcbc4c4..2486c9c43e 100644
--- a/doc/arm/man.dig.html
+++ b/doc/arm/man.dig.html
@@ -14,7 +14,7 @@
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
+
@@ -52,7 +52,7 @@
dig [global-queryopt...] [query...]
-DESCRIPTION
+DESCRIPTION
dig
(domain information groper) is a flexible tool
for interrogating DNS name servers. It performs DNS lookups and
@@ -91,7 +91,7 @@
-OPTIONS
+OPTIONS
The -b option sets the source IP address of the query
to address. This must be a valid
@@ -237,7 +237,7 @@
-QUERY OPTIONS
+QUERY OPTIONS
dig
provides a number of query options which affect
the way in which lookups are made and the results displayed. Some of
@@ -556,7 +556,7 @@
-MULTIPLE QUERIES
+MULTIPLE QUERIES
The BIND 9 implementation of dig
supports
@@ -602,7 +602,7 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
-IDN SUPPORT
+IDN SUPPORT
If dig has been built with IDN (internationalized
domain name) support, it can accept and display non-ASCII domain names.
@@ -616,14 +616,14 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
-SEE ALSO
+SEE ALSO
host(1),
named(8),
dnssec-keygen(8),
@@ -631,7 +631,7 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
-BUGS
+BUGS
There are probably too many query options.
diff --git a/doc/arm/man.dnssec-keygen.html b/doc/arm/man.dnssec-keygen.html
index e063393286..9530152baa 100644
--- a/doc/arm/man.dnssec-keygen.html
+++ b/doc/arm/man.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.
-->
-
+
@@ -50,7 +50,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 level] {name}
-DESCRIPTION
+DESCRIPTION
dnssec-keygen
generates keys for DNSSEC (Secure DNS), as defined in RFC 2535
and RFC <TBA\>. It can also generate keys for use with
@@ -58,7 +58,7 @@
-EXAMPLE
+EXAMPLE
To generate a 768-bit DSA key for the domain
example.com, the following command would be
@@ -233,7 +233,7 @@
-SEE ALSO
+SEE ALSO
dnssec-signzone(8),
BIND 9 Administrator Reference Manual,
RFC 2535,
@@ -242,7 +242,7 @@
diff --git a/doc/arm/man.dnssec-signzone.html b/doc/arm/man.dnssec-signzone.html
index 09c8854dfe..48fd2f5c20 100644
--- a/doc/arm/man.dnssec-signzone.html
+++ b/doc/arm/man.dnssec-signzone.html
@@ -14,7 +14,7 @@
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
+
@@ -50,7 +50,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 soa-serial-format] [-o origin] [-O output-format] [-p] [-r randomdev] [-s start-time] [-t] [-v level] [-z] {zonefile} [key...]
-DESCRIPTION
+DESCRIPTION
dnssec-signzone
signs a zone. It generates
NSEC and RRSIG records and produces a signed version of the
@@ -61,7 +61,7 @@
-EXAMPLE
+EXAMPLE
The following command signs the example.com
zone with the DSA key generated in the dnssec-keygen
@@ -283,14 +283,14 @@
diff --git a/doc/arm/man.host.html b/doc/arm/man.host.html
index ff83ad3339..764e84ead2 100644
--- a/doc/arm/man.host.html
+++ b/doc/arm/man.host.html
@@ -14,7 +14,7 @@
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
+
@@ -50,7 +50,7 @@
host [-aCdlnrsTwv] [-c class] [-N ndots] [-R number] [-t type] [-W wait] [-m flag] [-4] [-6] {name} [server]
-DESCRIPTION
+DESCRIPTION
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 @@
-IDN SUPPORT
+IDN SUPPORT
If host has been built with IDN (internationalized
domain name) support, it can accept and display non-ASCII domain names.
@@ -216,12 +216,12 @@
-SEE ALSO
+SEE ALSO
dig(1),
named(8).
diff --git a/doc/arm/man.named-checkconf.html b/doc/arm/man.named-checkconf.html
index 2f49dd6491..e8cb15657f 100644
--- a/doc/arm/man.named-checkconf.html
+++ b/doc/arm/man.named-checkconf.html
@@ -14,7 +14,7 @@
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
+
@@ -50,14 +50,14 @@
named-checkconf [-v] [-j] [-t directory] {filename} [-z]
-DESCRIPTION
+DESCRIPTION
named-checkconf
checks the syntax, but not the semantics, of a named
configuration file.
-RETURN VALUES
+RETURN VALUES
named-checkconf
returns an exit status of 1 if
errors were detected and 0 otherwise.
diff --git a/doc/arm/man.named-checkzone.html b/doc/arm/man.named-checkzone.html
index 3ce08b0ed0..ee6be9393c 100644
--- a/doc/arm/man.named-checkzone.html
+++ b/doc/arm/man.named-checkzone.html
@@ -14,7 +14,7 @@
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
+
@@ -51,7 +51,7 @@
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] {zonename} {filename}
-DESCRIPTION
+DESCRIPTION
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 @@
-RETURN VALUES
+RETURN VALUES
named-checkzone
returns an exit status of 1 if
errors were detected and 0 otherwise.
diff --git a/doc/arm/man.named.html b/doc/arm/man.named.html
index 782f08057c..544c813d18 100644
--- a/doc/arm/man.named.html
+++ b/doc/arm/man.named.html
@@ -14,7 +14,7 @@
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
+
@@ -50,7 +50,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]
-DESCRIPTION
+DESCRIPTION
named
is a Domain Name System (DNS) server,
part of the BIND 9 distribution from ISC. For more
@@ -65,7 +65,7 @@
-SIGNALS
+SIGNALS
In routine operation, signals should not be used to control
the nameserver; rndc should be used
@@ -219,7 +219,7 @@
-CONFIGURATION
+CONFIGURATION
The named configuration file is too complex
to describe in detail here. A complete description is provided
@@ -228,7 +228,7 @@
diff --git a/doc/arm/man.rndc-confgen.html b/doc/arm/man.rndc-confgen.html
index 01b805eb60..3dd8418942 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.
-->
-
+
@@ -48,7 +48,7 @@
rndc-confgen [-a] [-b keysize] [-c keyfile] [-h] [-k keyname] [-p port] [-r randomfile] [-s address] [-t chrootdir] [-u user]
-DESCRIPTION
+DESCRIPTION
rndc-confgen
generates configuration files
for rndc. It can be used as a
@@ -64,7 +64,7 @@
diff --git a/doc/arm/man.rndc.conf.html b/doc/arm/man.rndc.conf.html
index 883879fe76..9580fa8234 100644
--- a/doc/arm/man.rndc.conf.html
+++ b/doc/arm/man.rndc.conf.html
@@ -14,7 +14,7 @@
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
+
@@ -50,7 +50,7 @@
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
The name server must be configured to accept rndc connections and
to recognize the key specified in the rndc.conf
@@ -219,7 +219,7 @@
diff --git a/doc/arm/man.rndc.html b/doc/arm/man.rndc.html
index dcc448fb58..6a43989e98 100644
--- a/doc/arm/man.rndc.html
+++ b/doc/arm/man.rndc.html
@@ -14,7 +14,7 @@
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-
+
@@ -50,7 +50,7 @@
rndc [-b source-address] [-c config-file] [-k key-file] [-s server] [-p port] [-V] [-y key_id] {command}