HP-UX Reference (11i v1 00/12) - 1M System Administration Commands N-Z (vol 4)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1m/naaagt.1m
________________________________________________________________
___ ___
n
named(1M) named(1M)
The sortlist line can be used to indicate networks that are preferred over other, unlisted networks.
Address sorting only happens when the query is from a host on the same network as the server. The best
address is placed first in the response. The address preference is local network addresses, then addresses
on the sort list, then other addresses.
A server can access information from servers in other domains given a list of root name servers and their
addresses. The zone "." line specifies that data in db.cache is to be placed in the backup cache. Its
use is to prime the server with the locations of root domain servers. This information is used to find the
current root servers and their addresses. The current root server information is placed in the operating
cache. Data for the root nameservers in the backup cache are never discarded.
The zone "berkeley.edu" line states that the master file db.berkeley contains authoritative
data for the berkeley.edu zone. A server authoritative for a zone has the most accurate information
for the zone. All domain names are relative to the origin, in this case, berkeley.edu (see below for a
more detailed description).
The zone "32.128.in-addr.arpa" line states that the file db.128.32 contains authoritative
data for the domain 32.128.in-addr.arpa. This domain is used to translate addresses in network
128.32 to hostnames.
The zone "cc.berkeley.edu"
line specifies that all authoritative data in the
cc.berkeley.edu
zone is to be transferred from the name server at Internet address 128.32.137.8 and will be saved in the
backup file db.cc. Up to 10 addresses can be listed on this line. If a transfer fails, it will try the next
address in the list. The secondary copy is also authoritative for the specified domain. The first non-
Internet address on this line will be taken as a filename in which to backup the transferred zone. The
name server will load the zone from this backup file (if it exists) when it boots, providing a complete copy,
even if the master servers are unreachable. Whenever a new copy of the domain is received from one of
the master servers, this file is updated. If no file name is given, a temporary file will be used and will be
deleted after each successful zone transfer. This is not recommended because it causes a needless waste of
bandwidth.
Master File Format
The master file consists of control information and a list of resource records for objects in the zone of the
forms:
$INCLUDE filename opt_domain
$ORIGIN domain
domain opt_ttl opt_class type resource_record_data
where:
domain is . for root, @ for the current origin, or a standard domain name. If domain is a
standard domain name that does not end with ‘‘.’’, the current origin is appended to
the domain. Domain names ending with ‘‘.’’ are unmodified.
opt_domain This field is used to define an origin for the data in an included file. It is equivalent to
placing an $ORIGIN statement before the first line of the included file. The field is
optional. Neither the opt_domain field nor $ORIGIN statements in the included file
modify the current origin for this file.
opt_ttl An optional integer number for the time-to-live field. It defaults to zero, meaning the
minimum value specified in the SOA record for the zone.
opt_class The object address type; currently only one type is supported, IN, for objects con-
nected to the DARPA Internet.
type This field contains one of the following tokens; the data expected in the
resource_record_data field is in parentheses:
A a host address (dotted-quad IP address)
NS an authoritative name server (domain)
MX a mail exchanger (domain), preceded by a preference value (0..32767), with
lower numeric values representing higher logical preferences.
CNAME the canonical name for an alias (domain)
SOA marks the start of a zone of authority (domain of originating host, domain
address of maintainer, a serial number and the following parameters in
seconds: refresh, retry, expire and minimum TTL (see RFC 883)).
HP-UX Release 11i: December 2000 − 3 − Section 1M−−527
___
___