Nie jesteś zalogowany.
Jeśli nie posiadasz konta, zarejestruj je już teraz! Pozwoli Ci ono w pełni korzystać z naszego serwisu. Spamerom dziękujemy!

Ogłoszenie

Prosimy o pomoc dla małej Julki — przekaż 1% podatku na Fundacji Dzieciom zdazyć z Pomocą.
Więcej informacji na dug.net.pl/pomagamy/.

Strony: 1

 

#1  2015-07-17 17:08:25

  ptaszol - Użytkownik

ptaszol
Użytkownik
Zarejestrowany: 2013-02-11

Problem - dwa serwery bind

Witam,

Na jednej ze swoich maszyn (debian 7.8) najprawdopodobniej mam zainstalowane 2 serwery bind9.
Gdy uruchamiam serwer bind /etc/init.d/bind9 w logach pojawia mi się następujące wpisy:

Kod:

Jul 17 17:00:05 dc01 named[3233]: starting BIND 9.8.4-rpz2+rl005.12-P1 -u bind
Jul 17 17:00:05 dc01 named[3233]: built with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/var' '--enable-threads' '--enable-largefile' '--with-libtool' '--enable-shared' '--enable-static' '--with-openssl=/usr' '--with-gssapi=/usr' '--with-gnu-ld' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2'
Jul 17 17:00:05 dc01 named[3233]: ----------------------------------------------------
Jul 17 17:00:05 dc01 named[3233]: BIND 9 is maintained by Internet Systems Consortium,
Jul 17 17:00:05 dc01 named[3233]: Inc. (ISC), a non-profit 501(c)(3) public-benefit
Jul 17 17:00:05 dc01 named[3233]: corporation.  Support and training for BIND 9 are
Jul 17 17:00:05 dc01 named[3233]: available at https://www.isc.org/support
Jul 17 17:00:05 dc01 named[3233]: ----------------------------------------------------
Jul 17 17:00:05 dc01 named[3233]: adjusted limit on open files from 4096 to 1048576
Jul 17 17:00:05 dc01 named[3233]: found 4 CPUs, using 4 worker threads
Jul 17 17:00:05 dc01 named[3233]: using up to 4096 sockets
Jul 17 17:00:05 dc01 named[3233]: loading configuration from '/etc/bind/named.conf'
Jul 17 17:00:05 dc01 named[3233]: reading built-in trusted keys from file '/etc/bind/bind.keys'
Jul 17 17:00:05 dc01 named[3233]: using default UDP/IPv4 port range: [1024, 65535]
Jul 17 17:00:05 dc01 named[3233]: using default UDP/IPv6 port range: [1024, 65535]
Jul 17 17:00:05 dc01 named[3233]: listening on IPv4 interface lo, 127.0.0.1#53
Jul 17 17:00:05 dc01 named[3233]: listening on IPv4 interface eth0, 192.168.0.141#53
Jul 17 17:00:05 dc01 named[3233]: generating session key for dynamic DNS
Jul 17 17:00:05 dc01 named[3233]: sizing zone task pool based on 0 zones
Jul 17 17:00:05 dc01 named[3233]: Loading 'AD DNS Zone' using driver dlopen
Jul 17 17:00:05 dc01 named[3233]: samba_dlz: started for DN DC=dc01,DC=gtc
Jul 17 17:00:05 dc01 named[3233]: samba_dlz: starting configure
Jul 17 17:00:05 dc01 named[3233]: samba_dlz: configured writeable zone 'dc01.gtc'
Jul 17 17:00:05 dc01 named[3233]: samba_dlz: configured writeable zone '0.168.192.in-addr.arpa'
Jul 17 17:00:05 dc01 named[3233]: samba_dlz: configured writeable zone '_msdcs.dc01.gtc'
Jul 17 17:00:05 dc01 named[3233]: set up managed keys zone for view _default, file 'managed-keys.bind'
Jul 17 17:00:05 dc01 named[3233]: Warning: 'empty-zones-enable/disable-empty-zone' not set: disabling RFC 1918 empty zones
Jul 17 17:00:05 dc01 named[3233]: automatic empty zone: 0.IN-ADDR.ARPA
Jul 17 17:00:05 dc01 named[3233]: automatic empty zone: 127.IN-ADDR.ARPA
Jul 17 17:00:05 dc01 named[3233]: automatic empty zone: 254.169.IN-ADDR.ARPA
Jul 17 17:00:05 dc01 named[3233]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Jul 17 17:00:05 dc01 named[3233]: automatic empty zone: 100.51.198.IN-ADDR.ARPA
Jul 17 17:00:05 dc01 named[3233]: automatic empty zone: 113.0.203.IN-ADDR.ARPA
Jul 17 17:00:05 dc01 named[3233]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Jul 17 17:00:05 dc01 named[3233]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Jul 17 17:00:05 dc01 named[3233]: automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Jul 17 17:00:05 dc01 named[3233]: automatic empty zone: D.F.IP6.ARPA
Jul 17 17:00:05 dc01 named[3233]: automatic empty zone: 8.E.F.IP6.ARPA
Jul 17 17:00:05 dc01 named[3233]: automatic empty zone: 9.E.F.IP6.ARPA
Jul 17 17:00:05 dc01 named[3233]: automatic empty zone: A.E.F.IP6.ARPA
Jul 17 17:00:05 dc01 named[3233]: automatic empty zone: B.E.F.IP6.ARPA
Jul 17 17:00:05 dc01 named[3233]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
Jul 17 17:00:05 dc01 named[3233]: open: /etc/bind/rndc.key: file not found
Jul 17 17:00:05 dc01 named[3233]: couldn't add command channel 127.0.0.1#953: file not found
Jul 17 17:00:05 dc01 named[3233]: open: /etc/bind/rndc.key: file not found
Jul 17 17:00:05 dc01 named[3233]: couldn't add command channel ::1#953: file not found
Jul 17 17:00:05 dc01 named[3233]: the working directory is not writable
Jul 17 17:00:05 dc01 named[3233]: managed-keys-zone ./IN: loaded serial 0
Jul 17 17:00:05 dc01 named[3233]: running
Jul 17 17:00:08 dc01 named[3233]: error (network unreachable) resolving '2.pool.ntp.org/A/IN': 2001:503:ba3e::2:30#53
Jul 17 17:00:08 dc01 named[3233]: error (network unreachable) resolving '2.pool.ntp.org/AAAA/IN': 2001:503:ba3e::2:30#53
Jul 17 17:00:08 dc01 named[3233]: error (network unreachable) resolving './NS/IN': 2001:503:ba3e::2:30#53
Jul 17 17:00:08 dc01 named[3233]: error (network unreachable) resolving 'keeper.slican.pl/A/IN': 2001:503:ba3e::2:30#53
Jul 17 17:00:09 dc01 named[3233]: error (network unreachable) resolving 'axence.net/A/IN': 2001:503:ba3e::2:30#53
Jul 17 17:00:11 dc01 named[3233]: error (network unreachable) resolving '2.pool.ntp.org/A/IN': 2001:500:40::1#53
Jul 17 17:00:11 dc01 named[3233]: error (network unreachable) resolving '2.pool.ntp.org/AAAA/IN': 2001:500:40::1#53
Jul 17 17:00:13 dc01 named[3233]: error (network unreachable) resolving 'ns69.1and1.pl/A/IN': 2a02:38:14::146#53
Jul 17 17:00:13 dc01 named[3233]: error (network unreachable) resolving 'ns69.1and1.pl/AAAA/IN': 2a02:38:14::146#53
Jul 17 17:00:13 dc01 named[3233]: error (network unreachable) resolving 'ns70.1and1.pl/A/IN': 2a02:38:14::146#53
Jul 17 17:00:13 dc01 named[3233]: error (network unreachable) resolving 'ns70.1and1.pl/AAAA/IN': 2a02:38:14::146#53
Jul 17 17:00:14 dc01 named[3233]: error (network unreachable) resolving 'dns.home.pl/A/IN': 2a02:38:14::146#53
Jul 17 17:00:14 dc01 named[3233]: error (network unreachable) resolving 'dns2.home.pl/A/IN': 2a02:38:14::146#53
Jul 17 17:00:14 dc01 named[3233]: error (network unreachable) resolving 'dns.home.pl/AAAA/IN': 2a02:38:14::146#53
Jul 17 17:00:14 dc01 named[3233]: error (network unreachable) resolving 'dns2.home.pl/AAAA/IN': 2a02:38:14::146#53
Jul 17 17:00:14 dc01 named[3233]: error (network unreachable) resolving 'dns3.home.pl/A/IN': 2a02:38:14::146#53
Jul 17 17:00:14 dc01 named[3233]: error (network unreachable) resolving 'dns3.home.pl/AAAA/IN': 2a02:38:14::146#53
Jul 17 17:00:17 dc01 named[3233]: success resolving 'dns.home.pl/A' (in 'home.pl'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jul 17 17:00:18 dc01 named[3233]: success resolving 'axence.net/AAAA' (in 'axence.net'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jul 17 17:00:33 dc01 named[3233]: error (network unreachable) resolving '_sip._udp.sip.inotel.pl/SRV/IN': 2a00:4120:8000:2::186#53
Jul 17 17:00:33 dc01 named[3233]: error (network unreachable) resolving '_sip._udp.sip.inotel.pl/SRV/IN': 2001:678:4::2#53
Jul 17 17:00:33 dc01 named[3233]: error (network unreachable) resolving '_sip._udp.sip.inotel.pl/SRV/IN': 2001:1a68:0:17::238#53
Jul 17 17:00:35 dc01 named[3233]: error (network unreachable) resolving 'sip.inotel.pl/A/IN': 2a00:4120:8000:2::186#53
Jul 17 17:00:35 dc01 named[3233]: error (network unreachable) resolving 'sip.inotel.pl/A/IN': 2001:678:4::2#53
Jul 17 17:00:35 dc01 named[3233]: error (network unreachable) resolving 'sip.inotel.pl/A/IN': 2001:1a68:0:17::238#53

Gdy wpisuje polecenie named -v pojawia mi się BIND 9.9.2-P2

Czy moglibyście mi doradzić jak sprawdzić który serwer bind współpracuje z samba 4 AD/DC?
Oraz jak usunąć niepotrzebnego binda??

Pozdrawiam

Offline

 

#2  2015-07-17 17:54:15

  qluk - Pan inż. Cyc

qluk
Pan inż. Cyc
Skąd: Katowice
Zarejestrowany: 2006-05-22

Re: Problem - dwa serwery bind

Jak to instalowałeś?

Offline

 

#3  2015-07-17 19:49:09

  ptaszol - Użytkownik

ptaszol
Użytkownik
Zarejestrowany: 2013-02-11

Re: Problem - dwa serwery bind

Witam,

jak dobrze pamiętam jedną zainstalowałem ze źródeł podczas instalacji samba4 ad/dc
a drugi najprawdopodobniej poprzez apt-get install..

pozdrawiam

Offline

 

#4  2015-07-17 22:14:04

  qluk - Pan inż. Cyc

qluk
Pan inż. Cyc
Skąd: Katowice
Zarejestrowany: 2006-05-22

Re: Problem - dwa serwery bind

No i tak to się kończy jak się na wyrost ze źródeł instaluje w systemie z dystrybucją w pakietach (w sumie przypuszczałem że to jest przyczyną). Sprawdź do czego linkuje named a potem co jest podpięte pod ten skrypt startowy i będziesz wiedział. To który jest obojętne ważne że ładuje dobry plik konfiguracji. Posprzątanie teraz tego będzie raczej uciążliwe.

Offline

 

#5  2015-07-17 23:43:11

  jurgensen - Użytkownik

jurgensen
Użytkownik
Skąd: Wrocław
Zarejestrowany: 2010-01-26

Re: Problem - dwa serwery bind

Jeśli budowałeś sambę z wykorzystaniem bibliotek binda, musisz jeszcze sprawdzić (ldd) jakie biblioteki ma podlinkowana binarka samby

Offline

 

 

Strony: 1

Stopka forum

Powered by PunBB
© Copyright 2002–2005 Rickard Andersson
Nas ludzie lubią po prostu, a nie klikając w przyciski ;-)