How to set up BIND v4.8.3 named database files: $Revision: 1.16 $
-----------------------------------------------
Please read the chapter on BIND in the "IRIX Advanced Site and
Server Administration Guide" and the named(1M) manual page first.
Files:
------
The following files in /var/named/Examples are templates that must
be customized for your environment. These example files may be updated in the
next IRIX release.
named.boot.master - boot file for a master name server
named.boot.slave - boot file for a secondary name server
named.hosts - The host-address data base for your domain
named.rev - address-hosts (PTR) records for your domain, so that
the .IN-ADDR.ARPA domain works
localhost.rev - PTR data for localhost
root.cache - data for the name server's initial cache for
machines connected to the Internet
*** Note: see the comments in the file about
obtaining the current list of root servers.
Named uses the following types of database files:
boot file
hostname-to-address and address-to-hostname for each domain
initial cache of servers
By default, named expects the database file in /etc.
If you are a master server for a domain,
cp /var/named/Examples/named.boot.master /etc/named.boot
If you are a secondary (slave) server,
cp /var/named/Examples/named.boot.slave /etc/named.boot
Also copy named.hosts, named.rev, localhost.rev and root.cache to
/var/named. You MUST edit these files to reflect your domain setup.
It's useful to name the host-address and address-host files with the domain
name, e.g., berkeley.zone, berkeley.rev. This especially useful if you have
named serving several domains.
How to add new hosts to the named data base:
--------------------------------------------
1) Edit 'named.hosts' file:
For each machine you need to enter the following information:
machine name, all its network addresses, and common aliases (CNAMES).
The WKS records list well-known services and HINFO records list the
machine type and operating system; these records are optional.
This is the entry for calder.Berkeley.EDU.
CALDER IN A 128.32.130.1
IN A 128.32.129.3
IN WKS 128.32.0.12 TCP DAYTIME FTP TELNET SMTP DOMAIN FINGER
IN WKS 128.32.0.12 UDP DAYTIME TIME DOMAIN
IN HINFO VAX-11/750 UNIX
UCBCALDER IN CNAME CALDER
For the machine you are adding:
1) replace 'CALDER' with the new machine name
2) replace '128.32.130.1' with the new machine's address
if there is more then one address for the machine
then add lines like the one with '128.32.129.3'
3) replace 'VAX-11/750' with the machine type, as listed in
RFC-1340 'Assigned Numbers'. 'Official' names for Silicon Graphics
machines are:
SGI-IRIS-INDIGO SGI-IRIS-INDIGO-R4000
SGI-IRIS-INDIGO-XS SGI-IRIS-INDIGO-XS24
SGI-IRIS-INDIGO-ELAN
SGI-IRIS-INDIGO-R4000-XS SGI-IRIS-INDIGO-R4000-XS24
SGI-IRIS-INDIGO-R4000-XZ SGI-IRIS-INDIGO-R4000-ELAN
SGI-INDIGO2 SGI-INDIGO2-EX
SGI-INDIGO2-XL SGI-INDIGO2-XZ
SGI-INDY
SGI-IRIS-CRIMSON SGI-IRIS-CRIMSON-S
SGI-IRIS-CRIMSON-XS SGI-IRIS-CRIMSON-XS24
SGI-IRIS-CRIMSON-ELAN SGI-IRIS-CRIMSON-EX
SGI-IRIS-CRIMSON-GTX SGI-IRIS-CRIMSON-RE
SGI-IRIS-CRIMSON-VGX SGI-IRIS-CRIMSON-VGXT
SGI-ONYX-VTX SGI-ONYX-RE2
SGI-CHALLENGE-M
SGI-CHALLENGE-L-{x} where {x} = number of processors
SGI-CHALLENGE-XL-{x}
SGI-IRIS-4D/20 SGI-IRIS-4D/20G SGI-IRIS-4D/20TG
SGI-IRIS-4D/25 SGI-IRIS-4D/25G SGI-IRIS-4D/25TG SGI-IRIS-4D/25S
SGI-IRIS-4D/30 SGI-IRIS-4D/30G SGI-IRIS-4D/30TG
SGI-IRIS-4D/30-ELAN
SGI-IRIS-4D/35 SGI-IRIS-4D/35G SGI-IRIS-4D/35TG SGI-IRIS-4D/35S
SGI-IRIS-4D/35-ELAN
SGI-IRIS-4D/50 SGI-IRIS-4D/50G SGI-IRIS-4D/50GT
SGI-IRIS-4D/60 SGI-IRIS-4D/60G SGI-IRIS-4D/60T SGI-IRIS-4D/60GT
SGI-IRIS-4D/70 SGI-IRIS-4D/70G SGI-IRIS-4D/70GT
SGI-IRIS-4D/80GT SGI-IRIS-4D/80S
SGI-IRIS-4D/85GT
SGI-IRIS-4D/120GTX SGI-IRIS-4D/120S
SGI-IRIS-4D/2{x}0GTX SGI-IRIS-4D/2{x}0VGX SGI-IRIS-4D/2{x}0S
where {x} = 1, 2, 4 or 8
SGI-IRIS-4D/3{x}0S SGI-IRIS-4D/3{x}0GTX
SGI-IRIS-4D/3{x}0VGX SGI-IRIS-4D/3{x}0VGXT SGI-IRIS-4D/310RE
where {x} = 1, 2, 4 or 8
SGI-IRIS-4D/4{x}0S SGI-IRIS-4D/4{x}0GTX
SGI-IRIS-4D/4{x}0VGX SGI-IRIS-4D/4{x}0VGXT SGI-IRIS-4D/4{x}0RE
where {x} = 2, 4 or 8
SGI-IRIS-4D/320IG2 SGI-IRIS-4D/340IG2
SGI-IRIS-4D/420IG2 SGI-IRIS-4D/440IG2
SGI-IRIS-CS12 SGI-IRIS-4SERVER-8
SGI-IRIS-2400 SGI-IRIS-2500
SGI-IRIS-3010 SGI-IRIS-3020 SGI-IRIS-3030
SGI-IRIS-3110 SGI-IRIS-3115 SGI-IRIS-3120 SGI-IRIS-3130
4) For Silicon Graphics machines, replace UNIX with IRIX. Otherwise if
it doesn't run 'UNIX' then replace UNIX with its operating system.
2) Edit 'named.rev' file:
For each address of a machine you need to enter the reverse
address notation for the machine and the machine's name.
Addresses in dotted-decimal format are composed of 4 numbers.
For Class A networks, you take the last 3 numbers and reverse them.
For Class B networks, you take the last 2 numbers and reverse them.
For Class C networks, you take the last number.
For example, Calder has two address '128.32.0.12' and '128.32.129.3'.
(128.32 is Berkeley's Class B network number.) Calder's PTR lines are
as follows:
12.0 IN PTR CALDER.BERKELEY.EDU.
3.129 IN PTR CALDER.BERKELEY.EDU.
^
| Note the trailing dots --
they MUST be there!
The network numbers are used in the IN-ADDR.ARPA domain name, as
specified in the named.boot file. The numbers are also reversed.
For example, from named.boot.master,
primary 32.128.IN-ADDR.ARPA berkeley.rev
If you have multiple networks, each one must have its own .rev file.
For example, if your network numbers are 192.0.2 and 145.254 and
the gateway machine for these networks has addresses 192.0.2.1 and
145.254.0.1, then its 2 PTR records belong in separate .rev files.
3) Update the SOA (start of authority) records in named.hosts and named.rev
to reflect your domain setup. Change the 4th field in the SOA record
to be the hostname of the master server for your domain. Change the 5th
field to be the e-mail address of the person in charge of the named files.
; 1 2 3 4: master server 5: person in charge
@ IN SOA ucbvax.berkeley.edu kjd.ucbvax.berkeley.edu (
91032101 ; Serial
10800 ; Refresh 3 hours
3600 ; Retry 1 hour
3600000 ; Expire 1000 hours
86400 ) ; Minimum 24 hours
4) Every time you update named.hosts or named.rev, update the serial
number in the file's SOA record. A useful format is to encode the current
date in the number. For example, 93032101 encodes 21 March 1993 edit #1.
Increment the edit number if you modify the file more than once in a day.
5) If you make a change to a database file, run /usr/sbin/named.reload to
notify the server of the change.
Note: if you use NIS and BIND, look at the /var/named/mkdns/mkdns script
and /var/named/mkdns/local.make.script for a way to generate BIND files from
the NIS data.
