Page 111 - DCAP602_NETWORK_OPERATING_SYSTEMS_I

Unit 6: Domain Name System

There can be uncertainty with the locations: Regular BIND installs its files in the normal notes
locations, and the chroot BIND add-on RPM installs its own versions in their chroot locations.
Unfortunately, the chroot versions of some of the files are empty. Before starting Fedora BIND,
copy the configuration files to their chroot locations:
[root@bigboy tmp]# cp -f /etc/named.conf /var/named/chroot/etc/
[root@bigboy tmp]# cp -f /etc/rndc.* /var/named/chroot/etc/
Before you go to the next step of configuring a regular name server, it is important to understand
exactly where the files are located.

Task Describe why the first domain scheduled after the search directive must be the
home domain of your network?

table 6.2: Differences in fedora and redhat Dns file Locations
file purpose BinD chroot Location regular BinD Location
named.conf Tells the names of the zone /var/named/chroot/etc /etc
files to be used for each of
your website domains.
rndc.key Files used in named /var/named/chroot/etc /etc
rndc.conf authentication
zone files Links all the IP addresses /var/named/chroot/ /var/named
in your domain to their var/named
corresponding server

Fedora Core installs BIND chroot by default. RedHat 9 and earlier don’t.
Debian / ubuntu
With Debian / Ubuntu, all the configuration files, the primary named.conf file and all the DNS
zone files reside in the /etc/bind directory.
Unlike in Redhat / Fedora, references to other files within these configuration files must include
the full path. The named daemon won’t automatically assume they are located in the /etc/bind
directory.
Configuring your Nameserver
Assume your ISP assigned you the subnet 97.158.253.24 with a subnet mask of 255.255.255.248
(/29).
Configuring resolv.conf
You’ll have to build your DNS server refer to itself for all DNS queries by configuring the /etc/
resolv.conf file to reference localhost only.
nameserver 127.0.0.1
Creating a named.conf Base Configuration
The /etc/named.conf file contains the main DNS configuration and tells BIND where to find the
configuration, or zone files for each domain you own. This file generally has two zone areas:
1. Forward zone file definitions list files to map domains to IP addresses.
2. Reverse zone file definitions list files to map IP addresses to domains.

LoveLy professionaL university 105