Configure-the-Linux-DNS-and-BIND-Server.rar_DNS Server_The Bind

Linux DNS and BIND Server

Setting up a caching server for client local machines will reduce the load on the site's

primary server. A caching only name server will find the answer to name queries and

remember the answer the next time we need it. This will shorten the waiting time the next

time significantly. For security reasons, it is very important that DNS doesn't exist between

hosts on the corporate network and external hosts; it is far safer to simply use IP addresses

to connect to external machines from the corporate network and vice-versa.

In our configuration and installation we'll run BIND/DNS as non root-user and in a

The simple caching name server configuration will be used for your servers that don't

act as a master or slave name server, and the slave and master configurations will be used

for your servers that act as a master name server and slave name server. Usually one of

your servers acts as master, another one acts as slave and the rest act as simple caching

client name server.

This is a graphical representation of the DNS configuration we use in this book. We try

to show you different settings

•

Caching Only DNS

•

Master DNS

•

Commands are Unix-compatible.

•

The source path is /var/tmp. other paths are possible.

•

Installations were tested on Red Hat Linux 6.1 and 6.2.

•

All steps in the installation will happen in super-user account root.

•

ISC BIND version number is 8.2.2-patchlevel5

These are the Package(s) required:

ISC BIND Homepage:

bind-contrib.tar.gz, bind-doc.tar.gz, bind-src.tar.gz

Before you decompress Tarballs and install, it is a good idea to make a list of files on

the system before you install BIND, and one afterwards, and then compare them using diff

to find out what file it placed where. Simply run find /* > DNS1 before and find /* > DNS2

after you install the software, and use diff DNS1 DNS2 > DNS-Installed to get a list of what

changed.

Compile and Decompress the tarball (tar.gz).

We create a directory named bind to handle the tar archives and copy them to this

new directory.

Move into the new bind directory cd /var/tmp/bind and decompress the tar files:

: All the configuration files required for each software described in this

book has been provided by us as a gzipped file, floppy.tgz for your convenience.

This can be downloaded from this web address:

http://www.openna.com/books/floppy.tgz You can unpack this to any location on

your local machine, say for example

/tmp, assuming you have done this your directory

structure will be

/tmp/floppy. Within this floppy directory each configuration file has its

You can either cut and paste this directly if you are faithfully following our instructions

from the begining or manually edit these to modify to your needs. This facility is there

though as a convenience but please don't forget ultimately it will be your responsibility to

check, verify, etc. before you use them whether modified or as it is.

To run a master name server, the following files are required and must be created or

copied to the appropriate directories on your server.

on the floppy.tgz archive. Copy the following files from the decompressed floppy.tgz archive

to the appropriate places, or copy them directly from this book to the concerned file.

The necessary files to setup a simple caching name server are:

To configure the /etc/named.conf file for a simple caching name server, use this for all

servers that don’t act as a master or slave name server. Setting up a simple caching server

Use the following commands on another UNIX computer in your organization to

query a new db.cache file for your DNS Server or pick one from your Red Hat Linux CD-

ROM source distribution: