diff --git a/bin/check/named-checkconf.docbook b/bin/check/named-checkconf.docbook index a5e50334e2..a9329c954e 100644 --- a/bin/check/named-checkconf.docbook +++ b/bin/check/named-checkconf.docbook @@ -105,7 +105,7 @@ Chroot to directory so that include directives in the configuration file are processed as if - run by a similarly chrooted named. + run by a similarly chrooted named. diff --git a/bin/check/named-checkzone.docbook b/bin/check/named-checkzone.docbook index 9e827f398d..7512f476b6 100644 --- a/bin/check/named-checkzone.docbook +++ b/bin/check/named-checkzone.docbook @@ -431,7 +431,7 @@ Chroot to directory so that include directives in the configuration file are processed as if - run by a similarly chrooted named. + run by a similarly chrooted named. diff --git a/bin/named/named.conf.docbook b/bin/named/named.conf.docbook index 3dc483cce1..78f692f633 100644 --- a/bin/named/named.conf.docbook +++ b/bin/named/named.conf.docbook @@ -30,7 +30,7 @@ named.conf - configuration file for named + configuration file for named diff --git a/bin/rndc/rndc.docbook b/bin/rndc/rndc.docbook index c67b8b7e75..bb99a70781 100644 --- a/bin/rndc/rndc.docbook +++ b/bin/rndc/rndc.docbook @@ -193,7 +193,7 @@ from the configuration file. key_id must be - known by named with the same algorithm and secret string + known by named with the same algorithm and secret string in order for control message validation to succeed. If no key_id is specified, rndc will first look @@ -649,7 +649,7 @@ NTA's lifetime is elapsed. - NTAs persist across restarts of the named server. + NTAs persist across restarts of the named server. The NTAs for a view are saved in a file called name.nta, where name is the diff --git a/doc/arm/Bv9ARM-book.xml b/doc/arm/Bv9ARM-book.xml index d2c0a64950..b85123e796 100644 --- a/doc/arm/Bv9ARM-book.xml +++ b/doc/arm/Bv9ARM-book.xml @@ -5349,7 +5349,7 @@ badresp:1,adberr:0,findfail:0,valfail:0] Specifying lock-file none disables the use of a lock file. lock-file is - ignored if named was run using the + ignored if named was run using the option, which overrides it. Changes to lock-file are ignored if named is being reloaded or diff --git a/doc/arm/dlz.xml b/doc/arm/dlz.xml index d98bc698f9..b8070ae7c4 100644 --- a/doc/arm/dlz.xml +++ b/doc/arm/dlz.xml @@ -27,7 +27,7 @@ written for any other. - Historically, DLZ drivers had to be statically linked with the named + Historically, DLZ drivers had to be statically linked with the named binary and were turned on via a configure option at compile time (for example, "configure --with-dlz-ldap"). Currently, the drivers provided in the BIND 9 tarball in @@ -38,15 +38,15 @@ In BIND 9.8 and higher, it is possible to link some DLZ modules dynamically at runtime, via the DLZ "dlopen" driver, which acts as a generic wrapper around a shared object implementing the DLZ API. The - "dlopen" driver is linked into named by default, so configure options + "dlopen" driver is linked into named by default, so configure options are no longer necessary when using these dynamically linkable drivers, but are still needed for the older drivers in contrib/dlz/drivers. - When the DLZ module provides data to named, it does so in text format. - The response is converted to DNS wire format by named. This + When the DLZ module provides data to named, it does so in text format. + The response is converted to DNS wire format by named. This conversion, and the lack of any internal caching, places significant limits on the query performance of DLZ modules. Consequently, DLZ is not recommended for use on high-volume servers. However, it can be diff --git a/doc/arm/dnssec.xml b/doc/arm/dnssec.xml index 4b058eb8b0..c2efb2a5b6 100644 --- a/doc/arm/dnssec.xml +++ b/doc/arm/dnssec.xml @@ -273,7 +273,7 @@ Periodic re-signing - In any secure zone which supports dynamic updates, named + In any secure zone which supports dynamic updates, named will periodically re-sign RRsets which have not been re-signed as a result of some update action. The signature lifetimes will be adjusted so as to spread the re-sign load over time rather than diff --git a/doc/arm/notes.xml b/doc/arm/notes.xml index 2a99ad5fc9..e544456c5f 100644 --- a/doc/arm/notes.xml +++ b/doc/arm/notes.xml @@ -135,7 +135,7 @@ can be changed by setting the in named.conf. When added, NTAs are stored in a file (viewname.nta) - in order to persist across restarts of the named server. + in order to persist across restarts of the named server. @@ -224,7 +224,7 @@ named -L filename - causes named to send log messages to the specified file by + causes named to send log messages to the specified file by default instead of to the system log. @@ -443,7 +443,7 @@ - If named is not configured to validate the answer then + If named is not configured to validate the answer then allow fallback to plain DNS on timeout even when we know the server supports EDNS. This will allow the server to potentially resolve signed queries when TCP is being diff --git a/doc/arm/pkcs11.xml b/doc/arm/pkcs11.xml index 385e497223..4fd03aa00c 100644 --- a/doc/arm/pkcs11.xml +++ b/doc/arm/pkcs11.xml @@ -604,7 +604,7 @@ $ dnssec-signzone -E '' -S example.net If you want named to dynamically re-sign zones using HSM keys, and/or to to sign new records inserted via nsupdate, - then named must have access to the HSM PIN. In OpenSSL-based PKCS#11, + then named must have access to the HSM PIN. In OpenSSL-based PKCS#11, this is accomplished by placing the PIN into the openssl.cnf file (in the above examples, /opt/pkcs11/usr/ssl/openssl.cnf). @@ -612,7 +612,7 @@ $ dnssec-signzone -E '' -S example.net The location of the openssl.cnf file can be overridden by setting the OPENSSL_CONF environment variable before running - named. + named. Sample openssl.cnf: