named.conf.4 (2010 09)

n
named.conf(4) named.conf(4)
(BIND 9.3)
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.
An
MX record must have an associated A record; a CNAME is not sufficient. For a given domain, if there is
both a CNAME record and an MX record, the MX record is in error and will be ignored. Instead, the mail
will be delivered to the server specified in the MX record pointed to by the
CNAME.
Example
example.com. IN MX 10 mail.example.com.
IN MX 10 mail2.example.com.
IN MX 20 mail.backup.org.
mail.example.com. IN A 10.0.0.1
mail2.example.com. IN A 10.0.0.2
Mail delivery will be attempted to
mail.example.com and mail2.example.com
(in any order),
and if neither of those succeed, delivery to
mail.backup.org will be attempted.
SOA Resource Records
Each zone file begins with an
SOA record for the zone. All records in a zone file must be of the same
class. Described in RFC 1035.
Syntax
...
SOA mname rname serial refresh retry expire minimum
... The owner_name , ttl , and class have been omitted for clarity.
mname The domain name of the name server that is the source of data for this zone.
rname A domain name that specifies the mailbox of the person responsible for this zone. The
first period represents the @ in the e-mail address. If the mailbox user name contains a
period, you can escape it with a backslash (\). See the example.
serial An arbitrary unsigned 32-bit integer serial number for the zone. The range is 0 to
4294967295 (2ˆ32-1).
refresh A 32-bit integer time interval in seconds to refresh the zone. See the Time Specification
section for more detail.
34 Hewlett-Packard Company − 34 − HP-UX 11i Version 3: September 2010