ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzakk_5.4.0.1/rzakkconceptresourcerec.xml

<?xml:stylesheet version="1.0" encoding="utf-8"?>
<?xml:stylesheet type="text/xsl" href="../rzahg/icdyntable.xsl"?>
<TABLE xmlns="x-schema:rzakkconceptresourcerec-schema.xml">
<TITLE>Domain Name System resource records</TITLE>
<TH col="TD1">
Resource record
</TH>
<TH col="TD2">
Abbreviation
</TH>
<TH col="TD3">
Description
</TH>
<TR><TD1 valign="top">Address Mapping records</TD1><TD2 valign="top">A</TD2><TD3 valign="top">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.</TD3></TR>
<TR><TD1 valign="top">Andrew File System Database records</TD1><TD2 valign="top">AFSDB</TD2><TD3 valign="top">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.</TD3></TR>
<TR><TD1 valign="top">Canonical Name records</TD1><TD2 valign="top">CNAME</TD2><TD3 valign="top">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.</TD3></TR>
<TR><TD1 valign="top">Host Information records</TD1><TD2 valign="top">HINFO</TD2><TD3 valign="top">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.</TD3></TR>
<TR><TD1 valign="top">Integrated Services Digital Network records</TD1><TD2 valign="top">ISDN</TD2><TD3 valign="top">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.</TD3></TR>
<TR><TD1 valign="top">IP Version 6 Address records</TD1><TD2 valign="top">AAAA</TD2><TD3 valign="top">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.</TD3></TR>
<TR><TD1 valign="top">Location records</TD1><TD2 valign="top">LOC</TD2><TD3 valign="top">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.</TD3></TR>
<TR><TD1 valign="top">Mail Exchanger records</TD1><TD2 valign="top">MX</TD2><TD3 valign="top">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.</TD3></TR>
<TR><TD1 valign="top">Mail Group records</TD1><TD2 valign="top">MG</TD2><TD3 valign="top">The MG records specifies the mail group domain name. This record type
is defined in RFC 1035.</TD3></TR>
<TR><TD1 valign="top">Mailbox records</TD1><TD2 valign="top">MB</TD2><TD3 valign="top">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.</TD3></TR>
<TR><TD1 valign="top">Mailbox Information records</TD1><TD2 valign="top">MINFO</TD2><TD3 valign="top">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.</TD3></TR>
<TR><TD1 valign="top">Mailbox Rename records</TD1><TD2 valign="top">MR</TD2><TD3 valign="top">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.</TD3></TR>
<TR><TD1 valign="top">Name Server records</TD1><TD2 valign="top">NS</TD2><TD3 valign="top">The NS record specifies an authoritative name server for this host.
This record type is defined in RFC 1035.</TD3></TR>
<TR><TD1 valign="top">Network Service Access Protocol records</TD1><TD2 valign="top">NSAP</TD2><TD3 valign="top">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.</TD3></TR>
<TR><TD1 valign="top">Public Key records</TD1><TD2 valign="top">KEY</TD2><TD3 valign="top">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.</TD3></TR>
<TR><TD1 valign="top">Responsible Person records</TD1><TD2 valign="top">RP</TD2><TD3 valign="top">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.</TD3></TR>
<TR><TD1 valign="top">Reverse-lookup Pointer records</TD1><TD2 valign="top">PTR</TD2><TD3 valign="top">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.</TD3></TR>
<TR><TD1 valign="top">Route Through records</TD1><TD2 valign="top">RT</TD2><TD3 valign="top">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.</TD3></TR>
<TR><TD1 valign="top">Start of Authority records</TD1><TD2 valign="top">SOA</TD2><TD3 valign="top">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.</TD3></TR>
<TR><TD1 valign="top">Text records</TD1><TD2 valign="top">TXT</TD2><TD3 valign="top">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>
</TD3></TR>
<TR><TD1 valign="top">Well-Known Services records</TD1><TD2 valign="top">WKS</TD2><TD3 valign="top">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.</TD3></TR>
<TR><TD1 valign="top">X.400 Address Mapping records</TD1><TD2 valign="top">PX</TD2><TD3 valign="top">The PX records is a pointer to X.400/RFC 822 mapping information. This
record type is defined in RFC 1664.</TD3></TR>
<TR><TD1 valign="top">X25 Address Mapping records</TD1><TD2 valign="top">X25</TD2><TD3 valign="top">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.</TD3></TR>
</TABLE>