Red Hat ENTERPRISE LINUX 3 Reference Manual page 208

Hide thumbs Also See for ENTERPRISE LINUX 3:
Table of Contents

Advertisement

190
Consider the following
IN
server1
IN
Requests for
example.com
are pointed to 10.0.1.5.
— Canonical name record, maps one name to another. This type of record is also known as
CNAME
an alias record.
The next example tells
host,
real-name .
common naming scheme, such as
alias-name
In the following example, an
points the commonly used
server1
IN
www
IN
— Mail eXchange record, which tells where mail sent to a particular namespace controlled by
MX
this zone should go.
IN
MX
In this example, the
namespace, giving preference to some email systems over others. The
lowest
preference-value
can possess the same value to distribute email traffic evenly among them.
The
email-server-name may be a hostname or FQDN.
IN
MX
IN
MX
In this example, the first
mail2.example.com
— NameServer record, which announces the authoritative nameservers for a particular zone.
NS
This is an example of an
IN
NS
The
nameserver-name should be an FQDN.
Next, two nameservers are listed as authoritative for the domain. It is not important whether these
nameservers are slaves or if one is a master; they are both still considered authoritative.
IN
NS
IN
NS
— PoinTeR record, designed to point to another part of the namespace.
PTR
records are primarily used for reverse name resolution, as they point IP addresses back to a
PTR
particular name. See Section 12.3.4 Reverse Name Resolution Zone Files for more examples of
records in use.
PTR
— Start Of Authority resource record, proclaims important authoritative information about a
SOA
namespace to the nameserver.
Located after the directives, an
The following example shows the basic structure of an
@
IN
SOA
Chapter 12. Berkeley Internet Name Domain (BIND)
record examples for the
A
A
10.0.1.3
A
10.0.1.5
are pointed to 10.0.1.3, while requests for
that any requests sent to the
named
records are most commonly used to point to services that use a
CNAME
for Web servers.
www
IN
CNAME
record binds a hostname to an IP address, while a
A
hostname to it.
www
A
10.0.1.5
CNAME
server1
preference-value
preference-value allows numerical ranking of the email servers for a
is preferred over the others. However, multiple email servers
10
mail.example.com.
20
mail2.example.com.
mail.example.com
email server when receiving email destined for the
record:
NS
nameserver-name
dns1.example.com.
dns2.example.com.
resource record is the first resource record in a zone file.
SOA
primary-name-server
serial-number
time-to-refresh
time-to-retry
time-to-expire
minimum-TTL
example.com
alias-name
real-name
email-server-name
email server is preferred
resource record:
SOA
hostmaster-email
)
zone file:
server1.example.com
should point to the
CNAME
resource record with the
MX
example.com
(
record
to the
domain.

Advertisement

Table of Contents
loading

Table of Contents