[deployment-guide/comm-rel: 381/727] Updated the MX resource record description.

Jaromir Hradilek jhradile at fedoraproject.org
Tue Oct 19 12:56:45 UTC 2010


commit 4ec6071b8e5e3a2eebe59e98009acfc9f38f0f03
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Mon Aug 16 15:10:45 2010 +0200

    Updated the MX resource record description.

 en-US/The_BIND_DNS_Server.xml |   20 ++++++++++----------
 1 files changed, 10 insertions(+), 10 deletions(-)
---
diff --git a/en-US/The_BIND_DNS_Server.xml b/en-US/The_BIND_DNS_Server.xml
index 1b9fb85..efe620a 100644
--- a/en-US/The_BIND_DNS_Server.xml
+++ b/en-US/The_BIND_DNS_Server.xml
@@ -1171,21 +1171,21 @@ www IN CNAME server1</screen>
           <term><command>MX</command></term>
           <listitem>
             <para>
-              This refers to the Mail eXchange record, which tells where mail sent to a particular namespace controlled by this zone should go.
+              The <firstterm>Mail eXchange</firstterm> record specifies where the mail sent to a particular namespace controlled by this zone should go. It takes the following form:
             </para>
-            <screen>IN MX <replaceable>&lt;preference-value&gt;</replaceable>
-              <replaceable>&lt;email-server-name&gt;</replaceable></screen>
+            <screen>IN MX <replaceable>preference-value</replaceable> <replaceable>email-server-name</replaceable></screen>
             <para>
-              <!-- RHEL5:  In this example,  -->Here, the <replaceable>&lt;preference-value&gt;</replaceable> allows numerical ranking of the email servers for a namespace, giving preference to some email systems over others. The <command>MX</command> resource record with the lowest <replaceable>&lt;preference-value&gt;</replaceable> is preferred over the others. However, multiple email servers can possess the same value to distribute email traffic evenly among them.
+              The <replaceable>email-server-name</replaceable> is fully qualified domain name (FQDN). The <replaceable>preference-value</replaceable> allows numerical ranking of the email servers for a namespace, giving preference to some email systems over others. The <command>MX</command> resource record with the lowest <replaceable>preference-value</replaceable> is preferred over the others. However, multiple email servers can possess the same value to distribute email traffic evenly among them.
             </para>
             <para>
-              The <replaceable>&lt;email-server-name&gt;</replaceable> is FQDN.
-            </para>
-            <screen>example.com.  IN MX 10 mail.example.com.
-    IN MX 20 mail2.example.com.</screen>
-            <para>
-              In this example, the first <command>mail.example.com</command> email server is preferred to the <command>mail2.example.com</command> email server when receiving email destined for the <command>example.com</command> domain.
+              In <xref linkend="example-bind-zone-rr-mx" />, the first <systemitem class="domainname">mail.example.com</systemitem> email server is preferred to the <systemitem class="domainname">mail2.example.com</systemitem> email server when receiving email destined for the <systemitem class="domainname">example.com</systemitem> domain.
+
             </para>
+            <example id="example-bind-zone-rr-mx">
+              <title>Using the <command>MX</command> resource record</title>
+              <screen>example.com. IN MX 10 mail.example.com.
+             IN MX 20 mail2.example.com.</screen>
+            </example>
           </listitem>
         </varlistentry>
         <varlistentry>


More information about the docs-commits mailing list