LINUX.ORG.RU
решено ФорумAdmin

Bind9

 , ,


0

1

Не работает BIND. И не могу найти что ему мешает. Понятно что интерфейс…

named -v BIND 9.11.3-1ubuntu1.15+ci202105041610+astra1-Debian

lsof -i :53
named   2705 bind   21u  IPv4  38770      0t0  TCP localhost:domain (LISTEN)
named   2705 bind   23u  IPv4  38774      0t0  TCP x.ru:domain (LISTEN)
named   2705 bind  512u  IPv4  38769      0t0  UDP localhost:domain 
named   2705 bind  513u  IPv4  38769      0t0  UDP localhost:domain 
named   2705 bind  514u  IPv4  38769      0t0  UDP localhost:domain  
named   2705 bind  518u  IPv4  38773      0t0  UDP x.ru:domain 
named   2705 bind  519u  IPv4  38773      0t0  UDP x.ru:domain 
named   2705 bind  520u  IPv4  38773      0t0  UDP x.ru:domain
named -g -c ./named.conf
22-Feb-2023 10:03:08.127 running as: named -g -c ./named.conf
22-Feb-2023 10:03:08.127 ----------------------------------------------------
22-Feb-2023 10:03:08.127 BIND 9 is maintained by Internet Systems Consortium,
22-Feb-2023 10:03:08.127 Inc. (ISC), a non-profit 501(c)(3) public-benefit 
22-Feb-2023 10:03:08.127 corporation.  Support and training for BIND 9 are 
22-Feb-2023 10:03:08.127 available at https://www.isc.org/support
22-Feb-2023 10:03:08.127 ----------------------------------------------------
22-Feb-2023 10:03:08.127 found 4 CPUs, using 4 worker threads
22-Feb-2023 10:03:08.127 using 3 UDP listeners per interface
22-Feb-2023 10:03:08.129 using up to 4096 sockets
22-Feb-2023 10:03:08.138 loading configuration from '/etc/bind/./named.conf'
22-Feb-2023 10:03:08.139 reading built-in trust anchors from file '/etc/bind/bind.keys'
22-Feb-2023 10:03:08.140 initializing GeoIP Country (IPv4) (type 1) DB
22-Feb-2023 10:03:08.140 GEO-106FREE 20170512 Bu
22-Feb-2023 10:03:08.140 initializing GeoIP Country (IPv6) (type 12) DB
22-Feb-2023 10:03:08.141 GEO-106FREE 20170512 Bu

22-Feb-2023 10:02:04.036 GeoIP City (IPv4) (type 2) DB not available
22-Feb-2023 10:02:04.036 GeoIP City (IPv4) (type 6) DB not available
22-Feb-2023 10:02:04.036 GeoIP City (IPv6) (type 30) DB not available
22-Feb-2023 10:02:04.036 GeoIP City (IPv6) (type 31) DB not available
22-Feb-2023 10:02:04.036 GeoIP Region (type 3) DB not available
22-Feb-2023 10:02:04.036 GeoIP Region (type 7) DB not available
22-Feb-2023 10:02:04.036 GeoIP ISP (type 4) DB not available
22-Feb-2023 10:02:04.036 GeoIP Org (type 5) DB not available
22-Feb-2023 10:02:04.036 GeoIP AS (type 9) DB not available
22-Feb-2023 10:02:04.036 GeoIP Domain (type 11) DB not available
22-Feb-2023 10:02:04.036 GeoIP NetSpeed (type 10) DB not available
22-Feb-2023 10:02:04.037 using default UDP/IPv4 port range: [32768, 60999]
22-Feb-2023 10:02:04.037 using default UDP/IPv6 port range: [32768, 60999]
22-Feb-2023 10:02:04.039 listening on IPv6 interfaces, port 53
22-Feb-2023 10:02:04.062 listening on IPv4 interface lo, 127.0.0.1#53
22-Feb-2023 10:02:04.064 binding TCP socket: address in use
22-Feb-2023 10:02:04.065 binding TCP socket: address in use
22-Feb-2023 10:02:04.066 listening on IPv4 interface eth1, 192.168.1.49#53
22-Feb-2023 10:02:04.067 binding TCP socket: address in use
22-Feb-2023 10:02:04.067 unable to listen on any configured interfaces
22-Feb-2023 10:02:04.067 loading configuration: failure
22-Feb-2023 10:02:04.068 exiting (due to fatal error)
netstat -tupln
          
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      2705/named          
tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      1676/cupsd          
tcp        0      0 127.0.0.1:953           0.0.0.0:*               LISTEN      2705/named          
tcp        0      0 192.168.1.49:53         0.0.0.0:*               LISTEN      2705/named                         
tcp6       0      0 ::1:631                 :::*                    LISTEN      1676/cupsd          
udp        0      0 192.168.1.49:53         0.0.0.0:*                           2705/named            
udp        0      0 127.0.0.1:53            0.0.0.0:*                           2705/named


Последнее исправление: Zub80 (всего исправлений: 2)

Ответ на: комментарий от Zub80

В чём тогда проблема? Всё работает. Бинд запущен и слушает 53 порт, как и надо. Ты зачем-то попытался запустить второй его экземляр, который закономерно не смог эти 53 порты занять второй раз, и написал об этом ошибку.

firkax ★★★★★
()