From ArchWiki
Revision as of 12:50, 15 April 2017 by Soocki (talk | contribs) (→‎A configuration template for running a domain: point link to more relevant section of the article)
Jump to navigation Jump to search

Tango-edit-clear.pngThis article or section needs language, wiki syntax or style improvements. See Help:Style for reference.Tango-edit-clear.png

Reason: Numerous style and content issues. (Discuss in Talk:BIND#)

Berkeley Internet Name Daemon (BIND) is the reference implementation of the Domain Name System (DNS) protocols.

Note: The organization developing BIND is serving security notices to paying customers up to four days before Linux distributions or the general public.[1]


These few steps show you how to install BIND and set it up as a local caching-only server.

Install the bind package.

Optionally edit /etc/named.conf and add this into the options section, to only allow connections from the localhost:

listen-on {; };

Edit resolv.conf to use the local DNS server,

Start named.service.


When BIND acts as a forwarding DNS server, it merely acts as a cache for known queries, and naively forwards all other requests to a predefined upstream DNS server - such as the one managed by your ISP, or some well-known global DNS service like OpenNIC or Google DNS servers.

To setup a forwarding DNS server, add these lines to /etc/named.conf in either the global options section or in a specific zone, and change IP address according to your setup.

options {
 listen-on {; };
 forwarders {;; };

Do not forget to restart named.service.

A configuration template for running a domain

This is a simple tutorial in howto setup a simple home network DNS-server with bind. In our example we use "domain.tld" as our domain.

For a more elaborate example see Two-in-one DNS server with BIND9.

Another guide at Linux Home Server HOWTO - Domain name system (BIND): Adding your domain will show you how to set up internal network name resolution in no time; short, on-point and very informative.

1. Creating a zonefile

# nano /var/named/
$TTL 7200
; domain.tld
@       IN      SOA     ns01.domain.tld. postmaster.domain.tld. (
                                        2007011601 ; Serial
                                        28800      ; Refresh
                                        1800       ; Retry
                                        604800     ; Expire - 1 week
                                        86400 )    ; Minimum
                IN      NS      ns01
                IN      NS      ns02
ns01            IN      A
ns02            IN      A
localhost       IN      A
@               IN      MX 10   mail
imap            IN      CNAME   mail
smtp            IN      CNAME   mail
@               IN      A
www             IN      A
mail            IN      A
@               IN      TXT     "v=spf1 mx"

$TTL defines the default time-to-live in seconds for all record types. In this example it is 2 hours.

Serial must be incremented manually before restarting named every time you change a resource record for the zone. If you forget to do it slaves will not re-transfer the zone: they only do it if the serial is greater than that of the last time they transferred the zone.

2. Configuring master server

Add your zone to /etc/named.conf:

zone "domain.tld" IN {
        type master;
        file "";
        allow-update { none; };
        notify no;

Start/enable named.service and you are done.

Otherwise reload the configuration files.

The latter option will keep your nameserver available while still allowing the configuration change.

3. Setting this to be your default DNS server

If you are running your own DNS server, you might as well use it for all DNS lookups. This will require the ability to do recursive lookups. In order to prevent DNS Amplification Attacks, recursion is turned off by default for most resolvers. The default Arch /etc/named.conf file allows for recursion only on the loopback interface:

allow-recursion {; };

So to facilitate general DNS lookups from your host, your resolv.conf configuration file must have as a name server. See Resolv.conf#Preserve DNS settings on how to keep this from being overwritten.

If you want to provide name service for your local network; e.g. 192.168.0, you must add the appropriate range of IP addresses to /etc/named.conf:

allow-recursion {;; };

Configuring BIND to serve DNSSEC signed zones

See DNSSEC#BIND (serving signed DNS zones)

Automatically listen on new interfaces

By default bind scan for new interfaces and stop listening on interfaces which no longer exist every hours. You can tune this value by adding :

interface-interval <rescan-timeout-in-minutes>;

parameter into named.conf options section. Max value is 28 days. (40320 min)
You can disable this feature by setting its value to 0.

Then restart the service.

Running BIND in a chrooted environment

Running in a chroot environment is not required but improves security.

Creating the Jail House

In order to do this, we first need to create a place to keep the jail, we shall use /srv/named, and then put the required files into the jail.

 mkdir -p /srv/named/{dev,etc,usr/lib/engines,var/{run,log,named}}
 # Copy over required system files
 cp -av /etc/{localtime,named.conf} /srv/named/etc/
 cp -av /usr/lib/engines/* /srv/named/usr/lib/engines/
 cp -av /var/named/* /srv/named/var/named/.
 # Set up required dev nodes
 mknod /srv/named/dev/null c 1 3
 mknod /srv/named/dev/random c 1 8
 # Set Ownership of the files
 chown -R named:named /srv/named

This should create the required file system for the jail.

Service File

Next we need to create the new service file which will allow force bind into the chroot

 cp -av /usr/lib/systemd/system/named.service /etc/systemd/system/named-chroot.service

we need to edit how the service calls bind.

  ExecStart=/usr/bin/named -4 -f -u named -t "/srv/named"

Now, reload systemd systemctl daemon-reload. Then start named-chroot.service

See also