231 lines
14 KiB
HTML
231 lines
14 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="reference" />
|
||
|
|
<meta name="DC.Title" content="Domain Name System resource records" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakkconceptparent.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakkscenario1.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakkconceptbasic.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakkconceptdynamic.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakkmailmx.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="rzakkconceptresourcerec" />
|
||
|
|
<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>Domain Name System resource records</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakkconceptresourcerec"><a name="rzakkconceptresourcerec"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Domain Name System resource records</h1>
|
||
|
|
<div><p>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<sup>®</sup> V5R1.</p>
|
||
|
|
<div class="section"><p>A DNS zone database is made up of a collection of resource records.
|
||
|
|
Each resource record specifies information about a particular object. For
|
||
|
|
example, address mapping (A) records map a host name to an IP address, and
|
||
|
|
reverse-lookup pointer (PTR) records map an IP address to a host name. The
|
||
|
|
server uses these records to answer queries for hosts in its zone. For more
|
||
|
|
information, use the table to view DNS resource records.</p>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><!-- Link to dynamic table -->
|
||
|
|
<SCRIPT language="Javascript" type="text/javascript" src="../rzahg/iccommon.js"></SCRIPT>
|
||
|
|
<SCRIPT language="Javascript" type="text/javascript">
|
||
|
|
//<![CDATA[
|
||
|
|
//Do not split up the following string. Keep it on one line.
|
||
|
|
var textA = "<p>To easily compare and sort the data in this table, use the <a href='rzakkconceptresourcerec.xml'>interactive table<\/a>.<\/p>";
|
||
|
|
if (isIE5) {
|
||
|
|
document.writeln(textA);
|
||
|
|
}
|
||
|
|
//]]>
|
||
|
|
</SCRIPT>
|
||
|
|
<!-- End of link to dynamic table --><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><caption>Table 1. Resource record lookup table</caption><thead align="left"><tr><th valign="top" id="d0e42">Resource record</th>
|
||
|
|
<th valign="top" id="d0e44">Abbreviation</th>
|
||
|
|
<th valign="top" id="d0e46">Description</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" headers="d0e42 ">Address Mapping records</td>
|
||
|
|
<td valign="top" headers="d0e44 ">A</td>
|
||
|
|
<td valign="top" headers="d0e46 ">The A record specifies the IP address of this host. A records are used
|
||
|
|
to resolve a query for the IP address of a specific domain name. This record
|
||
|
|
type is defined in Request for Comments (RFC) 1035.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e42 ">Andrew File System Database records</td>
|
||
|
|
<td valign="top" headers="d0e44 ">AFSDB</td>
|
||
|
|
<td valign="top" headers="d0e46 ">The AFSDB record specifies the AFS<sup>®</sup> or DCE address of the object. AFSDB
|
||
|
|
records are used like A records to map a domain name to its AFSDB address;
|
||
|
|
or to map from the domain name of a cell to authenticated name servers for
|
||
|
|
that cell. This record type is defined in RFC 1183.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e42 ">Canonical Name records</td>
|
||
|
|
<td valign="top" headers="d0e44 ">CNAME</td>
|
||
|
|
<td valign="top" headers="d0e46 ">The CNAME record specifies the actual domain name of this object. When
|
||
|
|
DNS queries an aliased name and finds a CNAME record pointing to the canonical
|
||
|
|
name, it then queries that canonical domain name. This record type is defined
|
||
|
|
in RFC 1035.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e42 ">Host Information records</td>
|
||
|
|
<td valign="top" headers="d0e44 ">HINFO</td>
|
||
|
|
<td valign="top" headers="d0e46 ">The HINFO record specifies general information about a host machine.
|
||
|
|
Standard CPU and operating system names are defined in the Assigned Numbers
|
||
|
|
RFC 1700. However, use of the standard numbers is not required. This record
|
||
|
|
type is defined in RFC 1035.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e42 ">Integrated Services Digital Network records</td>
|
||
|
|
<td valign="top" headers="d0e44 ">ISDN</td>
|
||
|
|
<td valign="top" headers="d0e46 ">The ISDN record specifies the address of this object. This record maps
|
||
|
|
a host name to the ISDN address. They are used only in ISDN networks. This
|
||
|
|
record type is defined in RFC 1183.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e42 ">IP Version 6 Address records</td>
|
||
|
|
<td valign="top" headers="d0e44 ">AAAA</td>
|
||
|
|
<td valign="top" headers="d0e46 ">The AAAA record specifies the 128-bit address of a host. AAAA records
|
||
|
|
are used like A records to map a host name to its IP address. Use AAAA records
|
||
|
|
to support IP version 6 addresses, which do not fit the standard A record
|
||
|
|
format. This record type is defined in RFC 1886.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e42 ">Location records</td>
|
||
|
|
<td valign="top" headers="d0e44 ">LOC</td>
|
||
|
|
<td valign="top" headers="d0e46 ">The LOC record specifies the physical location of network components.
|
||
|
|
These records can be used by applications to evaluate network efficiency or
|
||
|
|
map the physical network. This record type is defined in RFC 1876.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e42 ">Mail Exchanger records</td>
|
||
|
|
<td valign="top" headers="d0e44 ">MX</td>
|
||
|
|
<td valign="top" headers="d0e46 ">The MX records defines a mail exchanger host for mail sent to this
|
||
|
|
domain. These records are used by Simple Mail Transfer Protocol (SMTP) to
|
||
|
|
locate hosts that processes or forwards mail for this domain, along with preference
|
||
|
|
values for each mail exchanger host. Each mail exchanger host must have a
|
||
|
|
corresponding host address (A) records in a valid zone. This record type is
|
||
|
|
defined in RFC 1035.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e42 ">Mail Group records</td>
|
||
|
|
<td valign="top" headers="d0e44 ">MG</td>
|
||
|
|
<td valign="top" headers="d0e46 ">The MG records specifies the mail group domain name. This record type
|
||
|
|
is defined in RFC 1035.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e42 ">Mailbox records</td>
|
||
|
|
<td valign="top" headers="d0e44 ">MB</td>
|
||
|
|
<td valign="top" headers="d0e46 ">The MB records specifies the host domain name which contains the mailbox
|
||
|
|
for this object. Mail sent to the domain is directed to the host specified
|
||
|
|
in the MB record. This record type is defined in RFC 1035.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e42 ">Mailbox Information records</td>
|
||
|
|
<td valign="top" headers="d0e44 ">MINFO</td>
|
||
|
|
<td valign="top" headers="d0e46 ">The MINFO records specifies the mailbox that should receive messages
|
||
|
|
or errors for this object. The MINFO record is more commonly used for mailing
|
||
|
|
lists than for a single mailbox. This record type is defined in RFC 1035.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e42 ">Mailbox Rename records</td>
|
||
|
|
<td valign="top" headers="d0e44 ">MR</td>
|
||
|
|
<td valign="top" headers="d0e46 ">The MR records specifies a new domain name for a mailbox. Use the MR
|
||
|
|
record as a forwarding entry for a user who has moved to a different mailbox.
|
||
|
|
This record type is defined in RFC 1035.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e42 ">Name Server records</td>
|
||
|
|
<td valign="top" headers="d0e44 ">NS</td>
|
||
|
|
<td valign="top" headers="d0e46 ">The NS record specifies an authoritative name server for this host.
|
||
|
|
This record type is defined in RFC 1035.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e42 ">Network Service Access Protocol records</td>
|
||
|
|
<td valign="top" headers="d0e44 ">NSAP</td>
|
||
|
|
<td valign="top" headers="d0e46 ">The NSAP record specifies the address of a NSAP resource. NSAP records
|
||
|
|
are used to map domain names to NSAP addresses. This record type is defined
|
||
|
|
in RFC 1706.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e42 ">Public Key records</td>
|
||
|
|
<td valign="top" headers="d0e44 ">KEY</td>
|
||
|
|
<td valign="top" headers="d0e46 ">The KEY record specifies a public key that is associated with a DNS
|
||
|
|
name. The key can be for a zone, a user, or a host. This record type is defined
|
||
|
|
in RFC 2065.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e42 ">Responsible Person records</td>
|
||
|
|
<td valign="top" headers="d0e44 ">RP</td>
|
||
|
|
<td valign="top" headers="d0e46 ">The RP record specifies the internet mail address and description of
|
||
|
|
the person responsible for this zone or host. This record type is defined
|
||
|
|
in RFC 1183.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e42 ">Reverse-lookup Pointer records</td>
|
||
|
|
<td valign="top" headers="d0e44 ">PTR</td>
|
||
|
|
<td valign="top" headers="d0e46 ">The PTR record specifies the domain name of a host for which you want
|
||
|
|
a PTR record defined. PTR records allow a host name lookup, given an IP address.
|
||
|
|
This record type is defined in RFC 1035.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e42 ">Route Through records</td>
|
||
|
|
<td valign="top" headers="d0e44 ">RT</td>
|
||
|
|
<td valign="top" headers="d0e46 ">The RT record specifies a host domain name that can act as a forwarder
|
||
|
|
of IP packets for this host. This record type is defined in RFC 1183.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e42 ">Start of Authority records</td>
|
||
|
|
<td valign="top" headers="d0e44 ">SOA</td>
|
||
|
|
<td valign="top" headers="d0e46 ">The SOA record specifies that this server is authoritative for this
|
||
|
|
zone. An authoritative server is the best source for data within a zone. The
|
||
|
|
SOA record contains general information about the zone and reload rules for
|
||
|
|
secondary servers. There can be only one SOA record per zone. This record
|
||
|
|
type is defined in RFC 1035.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e42 ">Text records</td>
|
||
|
|
<td valign="top" headers="d0e44 ">TXT</td>
|
||
|
|
<td valign="top" headers="d0e46 ">The TXT record specifies multiple strings of text, up to 255 characters
|
||
|
|
long each, to be associated with a domain name. TXT records can be used along
|
||
|
|
with responsible person (RP) records to provide information about who is responsible
|
||
|
|
for a zone. This record type is defined in RFC 1035. <p>TXT records are used
|
||
|
|
by iSeries™ DHCP
|
||
|
|
for dynamic updates. The DHCP server writes an associated TXT record for each
|
||
|
|
PTR and A record update done by the DHCP server. DHCP records have a prefix
|
||
|
|
of AS400 DHCP.</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e42 ">Well-Known Services records</td>
|
||
|
|
<td valign="top" headers="d0e44 ">WKS</td>
|
||
|
|
<td valign="top" headers="d0e46 ">The WKS record specifies the well-known services supported by the object.
|
||
|
|
Most commonly, WKS records indicate whether tcp or udp or both protocols are
|
||
|
|
supported for this address. This record type is defined in RFC 1035.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e42 ">X.400 Address Mapping records</td>
|
||
|
|
<td valign="top" headers="d0e44 ">PX</td>
|
||
|
|
<td valign="top" headers="d0e46 ">The PX records is a pointer to X.400/RFC 822 mapping information. This
|
||
|
|
record type is defined in RFC 1664.</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" headers="d0e42 ">X25 Address Mapping records</td>
|
||
|
|
<td valign="top" headers="d0e44 ">X25</td>
|
||
|
|
<td valign="top" headers="d0e46 ">The X25 record specifies the address of an X25 resource. This record
|
||
|
|
maps a host name to the PSDN address. They are used only in X25 networks.
|
||
|
|
This record type is defined in RFC 1183.</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</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="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakkconceptdynamic.htm" title="OS/400 V5R1 DNS based on BIND 8 supports dynamic updates. These allow outside sources, such as Dynamic Host Configuration Protocol (DHCP), to send updates to the Domain Name System (DNS) server.">Dynamic updates</a></div>
|
||
|
|
<div><a href="rzakkmailmx.htm" title="Domain Name System (DNS) supports advanced mail routing through the use of Mail and Mail Exchanger (MX) records.">Mail and Mail Exchanger records</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rzakkscenario1.htm" title="This example depicts a simple subnet with a Domain Name System (DNS) server for internal use.">Example: Single Domain Name System server for an intranet</a></div>
|
||
|
|
<div><a href="rzakkconceptbasic.htm" title="This topic explains Domain Name System (DNS) zones and zone types.">Understanding zones</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|