Installing and Administering Internet Services

106 Chapter3
Configuring and Administering the BIND Name Service
Configuring a Primary Master Name Server
[ allow-transfer { address_match_list }; ]
[ max-transfer-time-in number; ]
[ notify yes_or_no; ]
[ also-notify { ip_addr; [ ip_addr; ... ] };
};
zone . [ ( in | hs | hesiod | chaos ) ] {
type hint;
file path_name;
[ check-names ( warn | fail | ignore ); ]
} ;
Migrating /etc/named.boot to /etc/named.conf
To convert the BIND configuration file, /etc/named.boot to
/etc/named.conf follow the below steps.
1. Make sure that perl is installed on the system.
2. The "hosts_to_named" script has to be copied to /usr/sbin and a link
should be provided from /usr/bin.
3. A perl script "named-bootconf.pl" is available in /usr/bin. This script is
used to convert the existing named.boot file to named.conf file.
4. The new BIND configuration file "named.conf" can be created in
either of the two methods discussed below:
• If the configuration file "named.boot" already exists, create the
new configuration file executing the command:
/usr/bin/named-bootconf.pl named.boot > named.conf
• If a BIND configuration file does not exist:
execute hosts_to_named with appropriate options
The Primary Master Server’s Boot File
Prior to BIND 8.1.2, the /etc/named.boot file was the configuration file
used for BIND. The boot file, /etc/named.boot, tells the primary master
server the location of all the data files it needs. The primary name server
loads its database from these data files. The hosts_to_named program
creates the named.boot file.