System Administration: Another Step toward the BIND - II

Yesterday, we looked at a named.conf file for a single domain we called example.org. Rather than send you back to the earlier article, we'll reproduce the file contents below:

options {
     pid-file "/var/run/bind/run/named.pid";
     directory "/etc/bind";
     // query-source address * port 53; };
//
// a master nameserver config
//
zone "." {
     type hint;
     file "db.root";
};

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

zone "158.253.70.in-addr.arpa" {
     type master;
     file "pri.253.158.70.in-addr.arpa";
};

zone "example.org" {
     type master;
     file "pri.example.org";
};

The file refers to the four other configuration files: db.root, db.local, pri.253.158.70.in-addr.arpa and pri.example.org.

The zone file allow BIND to do its work. But before the daemon can get to the zones, it needs to consult the file above. So, let's look at named.conf and see what it does.

To give you a sort of context, notice that third line from the top lists the directory we've already mentioned previously. If you recall, we said that the configuration file on Debian lived in /etc/bind. The third line from the top of named.conf let's you know where you can find named.conf. That's important because different distributions of Linux put named.conf in different places.

Above the third line, you can see that the file actually starts with what we call the options statement. It contains two lines. The first shows the location of named.pid, which simply contains the process ID of the running named daemon. That may seem like an odd snippet of information to store, but it's very useful for utilities or applications that have to kill and/or restart named.

More significantly, the options statement also defines the directory containing named and files related to its running.

The zone statement identifies the location of several files containing configuration information. (The first two typically do not need altering and appear when you install BIND). You will have to add the reverse and primary zone files, the later of which contains the domain database. named.conf needs the following files designated:

Hints file

This file contains the names and addresses of the root servers on the Internet. The root servers know where the authoritative servers for your domain reside. The first points to the Top Level Domain (com, net, org, etc.) and the next is the authoritative server for your domain.

Local host file

Name servers are the masters of their own loopback domain (127.0.0.1). The point of creating local zone files for each aspect of your localhost is to reduce traffic and allow the same software to work on your system as it does on the network. Reverse zone file

This file maps IP addresses to hosts. It's a reverse image of the zone master or primary zone file. You can recognize a reverse zone file because it has the extension in-addr.arpa.

Primary Zone file

This file, sometimes called the domain database, defines most of the information needed to resolve queries about the domain you administer. It does not come pre-configured when you install BIND. Usually, you have to write this file from scratch or use one of the files accompanying BIND as a template.

The primary zone file maps names to IP addresses and provides information about the services offered by your computers to the Internet, including your web and FTP servers, email, name servers, etc.

Zone files use record classes so that other computers on the Internet can identify your domain and how it points to various resources. The main record classes include:

      SOA (start of authority)
       NS (name server)
        A (host name to address mapping)
      PTR (pointer, which maps addresses to names)
       MX (mail exchanger, which identifies a mail server in the domain) 
    CNAME (canonical name, which defines an alias for a host name in an A record)

It's not necessary to try to memorize or understand these record types at this point. We'll have an opportunity to use them as we begin to write example primary and reverse zone files.

Tomorrow, we'll start with a primary zone file and dissect it so that you can see how these records work. Just remember that BIND runs a daemon called named or NAME-DEE and it has a configuration file called named.conf. In turn, named.conf points to configuration files that named uses to do its job. Our job will consist of making sure we format the records coherently.

______________________

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

this is the best article

Anonymous's picture

this is the best article explaining from the start of BIND and if any one want to manage BIND using BIND Web interface or GUI tools it is very easy for everyone to restart or configuring zone files

The article tells: "The

Laszlo molnar's picture

The article tells: "The third line from the top of named.conf let's you know where you can find named.conf."

According to the manual:
directory
The working directory of the server. Any non-absolute
pathnames in the configuration file will be taken as
relative to this directory. ...

"named.conf" is not neccessarily is in the folder where "directory" points to. What matters is how you start the daemon. You should check with the command "ps" whether it is started with an alternate configuration file.

Laszlo Molnar

indeed

Anonymous's picture

indeed good article to basic questions,

but like he said to register a domain you need nameserver

lets say i want to register foo.com
to what nameservers i will point since i want to control dns

You will point to your own

Anonymous's picture

You will point to your own nameservers. you do this through your domain registrar. Typically they have a form that asks for your server names and IPs:

ns1.foo.com 12.34.56.78
ns2.foo.com 12.34.56.79

He is right, most domain

Anonymous's picture

He is right, most domain registrars have it in their cp panel to access and point your name servers to different entities. This should work in getting BIND up and running

can nameservers be VH

Anonymous's picture

can named servers be virtual host.

on your response, i would have to configure my dns before registering?
correct?

White Paper
Linux Management with Red Hat Satellite: Measuring Business Impact and ROI

Linux has become a key foundation for supporting today's rapidly growing IT environments. Linux is being used to deploy business applications and databases, trading on its reputation as a low-cost operating environment. For many IT organizations, Linux is a mainstay for deploying Web servers and has evolved from handling basic file, print, and utility workloads to running mission-critical applications and databases, physically, virtually, and in the cloud. As Linux grows in importance in terms of value to the business, managing Linux environments to high standards of service quality — availability, security, and performance — becomes an essential requirement for business success.

Learn More

Sponsored by Red Hat

White Paper
Private PaaS for the Agile Enterprise

If you already use virtualized infrastructure, you are well on your way to leveraging the power of the cloud. Virtualization offers the promise of limitless resources, but how do you manage that scalability when your DevOps team doesn’t scale? In today’s hypercompetitive markets, fast results can make a difference between leading the pack vs. obsolescence. Organizations need more benefits from cloud computing than just raw resources. They need agility, flexibility, convenience, ROI, and control.

Stackato private Platform-as-a-Service technology from ActiveState extends your private cloud infrastructure by creating a private PaaS to provide on-demand availability, flexibility, control, and ultimately, faster time-to-market for your enterprise.

Learn More

Sponsored by ActiveState