Setting up a DNS zone (LAN)

suppose that we are going to set a DNS zone for the local domain: database.db

this is a fictionnal zone which is going to be used as a local network domain such as an intranet.

The name server is not accessible from the outside and only has 1 private LAN address network interface.

i.e nameserver -- 192.168.x.x

Procedure:

1. Install BIND
2. Create a DNS zone in /var/named/chroot/var/named/database.db.zone
Ex. [root@apps named]# database.db.zone
$TTL 86400
@ IN SOA ns1database.db root.database.db. (
42 ; serial (d. adams)
3H ; refresh
15M ; retry
1W ; expiry
1D ) ; minimum

@ IN NS database.db.
@ IN A 192.168.x.x

Futher Reading http://www.xmission.com/~tknarr/rh62config/bind.html

3. Edit /etc/named.conf
ex.ptions {
directory "/var/named";
forwarders { 192.168.50.x; 192.168.50.x; }; or Public IP
forward only;
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";

// version statement for security to avoid
// hacking known weaknesses
version "get lost";

// optional - disables all transfers -
// slaves allowed in zone clauses
allow-transfer {"none";};
allow-recursion { localnets; 192.168.0.0/16; };

/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
};

logging {
channel default_debug {
file "data/named.run";
severity dynamic;
};
};
zone "pipeline.db" IN {
type master;
file "/var/named/pipeline.db.zone";
allow-update { none; };
};

4. Start the service.
To have the service start automatically run ”
Ex. Execute chkconfig named on

5. on your browser key in database.db

end.