HP-UX Reference (11i v3 07/02) - 4 File Formats (vol 8)

n
named.conf(4) named.conf(4)
(BIND 9.3)
2874.
AAAA Defines an IPv6 address. Described in RFC 1886.
CERT Holds a digital certificate. Described in RFC 2538.
CNAME The canonical name of an alias. Described in RFC 1035.
DNAME Delegates reverse addresses. Replaces the domain name specified with another
name to be looked up. Described in RFC 2672.
GPOS Specifies the global position. Described in RFC 1712.
HINFO Identifies the CPU and OS used by a host. Described in RFC 1035.
KEY Stores a public key associated with a DNS name. Described in RFC 2535.
KX Identifies a key exchanger for this DNS name. Described in RFC 2230.
MX Identifies a mail exchange for the domain. A 16-bit preference value (lower is
better) followed by the host name of the mail exchange. See the MX Resource
Records section. Described in RFC 974 and RFC 1035.
NAPTR Name authority pointer. Described in RFC 2915.
NSAP A network service access point. Described in RFC 1706.
NS An authoritative name server for the domain. Described in RFC 1035.
NXT Used in DNSSEC to securely indicate that RRs with an owner name in a certain
name interval do not exist in a zone and indicate what RR types are present for
an existing name. Described in RFC 2535.
PTR Domain name pointer. A pointer to another part of the domain name space.
Often user to associate an IP address with a domain name. Described in RFC
1035.
PX Provides mappings between RFC 822 and X.400 addresses. Described in RFC
2163.
SIG (signature)
Contains data authenticated in the secure DNS. Described in RFC 2535.
SOA Identifies the start of a zone of authority in a zone file. See the SOA Resource
Records section. Described in RFC 1035.
SRV Information about the well-known network services, such as SMTP, that a
domain supports. Supersedes WKS. Described in RFC 2282.
TXT Text records. Described in RFC 1035.
WKS Information about well known network services. Historical. Superseded by
SRV. Described in RFC 1035.
rrdata The type-dependent and sometimes class-dependent data that describes the resource. This
data is defined in the RFCs that are specified with each type keyword.
MX Resource Records
MX records control the delivery of e-mail. Described in RFC 974 and RFC 1035.
Syntax
... MX priority host_domain_name
... The owner_name, ttl, and class have been omitted for clarity.
priority The priority controls the order in which e-mail delivery is attempted, with the lowest
number first. If two priorities are the same, a server is chosen randomly. If no servers at a
given priority are responding, the mail transport agent will fall back to the next largest
priority. Priority numbers do not have any absolute meaning: they are relevant only
respective to other MX records for that domain name.
host_domain_name
The domain name of the machine to which the mail should be delivered.
HP-UX 11i Version 3: February 2007 − 33 − Hewlett-Packard Company 265