Birmingham mumbai

[
 288 
]
As you can see, the default 
bind
 configuration is split among several configuration 
files. Here, it includes three others: 
named.conf.options
, 
named.conf.local
, and 
named.conf.default-zones
 (the first of which we already took care of editing). In 
order to resolve local names, we need to create a 
zone file
, which is essentially a 
text file that includes some configuration, a list of hosts, and their IP addresses. 
In order to do this, we need to tell 
bind
 where to find the zone file we're about to 
create. Within 
/etc/bind/named.conf.local
, we need to add a block of code like 
the following to the end of the file:
zone "local.lan" IN { 
    type master; 
    file "/etc/bind/net.local.lan"; 
}; 
Notice that the zone is named 
local.lan
, which is the same name I gave our domain 
in our DHCP server configuration. It's best to keep everything consistent when 
we can. If you use a different domain name than the one I used in my example, 
make sure that it matches here as well. Within the block, we're creating a 
master
 
zone file and
 informing 
bind
 that it can find a file named 
net.local.lan
, stored in 
the 
/etc/bind
 directory. This should be the only change we'll need to make to the 
named.conf.local
 file; we'll only create a single zone file (for the purpose of this 
section). Once you save this file, you'll need to create the 
/etc/bind/net.local.lan
 
file. So, go ahead and open that file in a text editor. Since we haven't created it yet, 
it should be blank. Here's an example of this zone file, completely filled out with 
some sample configuration:
$TTL 1D 
@ IN SOA local.lan. hostmaster.local.lan. ( 
 
202008161; serial 
 
8H ; refresh 
4H ; retry 
4W ; expire 
1D ) ; minimum 
IN A 192.168.1.1 
; 
@ IN NS hermes.local.lan. 
fileserv        IN  A   192.168.1.3 
hermes          IN  A    192.168.1.1 
mailserv        IN  A   192.168.1.5 
mail            IN  CNAME   mailserv. 
web01           IN  A   192.168.1.7 

---

Chapter 11