From: Tinderbox User
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.
@@ -545,7 +545,7 @@
- Send an EDNS Client Subnet option with the speciifed
+ Send an EDNS Client Subnet option with the specified
IP address or network prefix.
This option is mandatory unless the +[no]edns[=#]+[no]subnet=addr/prefix+[no]tcp-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.)
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 ec241708eca..5115b571ac7 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 086e2662146..6d3e33fa49d 100644
--- a/doc/arm/Bv9ARM.ch09.html
+++ b/doc/arm/Bv9ARM.ch09.html
@@ -57,13 +57,13 @@
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 @@ $
makeThe 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 @@ $
makeSome 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 @@ $
makeSimilar to "sample", but accepts a list of (query) domain names as a separate file and resolves the names @@ -856,7 +856,7 @@ $
makeconsists of a single domain name. Example:@@ -864,7 +864,7 @@ $
www.example.com
- mx.examle.net
+ mx.example.net
ns.xxx.example
makeIt sends a query to a specified server, and prints the response with minimal processing. It doesn't act as a @@ -905,7 +905,7 @@ $
makeThis is a test program to check getaddrinfo() and getnameinfo() behavior. It takes a @@ -922,7 +922,7 @@ $
makeIt 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+mmIt 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+mmAs 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 f010db7c888..ad13583dfa8 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/man.arpaname.html b/doc/arm/man.arpaname.html index 80250b32645..19af0c9d781 100644 --- a/doc/arm/man.arpaname.html +++ b/doc/arm/man.arpaname.html @@ -50,20 +50,20 @@
arpaname{ipaddress...}-diff --git a/doc/arm/man.ddns-confgen.html b/doc/arm/man.ddns-confgen.html index f41cd01b801..8be73c57ff3 100644 --- a/doc/arm/man.ddns-confgen.html +++ b/doc/arm/man.ddns-confgen.html @@ -51,7 +51,7 @@DESCRIPTION
+DESCRIPTION
arpaname translates IP addresses (IPv4 and IPv6) to the corresponding IN-ADDR.ARPA or IP6.ARPA names.
ddns-confgen[-a] [algorithm-h] [-k] [keyname-q] [-r] [ -srandomfilename| -zzone]-diff --git a/doc/arm/man.dig.html b/doc/arm/man.dig.html index 566a838572f..66783cec33f 100644 --- a/doc/arm/man.dig.html +++ b/doc/arm/man.dig.html @@ -52,7 +52,7 @@DESCRIPTION
+DESCRIPTION
tsig-keygen and ddns-confgen are invocation methods for a utility that generates keys for use @@ -87,7 +87,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 @@ -392,7 +392,7 @@
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[=#]@@ -563,7 +563,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.
diff --git a/doc/arm/man.dnssec-coverage.html b/doc/arm/man.dnssec-coverage.html index 71bdbee4f4d..aebe0dcac05 100644 --- a/doc/arm/man.dnssec-coverage.html +++ b/doc/arm/man.dnssec-coverage.html @@ -126,7 +126,7 @@ +[no]tcpThis option is mandatory unless the
@@ -152,7 +152,7 @@ been used to specify a zone file, or a default key TTL was set with the-fhas been used to specify a zone file. (If-fhas - 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.)-Lto 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/doc/arm/man.genrandom.html b/doc/arm/man.genrandom.html index d0187ae6ea7..263ae5ef8e7 100644 --- a/doc/arm/man.genrandom.html +++ b/doc/arm/man.genrandom.html @@ -50,7 +50,7 @@
genrandom[-n] {numbersize} {filename}-diff --git a/doc/arm/man.isc-hmac-fixup.html b/doc/arm/man.isc-hmac-fixup.html index 964c6899628..c678e25dade 100644 --- a/doc/arm/man.isc-hmac-fixup.html +++ b/doc/arm/man.isc-hmac-fixup.html @@ -50,7 +50,7 @@DESCRIPTION
+DESCRIPTION
genrandom generates a file or a set of files containing a specified quantity @@ -59,7 +59,7 @@
isc-hmac-fixup{algorithm} {secret}-DESCRIPTION
+DESCRIPTION
Versions of BIND 9 up to and including BIND 9.6 had a bug causing HMAC-SHA* TSIG keys which were longer than the digest length of the @@ -76,7 +76,7 @@
-diff --git a/doc/arm/man.nsec3hash.html b/doc/arm/man.nsec3hash.html index fdca850f2ac..0ca8b3dac49 100644 --- a/doc/arm/man.nsec3hash.html +++ b/doc/arm/man.nsec3hash.html @@ -48,7 +48,7 @@SECURITY CONSIDERATIONS
+SECURITY CONSIDERATIONS
Secrets that have been converted by isc-hmac-fixup are shortened, but as this is how the HMAC protocol works in @@ -87,14 +87,14 @@
nsec3hash{salt} {algorithm} {iterations} {domain}-diff --git a/doc/arm/man.rndc-confgen.html b/doc/arm/man.rndc-confgen.html index 64a11b2b0ff..b5d8c92d198 100644 --- a/doc/arm/man.rndc-confgen.html +++ b/doc/arm/man.rndc-confgen.html @@ -50,7 +50,7 @@DESCRIPTION
+DESCRIPTION
nsec3hash generates an NSEC3 hash based on a set of NSEC3 parameters. This can be used to check the validity @@ -56,7 +56,7 @@
rndc-confgen[-a] [-A] [algorithm-b] [keysize-c] [keyfile-h] [-k] [keyname-p] [port-r] [randomfile-s] [address-t] [chrootdir-u]user-diff --git a/doc/arm/man.rndc.conf.html b/doc/arm/man.rndc.conf.html index 706fa9e2558..bdf924038d0 100644 --- a/doc/arm/man.rndc.conf.html +++ b/doc/arm/man.rndc.conf.html @@ -50,7 +50,7 @@DESCRIPTION
+DESCRIPTION
rndc-confgen generates configuration files for rndc. It can be used as a @@ -66,7 +66,7 @@
rndc.conf-DESCRIPTION
+DESCRIPTION
rndc.confis the configuration file for rndc, the BIND 9 name server control utility. This file has a similar structure and syntax to @@ -136,7 +136,7 @@-diff --git a/doc/arm/man.rndc.html b/doc/arm/man.rndc.html index 09f91247b1a..f44a773c48f 100644 --- a/doc/arm/man.rndc.html +++ b/doc/arm/man.rndc.html @@ -50,7 +50,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@@ -220,7 +220,7 @@
rndc[-b] [source-address-c] [config-file-k] [key-file-s] [server-p] [port-q] [-V] [-y] {command}key_id-DESCRIPTION
+DESCRIPTION
rndc controls the operation of a name server. It supersedes the ndc utility @@ -81,7 +81,7 @@
-COMMANDS
+COMMANDS
A list of commands supported by rndc can be seen by running rndc without arguments. @@ -375,7 +375,7 @@ and, if applicable, from the server's nameserver address database or bad-server cache.
-+ flushtree[-all]name[view]flushtreename[view]Flushes the given name, and all of its subdomains, from the server's DNS cache, the address database, @@ -599,7 +599,7 @@
-diff --git a/lib/lwres/man/lwres.3 b/lib/lwres/man/lwres.3 index 32338b780d4..2c03e3ae9ff 100644 --- a/lib/lwres/man/lwres.3 +++ b/lib/lwres/man/lwres.3 @@ -39,7 +39,7 @@ lwres \- introduction to the lightweight resolver library .PP The BIND 9 lightweight resolver library is a simple, name service independent stub resolver library. It provides hostname\-to\-address and address\-to\-hostname lookup services to applications by transmitting lookup requests to a resolver daemon \fBlwresd\fR -running on the local host. The resover daemon performs the lookup using the DNS or possibly other name service protocols, and returns the results to the application through the library. The library and resolver daemon communicate using a simple UDP\-based protocol. +running on the local host. The resolver daemon performs the lookup using the DNS or possibly other name service protocols, and returns the results to the application through the library. The library and resolver daemon communicate using a simple UDP\-based protocol. .SH "OVERVIEW" .PP The lwresd library implements multiple name service APIs. The standard diff --git a/lib/lwres/man/lwres.html b/lib/lwres/man/lwres.html index 27ddd7efa5c..da5ab517dcd 100644 --- a/lib/lwres/man/lwres.html +++ b/lib/lwres/man/lwres.html @@ -39,7 +39,7 @@ and address-to-hostname lookup services to applications by transmitting lookup requests to a resolver daemon lwresd - running on the local host. The resover daemon performs the + running on the local host. The resolver daemon performs the lookup using the DNS or possibly other name service protocols, and returns the results to the application through the library. The library and resolver daemon communicate using a simple diff --git a/lib/lwres/man/lwres_gabn.3 b/lib/lwres/man/lwres_gabn.3 index cb1e93fc4c2..f67126eb545 100644 --- a/lib/lwres/man/lwres_gabn.3 +++ b/lib/lwres/man/lwres_gabn.3 @@ -53,7 +53,7 @@ These are low\-level routines for creating and parsing lightweight resolver name .PP There are four main functions for the getaddrbyname opcode. One render function converts a getaddrbyname request structure \(em \fBlwres_gabnrequest_t\fR -\(em to the lighweight resolver's canonical format. It is complemented by a parse function that converts a packet in this canonical format to a getaddrbyname request structure. Another render function converts the getaddrbyname response structure \(em +\(em to the lightweight resolver's canonical format. It is complemented by a parse function that converts a packet in this canonical format to a getaddrbyname request structure. Another render function converts the getaddrbyname response structure \(em \fBlwres_gabnresponse_t\fR \(em to the canonical format. This is complemented by a parse function which converts a packet in canonical format to a getaddrbyname response structure. .PP diff --git a/lib/lwres/man/lwres_gabn.html b/lib/lwres/man/lwres_gabn.html index afff8a3c08a..ef40b67b8be 100644 --- a/lib/lwres/man/lwres_gabn.html +++ b/lib/lwres/man/lwres_gabn.html @@ -188,7 +188,7 @@ void There are four main functions for the getaddrbyname opcode. One render function converts a getaddrbyname request structure — lwres_gabnrequest_t — - to the lighweight resolver's canonical format. + to the lightweight resolver's canonical format. It is complemented by a parse function that converts a packet in this canonical format to a getaddrbyname request structure. Another render function converts the getaddrbyname response structure diff --git a/lib/lwres/man/lwres_noop.3 b/lib/lwres/man/lwres_noop.3 index 6dffc53b95c..cacbd4b6a4c 100644 --- a/lib/lwres/man/lwres_noop.3 +++ b/lib/lwres/man/lwres_noop.3 @@ -57,7 +57,7 @@ packet: a packet is sent to the resolver daemon and is simply echoed back. The o .PP There are four main functions for the no\-op opcode. One render function converts a no\-op request structure \(em \fBlwres_nooprequest_t\fR -\(em to the lighweight resolver's canonical format. It is complemented by a parse function that converts a packet in this canonical format to a no\-op request structure. Another render function converts the no\-op response structure \(em +\(em to the lightweight resolver's canonical format. It is complemented by a parse function that converts a packet in this canonical format to a no\-op request structure. Another render function converts the no\-op response structure \(em \fBlwres_noopresponse_t\fR to the canonical format. This is complemented by a parse function which converts a packet in canonical format to a no\-op response structure. .PP diff --git a/lib/lwres/man/lwres_noop.html b/lib/lwres/man/lwres_noop.html index cad87024d7b..39a1a20915a 100644 --- a/lib/lwres/man/lwres_noop.html +++ b/lib/lwres/man/lwres_noop.html @@ -195,7 +195,7 @@ void There are four main functions for the no-op opcode. One render function converts a no-op request structure — lwres_nooprequest_t — - to the lighweight resolver's canonical format. + to the lightweight resolver's canonical format. It is complemented by a parse function that converts a packet in this canonical format to a no-op request structure. Another render function converts the no-op response structure — diff --git a/lib/lwres/man/lwres_resutil.3 b/lib/lwres/man/lwres_resutil.3 index c80fd70f1c7..0125c788d13 100644 --- a/lib/lwres/man/lwres_resutil.3 +++ b/lib/lwres/man/lwres_resutil.3 @@ -97,7 +97,7 @@ functions. .PP The lightweight resolver uses \fBlwres_getaddrsbyname()\fR -to perform foward lookups. Hostname +to perform forward lookups. Hostname \fIname\fR is looked up using the resolver context \fIctx\fR diff --git a/lib/lwres/man/lwres_resutil.html b/lib/lwres/man/lwres_resutil.html index 1a45a5705ab..5f9a3d972f7 100644 --- a/lib/lwres/man/lwres_resutil.html +++ b/lib/lwres/man/lwres_resutil.html @@ -186,7 +186,7 @@ typedef struct {LIMITATIONS
+LIMITATIONS
There is currently no way to provide the shared secret for a
key_idwithout using the configuration file. @@ -609,7 +609,7 @@The lightweight resolver uses
lwres_getaddrsbyname()to perform - foward lookups. + forward lookups. Hostnamenameis looked up using the resolver contextctxfor memory allocation.