The Master Server Configuration

The named.conf file for a master server looks very much like the configuration file for a secondary server. In Listing 4.9, falcon was the slave server for foobirds.org and 16.172.in-addr.arpa, and wren was the master server for those domains. The named.conf file for wren is shown in Listing 4.10.

Listing 4.10: A DNS Master Server Configuration

$ cat /etc/named.conf options {

directory "/var/named";

// a master nameserver config

type hint; file "named.ca";

zone "0.0.127.in-addr.arpa" { type master; file "named.local";

zone "foobirds.org" { type master; file "foobirds.hosts"; notify yes;

zone "16.172.in-addr.arpa" { type master; file "172.16.reverse"; notify yes;

The zone statements for the foobirds.org and 16.172.in-addr.arpa domains are almost the same as the zone statement for the 0.0.127.in-addr.arpa domain, and they function the same way: The statements declare the zones, say that this is the master server for those zones, and identify the files that contain the database records for those zones. The new zone statements also have two options. notify was added so that the server will send DNS NOTIFY messages to the slave servers whenever the zone file is updated. allow-update is set to none to reject dynamic updates.

So far, the configuration of the master server is the same as any other server—you create a configuration file, a hints file, and a local host reverse zone file. The difference comes from the fact that you must also create the real domain database files. The foobirds.hosts file and the 172.16.reverse file in our example can't be downloaded from a repository. You must create them, and in order to do so, you must understand the syntax and purpose of the database records.

Was this article helpful?

0 0

Post a comment