Installing and Administering Internet Services

Chapter 3 77
Configuring and Administering the BIND Name Service
Configuring a Primary Master Name Server
99999999 A 192.52.195.10
. 99999999 NS NS.NIC.DDN.MIL.
NS.NIC.DDN.MIL. 99999999 A 192.112.36.4
. 99999999 NS AOS.ARL.ARMY.MIL.
AOS.ARL.ARMY.MIL. 99999999 A 128.63.4.82
99999999 A 192.5.25.82
. 99999999 NS NIC.NORDU.NET.
NIC.NORDU.NET. 99999999 A 192.36.148.17
; Lines beginning with a semicolon (;) are comments.
name In NS records, the name of the domain served by the
name server listed in the data column. A period (.) in
the name column represents the root domain (the root
of the DNS name space hierarchy). In A records, the
name column contains the name of the name server
whose address appears in the data column.
ttl The optional time-to-live (ttl) indicates how long, in
seconds, a server may cache the data it receives in
response to a query.
class The optional class field specifies the protocol group.
IN, for internet addresses, is the most common class. If
left blank, the class defaults to the last class specified.
So, all the entries in this example db.cache file are of
class IN.
type Type NS records list name servers. The first field in an
NS record is the domain for which the name server has
authority. The last field in an NS record is the fully
qualified name of the name server.
Type A records list addresses. The first field in an A
record is the name of the name server. The last field in
an A record is the internet address of the name server.
data The data field for an NS record gives the fully qualified
name of a name server. The data field for an A record
gives an internet address.
The db.127.0.0 File
Each name server must have an /etc/named.data/db.127.0.0 file.
Hosts running Berkeley networking use 127.0.0.1 as the address of the
loopback interface. Since the network number 127.0.0 is not assigned to
any one site but is used by all hosts running Berkeley networking, each
name server must be authoritative for network 127.0.0. The file