configure bind9 on debian 10

Hi there!
I try configure bind9 inside two virtual machines. I made this config for my zone
named.conf.option

options {
forwarders {
        8.8.8.8;
     };

    listen-on {
      127.0.0.1;
      192.168.2.1;
    };
};

named.conf.local

zone "network.local" 
{
	type master;
	file "/etc/bind/network.local";
	allow-update { any; };
};

zone "10.168.192.in-addr.arpa"  {
        type master;
        file "/etc/bind/reverse.local";
    allow-update { any; };
};

network.local

$TTL 86400      ;       1 day
example.net.    IN      SOA     server.example.net. admin.example.net. (
                                20110103        ; Serial
                                10800           ; Refresh
                                3600            ; Retry
                                604800          ; Expire
                                86400           ; Minimum TTL
                        )

                IN      NS      server.example.net.
                IN      A       192.168.2.1
localhost       IN      A       127.0.0.1
server          IN      A       192.168.2.1

reverse.local

$TTL 86400      ;       1 day
10.168.192.in-addr.arpa. IN SOA server.example.net. admin.example.net. (
                        20110104        ; Serial
                        10800           ; Refresh
                        3600            ; Retry
                        604800          ; Expire
                        3600 )          ; Minimum

        IN      NS      server.example.net.
1       IN      PTR     example.net.
1       IN      PTR     server.example.net.

After restart bind9 and networking i get:

nslookup server
Server:         192.168.1.1
Address:        192.168.1.1#53

** server can't find server: NXDOMAIN

Where i wrong?

Hi,

For starters, you have some errors in your setup.
Your test zone name is "network.local" in named.conf while the SOA and the RR records in the zonefile refer to "example.net"...


Regarding the following error:

After restart bind9 and networking i get: nslookup server Server: 192.168.1.1 Address: 192.168.1.1#53 ** server can't find server: NXDOMAIN

You get a response from 192.168.1.1, that apparently knows nothing about the host "server".
Check /etc/resolv.conf to see what nameserver(s) are listed there
Also running nslookup without a FQDN, it uses the domain and/or search keywords in /etc/resolv.conf in order to compose the FQDN and do the lookup

Regards

Originally Posted by bathory Hi, For starters, you have some errors in your setup. Regards

Hi. Thansk for the answer.
In fact, server resolve normal now:

nslookup server
Server:		192.168.2.1
Address:	192.168.2.1#53

Name:	server.network.local
Address: 192.168.2.1

But, if i use this command from another vbox machine, i get this message:

nslookup pc1
Server:		192.168.2.1
Address:	192.168.2.1#53

can't find pc1: SERVFAIL

But, if i use this command from another vbox machine, i get this message: nslookup pc1 Server: 192.168.2.1 Address: 192.168.2.1#53 can't find pc1: SERVFAIL

What you get when you run the same query from the nameserver itself. (Note that there is no pc1 A RR in the zonefile you posted in your OP).
If you get an answer from the nameserver, then there should be a firewall perhaps dropping some packets resulting in the SERVFAIL.

You may use the dig command using the syntax below, to see more details about the query and the server answer:

dig pc1.network.local @192.168.2.1