Bind9 Installation und Kontrolle

Installation bind9

• apt install bind9

Systemctl

Start

• systemctl start bind9

Stop

• systemctl stop bind9

Restart

• systemctl restart bind9

Status

• systemctl status bind9

● named.service - BIND Domain Name Server
     Loaded: loaded (/lib/systemd/system/named.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2023-02-15 13:39:21 CET; 1h 47min ago
       Docs: man:named(8)
   Main PID: 2428 (named)
      Tasks: 4 (limit: 2337)
     Memory: 15.3M
        CPU: 399ms
     CGroup: /system.slice/named.service
             └─2428 /usr/sbin/named -f -u bind

Feb 15 13:39:27 server1.it19.int named[2428]: network unreachable resolving 'ns2.pop-hannover.net/A/IN': 2001:500:856e::30#53
Feb 15 13:39:27 server1.it19.int named[2428]: network unreachable resolving 'ns2.pop-hannover.net/A/IN': 2001:503:eea3::30#53
Feb 15 13:39:27 server1.it19.int named[2428]: network unreachable resolving 'ns2.pop-hannover.net/A/IN': 2001:502:8cc::30#53
Feb 15 13:39:27 server1.it19.int named[2428]: network unreachable resolving 'ns2.pop-hannover.net/A/IN': 2001:502:1ca1::30#53
Feb 15 13:39:27 server1.it19.int named[2428]: network unreachable resolving 'ns2.pop-hannover.net/A/IN': 2001:503:d2d::30#53
Feb 15 13:39:27 server1.it19.int named[2428]: network unreachable resolving 'ns2.pop-hannover.net/A/IN': 2001:500:d937::30#53
Feb 15 13:39:27 server1.it19.int named[2428]: network unreachable resolving 'ns2.pop-hannover.net/A/IN': 2001:502:7094::30#53
Feb 15 13:39:27 server1.it19.int named[2428]: network unreachable resolving 'ns2.pop-hannover.net/A/IN': 2001:503:d414::30#53
Feb 15 13:39:27 server1.it19.int named[2428]: network unreachable resolving 'ns2.pop-hannover.net/AAAA/IN': 2001:502:1ca1::30#53
Feb 15 13:39:27 server1.it19.int named[2428]: network unreachable resolving 'ns2.pop-hannover.net/AAAA/IN': 2001:503:d414::30#53

Logging

systemctl

• journalctl -u named -f

-- Journal begins at Sat 2022-12-03 10:01:44 CET. --
Feb 15 13:39:27 server1.it19.int named[2428]: network unreachable resolving 'ns2.pop-hannover.net/A/IN': 2001:500:856e::30#53
Feb 15 13:39:27 server1.it19.int named[2428]: network unreachable resolving 'ns2.pop-hannover.net/A/IN': 2001:503:eea3::30#53
Feb 15 13:39:27 server1.it19.int named[2428]: network unreachable resolving 'ns2.pop-hannover.net/A/IN': 2001:502:8cc::30#53
Feb 15 13:39:27 server1.it19.int named[2428]: network unreachable resolving 'ns2.pop-hannover.net/A/IN': 2001:502:1ca1::30#53
Feb 15 13:39:27 server1.it19.int named[2428]: network unreachable resolving 'ns2.pop-hannover.net/A/IN': 2001:503:d2d::30#53
Feb 15 13:39:27 server1.it19.int named[2428]: network unreachable resolving 'ns2.pop-hannover.net/A/IN': 2001:500:d937::30#53

Syslog

• grep named /var/log/syslog

Feb 15 13:39:27 server1 named[2428]: network unreachable resolving 'ns2.pop-hannover.net/A/IN': 2001:500:856e::30#53
Feb 15 13:39:27 server1 named[2428]: network unreachable resolving 'ns2.pop-hannover.net/A/IN': 2001:503:eea3::30#53
Feb 15 13:39:27 server1 named[2428]: network unreachable resolving 'ns2.pop-hannover.net/A/IN': 2001:502:8cc::30#53
Feb 15 13:39:27 server1 named[2428]: network unreachable resolving 'ns2.pop-hannover.net/A/IN': 2001:502:1ca1::30#53

Ports

• netstat -lntup | grep ":53"

tcp        0      0 172.17.19.11:53         0.0.0.0:*               LISTEN      2428/named          
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      2428/named          
tcp6       0      0 ::1:53                  :::*                    LISTEN      2428/named          
tcp6       0      0 fe80::a00:27ff:fe09::53 :::*                    LISTEN      2428/named          
udp        0      0 172.17.19.11:53         0.0.0.0:*                           2428/named          
udp        0      0 127.0.0.1:53            0.0.0.0:*                           2428/named          
udp6       0      0 ::1:53                  :::*                                2428/named          
udp6       0      0 fe80::a00:27ff:fe09::53 :::*                                2428/named