Install BIND: Use sudo apt install bind9 bind9utils bind9-doc on Ubuntu/Debian, and use sudo dnf install bind bind-utils on CentOS/RHEL; 2. Configure global options: Edit the named.conf.options file to set allow-query, recursion, forwarders and other parameters to allow local network queries and enable recursive resolution; 3. Set forward region: Add forward region definition in named.conf.local and create corresponding region file db.example.local, including SOA, NS and A records to resolve the domain name to IP; 4. Set the reverse zone: Add the reverse zone definition in named.conf.local and create a db.192.168.1 file, configure PTR records to achieve reverse resolution of IP to domain name; 5. Test and start the service: Use named-checkconf and named-checkzone to verify the correctness of the configuration, restart the bind9 or named service after correctness and set up the power-on self-start; 6. Test the resolution function: Test whether the forward and reverse resolution are normal through dig, nslookup or host commands to ensure that the client points to the DNS server IP; in addition, pay attention to security maintenance, such as restricting area transmission, updating serial numbers, monitoring logs, and using rndc for remote management, thereby completing a basic authoritative and recursive DNS server construction.

Setting up a DNS server on Linux using BIND (Berkeley Internet Name Domain) is a common task for managing domain name resolution in a local network or for hosting public domains. BIND is the most widely used DNS server on Unix-like systems. Here's how to configure it step by step on a typical Linux distribution like Ubuntu or CentOS.

1. Install BIND

First, install the BIND package:

On Ubuntu/Debian:

 sudo apt update
sudo apt install bind9 bind9utils bind9-doc

On CentOS/RHEL/Rocky Linux:

 sudo dnf install bind bind-utils

After installation, the main configuration files are usually located in /etc/bind/ (Debian/Ubuntu) or /etc/named.conf (RHEL/CentOS).

2. Basic Configuration ( named.conf.options )

Edit the global options file to define how your DNS server behaves.

On Ubuntu:

 sudo nano /etc/bind/named.conf.options

On CentOS:

 sudo nano /etc/named.conf

Add or modify the options block:

 options {
    directory "/var/cache/bind";

    // Allow queries from local network (adjust as needed)
    allow-query { localhost; 192.168.1.0/24; };

    // Enable recursion for internal clients
    recursion yes;
    allow-recursion { 192.168.1.0/24; };

    // Forward DNS queries to external resolvers (optional)
    forwarders {
        8.8.8.8;
        8.8.4.4;
    };

    dnssec-validation auto;

    // Listen on all interfaces
    listen-on-v6 { any; };
    listen-on { any; };
};

Replace 192.168.1.0/24 with your actual network subnet.

3. Set Up a Forward Zone (Domain to IP)

Suppose you want to resolve example.local to internal IPs.

Step 1: Define the zone in named.conf.local

 sudo nano /etc/bind/named.conf.local

Add:

 zone "example.local" {
    type master;
    file "/etc/bind/zones/db.example.local";
};

Make sure the zones directory exists:

 sudo mkdir -p /etc/bind/zones

Step 2: Create the forward zone file

 sudo nano /etc/bind/zones/db.example.local

Content:

 $TTL 86400
@ IN SOA ns1.example.local. admin.example.local. (
                        2024040501 ; Serial (use YYYYMMDDNN)
                        3600 ; Refresh
                        1800 ; Retry
                        604800; Expire
                        86400 ); Minimum TTL

; Name Servers
@ IN NS ns1.example.local.

; A Records
@ IN A 192.168.1.10
ns1 IN A 192.168.1.10
www IN A 192.168.1.20
mail IN A 192.168.1.30

4. Set Up a Reverse Zone (IP to Domain)

To resolve IPs back to hostnames (PTR records).

Step 1: Add reverse zone in named.conf.local

 zone "1.168.192.in-addr.arpa" {
    type master;
    file "/etc/bind/zones/db.192.168.1";
};

Step 2: Create the reverse zone file

 sudo nano /etc/bind/zones/db.192.168.1

 $TTL 86400
@ IN SOA ns1.example.local. admin.example.local. (
                        2024040501
                        3600
                        1800
                        604800
                        86400 )

; Name Server
@ IN NS ns1.example.local.

; PTR Records
10 IN PTR ns1.example.local.
20 IN PTR www.example.local.
30 IN PTR mail.example.local.

5. Test Configuration and Start BIND

Check for syntax errors:

 sudo named-checkconf
sudo named-checkzone example.local /etc/bind/zones/db.example.local
sudo named-checkzone 1.168.192.in-addr.arpa /etc/bind/zones/db.192.168.1

If no errors, restart the service:

Ubuntu:

 sudo systemctl restart bind9

CentOS:

 sudo systemctl restart named

Enable on boot:

 sudo systemctl enable bind9 # or named

6. Test DNS Resolution

Use dig , nslookup , or host :

 dig @localhost www.example.local

dig @localhost -x 192.168.1.20 # Reverse lookup

Make sure your client machines use the DNS server by setting their DNS to the server's IP.

Security and Maintenance Tips

• Use access control lists (ACLs) to restrict zone transfers.
• Regularly update serial numbers when editing zone files.
• Monitor logs: /var/log/syslog or /var/log/messages .
• Consider using rndc for remote management:

   sudo rndc reload
  sudo rndc status

  ---

  Basically, that's how you set up a basic authoritative and recursive DNS server with BIND. It's not overly complex, but attention to detail in zone files and permissions is key.

  The above is the detailed content of Configuring a DNS Server on Linux using BIND. For more information, please follow other related articles on the PHP Chinese website!