ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzakk_5.4.0.1/rzakkmailmx.htm

84 lines
5.6 KiB
HTML

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="concept" />
<meta name="DC.Title" content="Mail and Mail Exchanger records" />
<meta name="abstract" content="Domain Name System (DNS) supports advanced mail routing through the use of Mail and Mail Exchanger (MX) records." />
<meta name="description" content="Domain Name System (DNS) supports advanced mail routing through the use of Mail and Mail Exchanger (MX) records." />
<meta name="DC.Relation" scheme="URI" content="rzakkconceptparent.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakkconceptresourcerec.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzakkmailmx" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>Mail and Mail Exchanger records</title>
</head>
<body id="rzakkmailmx"><a name="rzakkmailmx"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Mail and Mail Exchanger records</h1>
<div><p>Domain Name System (DNS) supports advanced mail routing through
the use of Mail and Mail Exchanger (MX) records.</p>
<p>Mail and MX records are used by mail routing programs, such as Simple Mail
Transfer Protocol (SMTP). The lookup table in DNS resource records contains
the types of mail records that iSeries™ DNS supports.</p>
<p>DNS includes information for sending electronic mail by using mail exchanger
information. If the network is using DNS, an SMTP application does not deliver
mail addressed to host TEST.IBM.COM by opening a TCP connection to TEST.IBM.COM.
SMTP first queries the DNS server to find out which host servers can be used
to deliver the message.</p>
<div class="section"><h4 class="sectiontitle">Deliver mail to a specific address</h4><p>DNS servers use
resource records that are known as <em>mail exchanger</em> (MX) records. MX
records map a domain or host name to a preference value and host name. MX
records are generally used to designate that one host is used to process mail
for another host. The records are also used to designate another host to deliver
mail to, if the first host cannot be reached. In other words, they allow mail
that is addressed to one host to be delivered to a different host.</p>
<p>Multiple
MX resource records might exist for the same domain or host name. When multiple
MX records exist for the same domain or host, the preference (or priority)
value of each record determines the order in which they are tried. The lowest
preference value corresponds to the most preferred record, which is tried
first. When the most preferred host cannot be reached, the sending mail application
tries to contact the next, less preferred MX host. The domain administrator,
or the creator of the MX record, sets the preference value.</p>
<p>A DNS server
can respond with an empty list of MX resource records when the name is in
the DNS server's authority but has no MX assigned to it. When this occurs,
the sending mail application might try to establish a connection with the
destination host directly.</p>
<div class="note"><span class="notetitle">Note:</span> Using a wild card (example: <samp class="codeph">*.mycompany.com</samp>)
in MX records for a domain is not suggested.</div>
</div>
<div class="section"><h4 class="sectiontitle">Example: MX record for a host</h4><p>In the following example,
the system, by preference, delivers mail for fsc5.test.ibm.com to the host
itself. If the host cannot be reached, the system might deliver the mail to
psfred.test.ibm.com or to mvs.test.ibm.com (if psfred.test.ibm.com also cannot
be reached). This is an example of what these MX records will look like:</p>
<pre> fsc5.test.ibm.com IN MX 0 fsc5.test.ibm.com
IN MX 2 psfred.test.ibm.com
IN MX 4 mvs.test.ibm.com</pre>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakkconceptparent.htm" title="This topic explains what Domain Name System (DNS) is and how it works. It also shows the different types of zones that can be defined on a DNS server.">Domain Name System concepts</a></div>
</div>
<div class="relref"><strong>Related reference</strong><br />
<div><a href="rzakkconceptresourcerec.htm" title="This topic explains how resource records are used by Domain Name System (DNS). Resource records are used to store data about domain names and IP addresses. This topic contains a searchable list of resource records supported for OS/400 V5R1.">Domain Name System resource records</a></div>
</div>
</div>
</body>
</html>