Technical Library

Domain Name System

Introduction

Integration

Starting a secondary name server involves the creation of two files.

The first file is the named.boot file. A secondary name server's named.boot file follows this pattern:

directory			        /directory name
secondary	zone		        primary name server IP	named.hosts
secondary	in-addr.arpa		primary name server IP	named.rev
primary		localhost in-addr.arpa 	named.local
cache		.			named.ca

Where the directory line specifies the name of the directory in which the necessary files are stored.

The next line is tells the name server that it is secondary for the zone and that it should look to the primary name server for its information. That is why the IP address of the primary name server is included. The data that is down-loaded from that name server will be stored in the named.hosts file, or whatever you named it.

The third line tells the name server that it is also secondary for the mapping of IP addresses to host names and that the data for that zone can be down-loaded from the primary name server.