docbook <command> tags around named server references

bin/check/named-checkconf.docbook

@@ -105,7 +105,7 @@
           <para>
             Chroot to <filename>directory</filename> so that include
             directives in the configuration file are processed as if
-            run by a similarly chrooted named.
+            run by a similarly chrooted <command>named</command>.
           </para>
         </listitem>
       </varlistentry>

bin/check/named-checkzone.docbook

@@ -431,7 +431,7 @@
             Chroot to <filename>directory</filename> so that
             include
             directives in the configuration file are processed as if
-            run by a similarly chrooted named.
+            run by a similarly chrooted <command>named</command>.
           </para>
         </listitem>
       </varlistentry>

bin/named/named.conf.docbook

@@ -30,7 +30,7 @@
 
   <refnamediv>
     <refname><filename>named.conf</filename></refname>
-    <refpurpose>configuration file for named</refpurpose>
+    <refpurpose>configuration file for <command>named</command></refpurpose>
   </refnamediv>
 
   <docinfo>

bin/rndc/rndc.docbook

@@ -193,7 +193,7 @@
 	    from the configuration file.
 	    <replaceable class="parameter">key_id</replaceable>
 	    must be
-	    known by named with the same algorithm and secret string
+	    known by <command>named</command> with the same algorithm and secret string
 	    in order for control message validation to succeed.
 	    If no <replaceable class="parameter">key_id</replaceable>
 	    is specified, <command>rndc</command> will first look
@@ -649,7 +649,7 @@
 	    NTA's lifetime is elapsed.
 	  </para>
 	  <para>
-	    NTAs persist across restarts of the named server.
+	    NTAs persist across restarts of the <command>named</command> server.
 	    The NTAs for a view are saved in a file called
 	    <filename><replaceable>name</replaceable>.nta</filename>,
 	    where <replaceable>name</replaceable> is the

doc/arm/Bv9ARM-book.xml

@@ -5349,7 +5349,7 @@ badresp:1,adberr:0,findfail:0,valfail:0]
 	      <para>
 		Specifying <command>lock-file none</command> disables the
 		use of a lock file.  <command>lock-file</command> is
-		ignored if named was run using the <option>-X</option>
+		ignored if <command>named</command> was run using the <option>-X</option>
 		option, which overrides it.  Changes to
 		<command>lock-file</command> are ignored if
 		<command>named</command> is being reloaded or

doc/arm/dlz.xml

@@ -27,7 +27,7 @@
     written for any other.
   </para>
   <para>
-    Historically, DLZ drivers had to be statically linked with the named
+    Historically, DLZ drivers had to be statically linked with the <command>named</command>
     binary and were turned on via a configure option at compile time (for
     example, <userinput>"configure --with-dlz-ldap"</userinput>).
     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 <command>named</command> by default, so configure options
     are no longer necessary when using these dynamically linkable drivers,
     but are still needed for the older drivers in
     <filename>contrib/dlz/drivers</filename>.
   </para>
 
   <para>
-    When the DLZ module provides data to named, it does so in text format.
+    When the DLZ module provides data to <command>named</command>, it does so in text format.
-    The response is converted to DNS wire format by named.  This
+    The response is converted to DNS wire format by <command>named</command>.  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

doc/arm/dnssec.xml

@@ -273,7 +273,7 @@
   <sect2>
     <title>Periodic re-signing</title>
   </sect2>
-  <para>In any secure zone which supports dynamic updates, named
+  <para>In any secure zone which supports dynamic updates, <command>named</command>
   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

doc/arm/notes.xml

@@ -135,7 +135,7 @@
 	  can be changed by setting the <option>nta-lifetime</option> in
 	  <filename>named.conf</filename>. When added, NTAs are stored in a
 	  file (<filename><replaceable>viewname</replaceable>.nta</filename>)
-	  in order to persist across restarts of the named server.
+	  in order to persist across restarts of the <command>named</command> server.
 	</para>
       </listitem>
       <listitem>
@@ -224,7 +224,7 @@
       <listitem>
 	<para>
 	  <command>named -L <replaceable>filename</replaceable></command>
-	  causes named to send log messages to the specified file by
+	  causes <command>named</command> to send log messages to the specified file by
 	  default instead of to the system log.
 	</para>
       </listitem>
@@ -443,7 +443,7 @@
       </listitem>
       <listitem>
 	<para>
-	  If named is not configured to validate the answer then
+	  If <command>named</command> 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

doc/arm/pkcs11.xml

@@ -604,7 +604,7 @@ $ <userinput>dnssec-signzone -E '' -S example.net</userinput>
     <para>
       If you want <command>named</command> 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 <command>named</command> 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, 
       <filename>/opt/pkcs11/usr/ssl/openssl.cnf</filename>).
@@ -612,7 +612,7 @@ $ <userinput>dnssec-signzone -E '' -S example.net</userinput>
     <para>
       The location of the openssl.cnf file can be overridden by
       setting the OPENSSL_CONF environment variable before running
-      named.
+      <command>named</command>.
     </para>
     <para>Sample openssl.cnf:</para>
     <programlisting>