Named Configuration File

In this named_conf_files.cfg example, we specify some named configurations.  Note how, by means of the '#if dnsmaster ... #elif dnsslave ... #endif' directives, we customize the configuration for each master and slave name server.

///////////////////////////////////////////////////////////////////////////////
//
// named_conf_files.cfg
//
///////////////////////////////////////////////////////////////////////////////

#if dnsserver

named.conf
        path "/etc/named.conf"  mode 640 uid =rootuid gid 44

        # Copyright (c) 2001-2003 SuSE Linux AG, Nuernberg, Germany.
        # All rights reserved.

[...]
        
        options {
        
                # The directory statement defines the name server's
                # working directory
        
                directory "/var/lib/named";
        
[...]
        
        # The following zone definitions don't need any modification.
        # The first one is the definition of the root name servers.
        # The second one defines localhost while the third defines the
        # reverse lookup for localhost.
        
        zone "." in {
                type hint;
                file "db.cache";
        ##      file "root.hint";
        };
        
        zone "localhost" in {
                type master;
                file "db.localhost";
        ##      file "localhost.zone";
        };
        
        zone "0.0.127.in-addr.arpa" in {
                type master;
                file "db.127.0.0";
        ##      file "127.0.0.zone";
        };
        
[...]
        
        # pikt
        
        zone "pikt.org" in {
#if dnsmaster
                type master;
                file "master/db.pikt.org";
#elif dnsslave
                type slave;
                file "slave/db.pikt.org";
                masters { 192.168.2.132; };
#endif
        };
        
        zone "pikt.net" in {
#if dnsmaster
                type master;
                file "master/db.pikt.net";
#elif dnsslave
                type slave;
                file "slave/db.pikt.net";
                masters { 192.168.2.132; };
#endif
        };
        
        # earlymusichicago
        
        zone "earlymusichicago.org" in {
#if dnsmaster
                type master;
                file "master/db.earlymusichicago.org";
#elif dnsslave
                type slave;
                file "slave/db.earlymusichicago.org";
                masters { 192.168.2.132; };
#endif
        };
        
        zone "earlymusichicago.com" in {
#if dnsmaster
                type master;
                file "master/db.earlymusichicago.com";
#elif dnsslave
                type slave;
                file "slave/db.earlymusichicago.com";
                masters { 192.168.2.132; };
#endif
        };
        
[...]

#endif

///////////////////////////////////////////////////////////////////////////////

On the piktmaster system, we would install the named.conf file to both master and slave name server system with, for example:

# piktc -iv +F named.conf +H dnsserver        [or: ... +H dnsmaster dnsslave]

For more examples, see Samples.

 
Home | FAQ | News | Intro | Samples | Tutorial | Reference | Software
Developer's Notes | Licensing | Authors | Pikt-Users | Pikt-Workers | Related Projects | Site Index | Privacy Policy | Contact Us
Page best viewed at 1024x768 or greater.   Page last updated 2019-01-12.   This site is PIKT® powered.
Copyright © 1998-2019 Robert Osterlund. All rights reserved.
Home FAQ News Intro Samples Tutorial Reference Software
PIKT Logo
PIKT Page Title
View sample
iptables firewall
script config file