Set the DSCP code point to be used when sending the query. Valid DSCP code points are in the range - [0..63]. By default no code point is explictly set. + [0..63]. By default no code point is explicitly set.
+[no]edns[=#]@@ -545,7 +545,7 @@
+[no]subnet=addr/prefix- Send an EDNS Client Subnet option with the speciifed + Send an EDNS Client Subnet option with the specified IP address or network prefix.
+[no]tcp
This option is mandatory unless the -f has
been used to specify a zone file. (If -f has
- been specified, this option may still be used; it will overrde
+ been specified, this option may still be used; it will override
the value found in the file.)
-L to
dnssec-keygen. (If either of those is true,
- this option may still be used; it will overrde the value found
+ this option may still be used; it will override the value found
in the zone or key file.)
diff --git a/bin/rndc/rndc.8 b/bin/rndc/rndc.8
index fd1b2e0bdf..8758edd908 100644
--- a/bin/rndc/rndc.8
+++ b/bin/rndc/rndc.8
@@ -20,11 +20,11 @@
.\" Title: rndc
.\" Author:
.\" Generator: DocBook XSL Stylesheets v1.71.1 flushtree [-all] name [view] flushtree name [view] Flushes the given name, and all of its subdomains, from the server's DNS cache, the address database, @@ -581,7 +581,7 @@
There is currently no way to provide the shared secret for a
key_id without using the configuration file.
@@ -591,7 +591,7 @@
./configure --enable-native-pkcs11 \
The modified OpenSSL code is included in the BIND 9 release,
- in the form of a context diff against the latest verions of
+ in the form of a context diff against the latest versions of
OpenSSL. OpenSSL 0.9.8, 1.0.0, and 1.0.1 are supported; there are
separate diffs for each version. In the examples to follow,
we use OpenSSL 0.9.8, but the same methods work with OpenSSL
@@ -2020,7 +2020,7 @@ $ dnssec-signzone -E '' -S example.net
- DLZ (Dynamically Loadable Zones) is an extention to BIND 9 that allows
+ DLZ (Dynamically Loadable Zones) is an extension to BIND 9 that allows
zone data to be retrieved directly from an external database. There is
no required format or schema. DLZ drivers exist for several different
database backends including PostgreSQL, MySQL, and LDAP and can be
diff --git a/doc/arm/Bv9ARM.ch06.html b/doc/arm/Bv9ARM.ch06.html
index ec241708ec..5115b571ac 100644
--- a/doc/arm/Bv9ARM.ch06.html
+++ b/doc/arm/Bv9ARM.ch06.html
@@ -437,7 +437,7 @@
In most cases, setting a value to 0 does not
literally mean zero; it means "undefined" or
"as big as possible", depending on the context.
- See the expalantions of particular parameters
+ See the explanations of particular parameters
that use size_spec
for details on how they interpret its use.
@@ -3082,7 +3082,7 @@ options {
restarted (NTA's do not persist across restarts).
- For convienience, TTL-style time unit suffixes can be
+ For convenience, TTL-style time unit suffixes can be
used to specify the NTA lifetime in seconds, minutes
or hours. nta-lifetime defaults to
one hour. It cannot exceed one day.
@@ -3107,13 +3107,13 @@ options {
the negative trust anchor is allowed to expire early.
- Validity checks can be disabled for an indivdiual
+ Validity checks can be disabled for an individual
NTA by using rndc nta -f, or
for all NTA's by setting nta-recheck
to zero.
- For convienience, TTL-style time unit suffixes can be
+ For convenience, TTL-style time unit suffixes can be
used to specify the NTA recheck interval in seconds,
minutes or hours. The default is five minutes.
@@ -4406,7 +4406,7 @@ options {
than matching the case of the records entered in
the zone file. This allows responses to exactly
match the query, which is required by some clients
- due to incorrect use of case-sensitive comparisions.
+ due to incorrect use of case-sensitive comparisons.
Case-insensitive compression is always
@@ -4414,12 +4414,12 @@ options {
the client matches this ACL.
- There are circusmstances in which named
+ There are circumstances in which named
will not preserve the case of owner names of records:
if a zone file defines records of different types with
the same name, but the capitalization of the name is
different (e.g., "www.example.com/A" and
- "WWW.EXAMPLE.COM/AAAA"), then all resposnes for that
+ "WWW.EXAMPLE.COM/AAAA"), then all responses for that
name will use the first version
of the name that was used in the zone file. This
limitation may be addressed in a future release. However,
@@ -6772,7 +6772,7 @@ rate-limit {
is over 1000 and the ratio is over 10),
the one that appears last in the configuration file is the
one chosen. To eliminate any ambiguity, it is recommended
- that under normal circumstnaces, rate limiting bands should
+ that under normal circumstances, rate limiting bands should
be configured using either size or
ratio parameters, but not both.
@@ -10316,8 +10316,7 @@ view external {
Each RR can have a TTL as the second
field in the RR, which will control how long other
- servers can cache
- the it.
+ servers can cache it.
diff --git a/doc/arm/Bv9ARM.ch09.html b/doc/arm/Bv9ARM.ch09.html
index 086e266214..6d3e33fa49 100644
--- a/doc/arm/Bv9ARM.ch09.html
+++ b/doc/arm/Bv9ARM.ch09.html
@@ -57,13 +57,13 @@
BIND 9 DNS Library Support
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
@@ -856,7 +856,7 @@ $ make
consists of a single domain name. Example:
www.example.com
- mx.examle.net
+ mx.example.net
ns.xxx.example
@@ -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 f010db7c88..ad13583dfa 100644
--- a/doc/arm/Bv9ARM.html
+++ b/doc/arm/Bv9ARM.html
@@ -251,13 +251,13 @@
BIND 9 DNS Library Support
I. Manual pages
diff --git a/doc/arm/dlz.xml b/doc/arm/dlz.xml
index 74a9f2a500..d98bc698f9 100644
--- a/doc/arm/dlz.xml
+++ b/doc/arm/dlz.xml
@@ -1,6 +1,6 @@