BIND Configuration

This page describes how to set up the BIND configuration file on the master to add new nodes to the nameserver.

For further help configuring BIND, refer to the DNS HOWTO.

All configuration files refered to here are from the master-nameserver SRPM which is in the medusa CVS archive. If you with to update the BIND configuration, please do this by obtaining and installing the master-nameserer SRPM, editing the files contained therein.

Once you have installed the SRPM, the configuration files will be in /usr/src/redhat/SOURCES

After you have modified the configuration files, rebuild the SRPM and RPM with rpm -ba /usr/src/redhat/SPECS/master-namesere.spec. This will place the new SRPM in /usr/src/redhat/SRPMS. Commit this back to the srpms module in the CVS archive. The RPMS will be placed in rpm -ba /usr/src/redhat/RPMS/noarch/. You can then use this to install or updrade on the master as neccessary.

The following configuration files in the master-nameserver SRPM should not be altered:

  1. resolv.conf.master
    This tells the master itself which nameservers to look at. It refers first to the nameserver running on localhost and then to the UWM nameservers if this fails. You should not modify this file.
  2. named.local
    This is an essential configuration file which should bot be modified. See the BIND howto for more information.
  3. named.conf.master
    This configures BIND and tells it where to look for other configuration files. It should not be altered.

The three files that may be altered to add more machines are:

  1. named.medusa
    This file contains the configuration for the medusa.phys.uwm.edu domain. It is is the most complicated of the three files and is described in detail below. There is a single file for the entire domain to resolve hostnames into IP addresses.
  2. named.129.89.200
    This file provides reverse DNS lookup (IP address to hostname) for the lower medusa subnet (129.89.200.0). It is simple and is described below.
  3. named.129.89.201
    This file provides reverse DNS lookup (IP address to hostname) for the upper medusa subnet (129.89.201.0). It is simple and described below.

Be aware of the following caveat:

Many hostnames in the configuration files end with a dot. This is significant and should not be left out. For example
  medusa-slave001.medusa.phys.uwm.edu.
does not mean the same thing as
  medusa-slave001.medusa.phys.uwm.edu
Refer to the DNS HOWTO for more information.

named.medusa

The first part of the file is the configuration for the medusa domain and should not be changed.

@INSOAmedusa.phys.uwm.edu. root.medusa.phys.uwm.edu. (
   200106241; serial, todays date + todays serial #
   8H; refresh, seconds
   2H; retry, seconds
   1W; expire, seconds
   1D ); minimum, seconds
 
 NSmedusa.phys.uwm.edu.
 NShydra.phys.uwm.edu.
 NSuwm.edu.
 MX10 medusa-master001.medusa.phys.uwm.edu.
 TXT"UWM LSC Group Medusa Beowulf"
 
localhostA127.0.0.1
 
medusa.phys.uwm.edu.A129.89.57.103
hydra.phys.uwm.edu.A129.89.57.104
 
nsA129.89.200.231
ns1A129.89.200.232
 
wwwAwww.lsc-group.phys.uwm.edu.

The second part of the file is can be edited. It should contain an entry for each machine on the medusa subnet. This includes all the slaves, the masters, the switch, uwmlsc, dataserver, lj2200, etc.

The following short example shows the entries for two slaves, the printer and two masters.

medusa-slave001A129.89.200.11
 MX10 medusa-master001.medusa.phys.uwm.edu.
 HINFO"Intel-i686" "Linux 2.4.5"
slave001CNAMEmedusa-slave001
s001CNAMEmedusa-slave001
 
medusa-slave002A129.89.200.12
 MX10 medusa-master001.medusa.phys.uwm.edu.
 HINFO"Intel-i686" "Linux 2.4.5"
slave002CNAMEmedusa-slave002
s002CNAMEmedusa-slave002
 
medusa-master001A129.89.200.231
 MX10 medusa-master001.medusa.phys.uwm.edu.
 HINFO"Intel-i686" "Linux 2.4.5"
master001CNAMEmedusa-master001
m001CNAMEmedusa-master001
 
medusa-master002A129.89.200.232
 MX10 medusa-master001.medusa.phys.uwm.edu.
 HINFO"Intel-i686" "Linux 2.4.5"
master002CNAMEmedusa-master002
m002CNAMEmedusa-master002
 
lj2200A129.89.200.240
 MX10 medusa-master001.medusa.phys.uwm.edu.
 HINFO"Printer" "HP LaserJet 2200"

To add aonther node, simply create another entry in the file of the form above. For instace to add an entry for slave 241 add the lines:

medusa-slave241A129.89.201.11
 MX10 medusa-master001.medusa.phys.uwm.edu.
 HINFO"Intel-i686" "Linux 2.4.5"
slave241CNAMEmedusa-slave241
s241CNAMEmedusa-slave241

Although order within the second section of the file does not matter, you should keep the entries in ascending order of IP address.

named.129.89.200

The first part of the file is the configuration for the lower subnet reverse IP lookup and should not be changed.

@INSOAmedusa.phys.uwm.edu. hostmaster.medusa.phys.uwm.edu. (
   200106241; serial, todays date + todays serial #
   8H; refresh, seconds
   2H; retry, seconds
   1W; expire, seconds
   1D ); minimum, seconds
 
 NSmedusa.phys.uwm.edu.
 NShydra.phys.uwm.edu.
 NSuwm.edu.

The second part of this file can be edited and contains the entries for reverse DNS lookup on the lower subnet. The following example fragment contains entries for two slaves.

11PTRmedusa-slave001.medusa.phys.uwm.edu.
12PTRmedusa-slave002.medusa.phys.uwm.edu.

Note the the reverse lookup should give the FQDN of the machine, i.e. medusa-slave001.medusa.phys.uwm.edu, not slave001 or s001. Note also that each FQDN ends in a period.

To add another machine, say to provide reverse DNS lookup for slave 50 add the following line to this file:

60PTRmedusa-slave050.medusa.phys.uwm.edu.

Although order within the second section of the file does not matter, you should keep the entries in ascending order of IP address.

named.129.89.201

The first part of the file is the configuration for the upper subnet reverse IP lookup and should not be changed.

@INSOAmedusa.phys.uwm.edu. hostmaster.medusa.phys.uwm.edu. (
   200106241; serial, todays date + todays serial #
   8H; refresh, seconds
   2H; retry, seconds
   1W; expire, seconds
   1D ); minimum, seconds
 
 NSmedusa.phys.uwm.edu.
 NShydra.phys.uwm.edu.
 NSuwm.edu.

The second part of this file can be edited and contains the entries for reverse DNS lookup on the upper subnet. The following example fragment contains entries for the printer and two masters.

231PTRmedusa-master001.medusa.phys.uwm.edu.
232PTRmedusa-master002.medusa.phys.uwm.edu.
240PTRlj2200.medusa.phys.uwm.edu.

Note the the reverse lookup should give the FQDN of the machine, i.e. medusa-master001.medusa.phys.uwm.edu, not master001 or m001. Note also that each FQDN ends in a period.

To add another machine, say to provide reverse DNS lookup for slave 241 add the following line to this file:

11PTRmedusa-slave241.medusa.phys.uwm.edu.

Although order within the second section of the file does not matter, you should keep the entries in ascending order of IP address.

$Id: bind_configuration.html,v 1.1 2002/02/07 00:10:24 duncan Exp $