Kein DNS nach Update auf UCS 3.0.2

german

#1

Hallo,

ein Update eines OX ASE auf UCS 3.0.2 verlief reibungslos und funktionierte ca. 1 Woche fehlerfrei. Nach 7 Tagen gingen alle internen DNS-Anfragen schief. Ein Neustart des Server zeigte, dass es Probleme beim Laden der Host- und PTR-Daten gab. Dass es eine Woche funktionierte lag vermutlich daran, dass parallel ein 2. DNS Server als Secondary mit gecachten Daten lief, sodass wir das Problem erst heute gemerkt haben.

Jun 3 18:15:33 janus named[10109]: starting BIND 9.8.0-P4 -c /etc/bind/named.conf -p 7777 -u bind -f Jun 3 18:15:33 janus named[10109]: 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-dlz-postgres=no' '--with-dlz-mysql=no' '--with-dlz-bdb=yes' '--with-dlz-filesystem=yes' '--with-dlz-ldap=yes' '--with-dlz-stub=yes' '--with-dlz-dlopen' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' 'LDFLAGS=' 'CPPFLAGS=' Jun 3 18:15:33 janus named[10109]: adjusted limit on open files from 1024 to 1048576 Jun 3 18:15:33 janus named[10109]: found 2 CPUs, using 2 worker threads Jun 3 18:15:33 janus named[10109]: using up to 4096 sockets Jun 3 18:15:33 janus named[10109]: loading configuration from '/etc/bind/named.conf' Jun 3 18:15:33 janus named[10109]: reading built-in trusted keys from file '/etc/bind/bind.keys' Jun 3 18:15:33 janus named[10109]: using default UDP/IPv4 port range: [1024, 65535] Jun 3 18:15:33 janus named[10109]: using default UDP/IPv6 port range: [1024, 65535] Jun 3 18:15:33 janus named[10109]: listening on IPv4 interface lo, 127.0.0.1#7777 Jun 3 18:15:33 janus named[10109]: listening on IPv4 interface eth0, 192.168.88.228#7777 Jun 3 18:15:33 janus named[10109]: generating session key for dynamic DNS Jun 3 18:15:33 janus named[10109]: set up managed keys zone for view _default, file 'managed-keys.bind' Jun 3 18:15:33 janus named[10109]: automatic empty zone: 0.IN-ADDR.ARPA Jun 3 18:15:33 janus named[10109]: automatic empty zone: 127.IN-ADDR.ARPA Jun 3 18:15:33 janus named[10109]: automatic empty zone: 254.169.IN-ADDR.ARPA Jun 3 18:15:33 janus named[10109]: automatic empty zone: 2.0.192.IN-ADDR.ARPA Jun 3 18:15:33 janus named[10109]: automatic empty zone: 100.51.198.IN-ADDR.ARPA Jun 3 18:15:33 janus named[10109]: automatic empty zone: 113.0.203.IN-ADDR.ARPA Jun 3 18:15:33 janus named[10109]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA Jun 3 18:15:33 janus named[10109]: 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 Jun 3 18:15:33 janus named[10109]: 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 Jun 3 18:15:33 janus named[10109]: automatic empty zone: D.F.IP6.ARPA Jun 3 18:15:33 janus named[10109]: automatic empty zone: 8.E.F.IP6.ARPA Jun 3 18:15:33 janus named[10109]: automatic empty zone: 9.E.F.IP6.ARPA Jun 3 18:15:33 janus named[10109]: automatic empty zone: A.E.F.IP6.ARPA Jun 3 18:15:33 janus named[10109]: automatic empty zone: B.E.F.IP6.ARPA Jun 3 18:15:33 janus named[10109]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA Jun 3 18:15:33 janus named[10109]: command channel listening on 127.0.0.1#55555 Jun 3 18:15:33 janus named[10109]: zone 88.168.192.in-addr.arpa/IN: could not find NS and/or SOA records Jun 3 18:15:33 janus named[10109]: zone 88.168.192.in-addr.arpa/IN: has 0 SOA records Jun 3 18:15:33 janus named[10109]: zone 88.168.192.in-addr.arpa/IN: has no NS records Jun 3 18:15:33 janus named[10109]: zone 88.168.192.in-addr.arpa/IN: not loaded due to errors. Jun 3 18:15:33 janus named[10109]: zone digitronic-berlin.de/IN: could not find NS and/or SOA records Jun 3 18:15:33 janus named[10109]: zone digitronic-berlin.de/IN: has 0 SOA records Jun 3 18:15:33 janus named[10109]: zone digitronic-berlin.de/IN: has no NS records Jun 3 18:15:33 janus named[10109]: zone digitronic-berlin.de/IN: not loaded due to errors. Jun 3 18:15:33 janus named[10109]: managed-keys-zone ./IN: loaded serial 0 Jun 3 18:15:33 janus named[10109]: running Jun 3 18:15:38 janus named[10127]: starting BIND 9.8.0-P4 -c /etc/bind/named.conf.proxy -u bind -f Jun 3 18:15:38 janus named[10127]: 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-dlz-postgres=no' '--with-dlz-mysql=no' '--with-dlz-bdb=yes' '--with-dlz-filesystem=yes' '--with-dlz-ldap=yes' '--with-dlz-stub=yes' '--with-dlz-dlopen' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' 'LDFLAGS=' 'CPPFLAGS=' Jun 3 18:15:38 janus named[10127]: adjusted limit on open files from 1024 to 1048576 Jun 3 18:15:38 janus named[10127]: found 2 CPUs, using 2 worker threads Jun 3 18:15:38 janus named[10127]: using up to 4096 sockets Jun 3 18:15:38 janus named[10127]: loading configuration from '/etc/bind/named.conf.proxy' Jun 3 18:15:38 janus named[10127]: reading built-in trusted keys from file '/etc/bind/bind.keys' Jun 3 18:15:38 janus named[10127]: using default UDP/IPv4 port range: [1024, 65535] Jun 3 18:15:38 janus named[10127]: using default UDP/IPv6 port range: [1024, 65535] Jun 3 18:15:38 janus named[10127]: listening on IPv4 interface lo, 127.0.0.1#53 Jun 3 18:15:38 janus named[10127]: listening on IPv4 interface eth0, 192.168.88.228#53 Jun 3 18:15:38 janus named[10127]: generating session key for dynamic DNS Jun 3 18:15:38 janus named[10127]: set up managed keys zone for view _default, file 'managed-keys.bind' Jun 3 18:15:38 janus named[10127]: automatic empty zone: 254.169.IN-ADDR.ARPA Jun 3 18:15:38 janus named[10127]: automatic empty zone: 2.0.192.IN-ADDR.ARPA Jun 3 18:15:38 janus named[10127]: automatic empty zone: 100.51.198.IN-ADDR.ARPA Jun 3 18:15:38 janus named[10127]: automatic empty zone: 113.0.203.IN-ADDR.ARPA Jun 3 18:15:38 janus named[10127]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA Jun 3 18:15:38 janus named[10127]: 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 Jun 3 18:15:38 janus named[10127]: 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 Jun 3 18:15:38 janus named[10127]: automatic empty zone: D.F.IP6.ARPA Jun 3 18:15:38 janus named[10127]: automatic empty zone: 8.E.F.IP6.ARPA Jun 3 18:15:38 janus named[10127]: automatic empty zone: 9.E.F.IP6.ARPA Jun 3 18:15:38 janus named[10127]: automatic empty zone: A.E.F.IP6.ARPA Jun 3 18:15:38 janus named[10127]: automatic empty zone: B.E.F.IP6.ARPA Jun 3 18:15:38 janus named[10127]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA Jun 3 18:15:38 janus named[10127]: command channel listening on 127.0.0.1#953 Jun 3 18:15:38 janus named[10127]: zone 0.in-addr.arpa/IN: loaded serial 1 Jun 3 18:15:38 janus named[10127]: zone 127.in-addr.arpa/IN: loaded serial 1 Jun 3 18:15:38 janus named[10127]: zone 255.in-addr.arpa/IN: loaded serial 1 Jun 3 18:15:38 janus named[10127]: zone localhost/IN: loaded serial 2 Jun 3 18:15:38 janus named[10127]: managed-keys-zone ./IN: loaded serial 0 Jun 3 18:15:38 janus named[10127]: running Jun 3 18:15:38 janus named[10127]: zone digitronic-berlin.de/IN: refresh: unexpected rcode (SERVFAIL) from master 127.0.0.1#7777 (source 0.0.0.0#0) Jun 3 18:15:38 janus named[10127]: zone 88.168.192.in-addr.arpa/IN: refresh: unexpected rcode (SERVFAIL) from master 127.0.0.1#7777 (source 0.0.0.0#0) Jun 3 18:16:32 janus master[3642]: process 10085 exited, status 0 Jun 3 18:16:36 janus named[10127]: zone 88.168.192.in-addr.arpa/IN: refresh: unexpected rcode (SERVFAIL) from master 127.0.0.1#7777 (source 0.0.0.0#0) Jun 3 18:16:38 janus named[10127]: zone digitronic-berlin.de/IN: refresh: unexpected rcode (SERVFAIL) from master 127.0.0.1#7777 (source 0.0.0.0#0) Jun 3 18:16:53 janus postfix/qmgr[3905]: 8D92BDB4205: from=<c.wegerich@digitronic-berlin.de>, size=624, nrcpt=1 (queue active)

Der Befehl:

univention-ldapsearch '(&(zoneName=digitronic-berlin.de)(univentionObjectType=dns/forward_zone))'

Liefert folgendes Ergebnis:

[code]root@janus:/var/cache/bind# univention-ldapsearch ‘(&(zoneName=digitronic-berlin.de)(univentionObjectType=dns/forward_zone))’

extended LDIF

LDAPv3

base <dc=digitronic-berlin,dc=de> (default) with scope subtree

filter: (&(zoneName=digitronic-berlin.de)(univentionObjectType=dns/forward_zone))

requesting: ALL

digitronic-berlin.de, dns, digitronic-berlin.de

dn: zoneName=digitronic-berlin.de,cn=dns,dc=digitronic-berlin,dc=de
dNSTTL: 10800
relativeDomainName: @
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/forward_zone
nSRecord: janus.digitronic-berlin.de.
nSRecord: 192.168.88.228.
sOARecord: janus.digitronic-berlin.de. root.digitronic-berlin.de. 61 28800 720
0 604800 10800

search result

search: 3
result: 0 Success

numResponses: 2

numEntries: 1

[/code]

Host- und PTR-Records sind nach wie vor vorhanden:

[code]root@janus:~# udm dns/host_record list --superordinate=zoneName=digitronic-berlin.de,cn=dns,dc=digitronic-berlin,dc=de | more

DN: relativeDomainName=janus,zoneName=digitronic-berlin.de,cn=dns,dc=digitronic-berlin,dc=de
ARG: None
a: 192.168.88.228
txt: None
mx: None
name: janus
zonettl: 80600 seconds

DN: relativeDomainName=rhea,zoneName=digitronic-berlin.de,cn=dns,dc=digitronic-berlin,dc=de
ARG: None
a: 192.168.88.231
txt: None
mx: None
name: rhea
zonettl: 3 hours

DN: relativeDomainName=dione,zoneName=digitronic-berlin.de,cn=dns,dc=digitronic-berlin,dc=de
ARG: None
a: 192.168.88.232
txt: None
mx: None
name: dione
zonettl: 3 hours
[/code]

[code]root@janus:~# udm dns/ptr_record list --superordinate=zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitronic-berlin,dc=de | more

DN: relativeDomainName=228,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitronic-berlin,dc=de
ARG: None
ptr_record: janus.digitronic-berlin.de.
address: 228

DN: relativeDomainName=233,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitronic-berlin,dc=de
ARG: None
ptr_record: ganymed.digitronic-berlin.de.
address: 233

DN: relativeDomainName=234,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitronic-berlin,dc=de
ARG: None
ptr_record: jupiter.digitronic-berlin.de.
address: 234
[/code]

Was könnte hier schief laufen?
Freundliche Grüße
Hans-Jürgen


#2

Hallo,

wir konnten dies Bereits für Zonen beobachten die mit falscher Syntax angelegt wurde. An [bug]28363[/bug] finden Sie ein Script was diese Zonen finden und die Syntax korrigieren kann.
Bitte prüfen Sie nach dem Ausführen ob der Zone-Transfer zum bind-Proxy wieder möglich ist.

Mit freundlichen Grüßen
Janis Meybohm


#3

Hallo,

danke für den Hinweis zu dem Script. Es werden scheinbar keine korrupten Zonendaten gefunden, zumindest gibt das Script nichts aus.

Noch eine Ergänzung zum Fehlerbild:
Anfangs gab es bei Restart des bind9 noch eine zusätzliche Fehlermeldung:
managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found

Jun 3 10:03:36 janus named[19350]: starting BIND 9.8.0-P4 -c /etc/bind/named.conf -p 7777 -u bind -f Jun 3 10:03:36 janus named[19350]: 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-dlz-postgres=no' '--with-dlz-mysql=no' '--with-dlz-bdb=yes' '--with-dlz-filesystem=yes' '--with-dlz-ldap=yes' '--with-dlz-stub=yes' '--with-dlz-dlopen' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' 'LDFLAGS=' 'CPPFLAGS=' Jun 3 10:03:36 janus named[19350]: adjusted limit on open files from 1024 to 1048576 Jun 3 10:03:36 janus named[19350]: found 2 CPUs, using 2 worker threads Jun 3 10:03:36 janus named[19350]: using up to 4096 sockets Jun 3 10:03:37 janus named[19352]: starting BIND 9.8.0-P4 -c /etc/bind/named.conf.proxy -u bind -f Jun 3 10:03:37 janus named[19352]: 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-dlz-postgres=no' '--with-dlz-mysql=no' '--with-dlz-bdb=yes' '--with-dlz-filesystem=yes' '--with-dlz-ldap=yes' '--with-dlz-stub=yes' '--with-dlz-dlopen' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' 'LDFLAGS=' 'CPPFLAGS=' Jun 3 10:03:37 janus named[19352]: adjusted limit on open files from 1024 to 1048576 Jun 3 10:03:37 janus named[19352]: found 2 CPUs, using 2 worker threads Jun 3 10:03:37 janus named[19352]: using up to 4096 sockets Jun 3 10:03:37 janus named[19350]: loading configuration from '/etc/bind/named.conf' Jun 3 10:03:37 janus named[19352]: loading configuration from '/etc/bind/named.conf.proxy' Jun 3 10:03:37 janus named[19350]: reading built-in trusted keys from file '/etc/bind/bind.keys' Jun 3 10:03:37 janus named[19352]: reading built-in trusted keys from file '/etc/bind/bind.keys' Jun 3 10:03:37 janus named[19350]: using default UDP/IPv4 port range: [1024, 65535] Jun 3 10:03:37 janus named[19352]: using default UDP/IPv4 port range: [1024, 65535] Jun 3 10:03:37 janus named[19350]: using default UDP/IPv6 port range: [1024, 65535] Jun 3 10:03:37 janus named[19352]: using default UDP/IPv6 port range: [1024, 65535] Jun 3 10:03:37 janus named[19350]: listening on IPv6 interfaces, port 7777 Jun 3 10:03:37 janus named[19352]: listening on IPv6 interfaces, port 53 Jun 3 10:03:37 janus named[19350]: listening on IPv4 interface lo, 127.0.0.1#7777 Jun 3 10:03:37 janus named[19352]: listening on IPv4 interface lo, 127.0.0.1#53 Jun 3 10:03:37 janus named[19350]: listening on IPv4 interface eth0, 192.168.88.228#7777 Jun 3 10:03:37 janus named[19350]: generating session key for dynamic DNS Jun 3 10:03:37 janus named[19352]: listening on IPv4 interface eth0, 192.168.88.228#53 Jun 3 10:03:37 janus named[19350]: set up managed keys zone for view _default, file 'managed-keys.bind' Jun 3 10:03:37 janus named[19350]: automatic empty zone: 0.IN-ADDR.ARPA Jun 3 10:03:37 janus named[19350]: automatic empty zone: 127.IN-ADDR.ARPA Jun 3 10:03:37 janus named[19350]: automatic empty zone: 254.169.IN-ADDR.ARPA Jun 3 10:03:37 janus named[19350]: automatic empty zone: 2.0.192.IN-ADDR.ARPA Jun 3 10:03:37 janus named[19350]: automatic empty zone: 100.51.198.IN-ADDR.ARPA Jun 3 10:03:37 janus named[19350]: automatic empty zone: 113.0.203.IN-ADDR.ARPA Jun 3 10:03:37 janus named[19350]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA Jun 3 10:03:37 janus named[19350]: 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 Jun 3 10:03:37 janus named[19350]: 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 Jun 3 10:03:37 janus named[19350]: automatic empty zone: D.F.IP6.ARPA Jun 3 10:03:37 janus named[19350]: automatic empty zone: 8.E.F.IP6.ARPA Jun 3 10:03:37 janus named[19350]: automatic empty zone: 9.E.F.IP6.ARPA Jun 3 10:03:37 janus named[19350]: automatic empty zone: A.E.F.IP6.ARPA Jun 3 10:03:37 janus named[19350]: automatic empty zone: B.E.F.IP6.ARPA Jun 3 10:03:37 janus named[19350]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA Jun 3 10:03:37 janus named[19352]: generating session key for dynamic DNS Jun 3 10:03:37 janus named[19352]: set up managed keys zone for view _default, file 'managed-keys.bind' Jun 3 10:03:37 janus named[19352]: automatic empty zone: 254.169.IN-ADDR.ARPA Jun 3 10:03:37 janus named[19352]: automatic empty zone: 2.0.192.IN-ADDR.ARPA Jun 3 10:03:37 janus named[19352]: automatic empty zone: 100.51.198.IN-ADDR.ARPA Jun 3 10:03:37 janus named[19352]: automatic empty zone: 113.0.203.IN-ADDR.ARPA Jun 3 10:03:37 janus named[19352]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA Jun 3 10:03:37 janus named[19352]: 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 Jun 3 10:03:37 janus named[19352]: 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 Jun 3 10:03:37 janus named[19352]: automatic empty zone: D.F.IP6.ARPA Jun 3 10:03:37 janus named[19352]: automatic empty zone: 8.E.F.IP6.ARPA Jun 3 10:03:37 janus named[19352]: automatic empty zone: 9.E.F.IP6.ARPA Jun 3 10:03:37 janus named[19352]: automatic empty zone: A.E.F.IP6.ARPA Jun 3 10:03:37 janus named[19352]: automatic empty zone: B.E.F.IP6.ARPA Jun 3 10:03:37 janus named[19352]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA Jun 3 10:03:37 janus named[19352]: command channel listening on 127.0.0.1#953 Jun 3 10:03:37 janus named[19350]: command channel listening on 127.0.0.1#55555 Jun 3 10:03:37 janus named[19350]: zone 88.168.192.in-addr.arpa/IN: could not find NS and/or SOA records Jun 3 10:03:37 janus named[19350]: zone 88.168.192.in-addr.arpa/IN: has 0 SOA records Jun 3 10:03:37 janus named[19350]: zone 88.168.192.in-addr.arpa/IN: has no NS records Jun 3 10:03:37 janus named[19350]: zone 88.168.192.in-addr.arpa/IN: not loaded due to errors. Jun 3 10:03:37 janus named[19350]: zone digitronic-berlin.de/IN: could not find NS and/or SOA records Jun 3 10:03:37 janus named[19350]: zone digitronic-berlin.de/IN: has 0 SOA records Jun 3 10:03:37 janus named[19350]: zone digitronic-berlin.de/IN: has no NS records Jun 3 10:03:37 janus named[19350]: zone digitronic-berlin.de/IN: not loaded due to errors. Jun 3 10:03:37 janus named[19350]: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found Jun 3 10:03:37 janus named[19352]: zone 0.in-addr.arpa/IN: loaded serial 1 Jun 3 10:03:37 janus named[19352]: zone 127.in-addr.arpa/IN: loaded serial 1 Jun 3 10:03:37 janus named[19352]: zone 255.in-addr.arpa/IN: loaded serial 1 Jun 3 10:03:37 janus named[19350]: managed-keys-zone ./IN: loaded serial 0 Jun 3 10:03:37 janus named[19350]: running Jun 3 10:03:37 janus named[19352]: zone localhost/IN: loaded serial 2 Jun 3 10:03:37 janus named[19352]: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found Jun 3 10:03:37 janus named[19352]: managed-keys-zone ./IN: loaded serial 0 Jun 3 10:03:37 janus named[19352]: running Jun 3 10:03:37 janus named[19352]: zone digitronic-berlin.de/IN: refresh: unexpected rcode (SERVFAIL) from master 127.0.0.1#7777 (source 0.0.0.0#0) Jun 3 10:03:37 janus named[19352]: zone 88.168.192.in-addr.arpa/IN: refresh: unexpected rcode (SERVFAIL) from master 127.0.0.1#7777 (source 0.0.0.0#0) Jun 3 10:04:34 janus named[19352]: zone digitronic-berlin.de/IN: refresh: unexpected rcode (SERVFAIL) from master 127.0.0.1#7777 (source 0.0.0.0#0) Jun 3 10:04:36 janus named[19352]: zone 88.168.192.in-addr.arpa/IN: refresh: unexpected rcode (SERVFAIL) from master 127.0.0.1#7777 (source 0.0.0.0#0)
Einem Hinweis aus einem Debian-Forum folgend, habe ich dann eine leere Datei /var/cache/bind/managed-keys.bind angelegt.
google.de/url?sa=t&rct=j&q=& … GE&cad=rja
Danach verschwand die Fehlermeldung zwar, änderte aber nichts am Ergebnis.

Freundliche Grüße
Hans-Jürgen Wegerich


#4

Hallo,

vielleicht finden Sie bei einem manuellen Zonentransfer Hinweise auf den Fehler.

dig @127.0.0.1 -p7777 digitronic-berlin.de axfr

Könnte es sein, dass Änderungen wie in Mx_record lässt sich nicht mit UDM Kommandozeile eintragen diskutiert eine Rolle spielen?
Siehe auch [bug]28363[/bug], [bug]23945[/bug], [bug]28367[/bug]

Viele Grüße,
Dirk Ahrnke


#5

Hallo,

danke für die Hinweise, aber bisher konnte der Fehler nicht gefunden werden. Das Script hat keine Fehler gefunden. Ich hatte allerdings in der Forward-Zone 2 Host-Einträge die dort vermutlich nicht hin gehörten, allerdings dort auch früher schon waren, ohne dass das Probleme bereitete.

digitronic-berlin.de A 192.168.88.282 digitronic-berlin.de. A 192.168.88.228

Ich habe beide Einträge mit UDM entfernt, bind9 neu gestartet, den Server rebootet. Es hat alles nichts gebracht.
Die Forward-Zone sieht momentan so aus:

[code]root@janus:/home/hjw# udm dns/forward_zone list

DN: zoneName=digitronic-berlin.de,cn=dns,dc=digitronic-berlin,dc=de
ARG: None
expire: 7 days
ttl: 3 hours
serial: 65
txt: None
a: 192.168.88.228
retry: 2 hours
zone: digitronic-berlin.de
zonettl: 3 hours
refresh: 8 hours
contact: root@digitronic-berlin.de.
nameserver: janus.digitronic-berlin.de.
mx: None
[/code]

Ich weiß absolut nicht, was hier falsch läuft.

Viele Grüße
Hans-Jürgen


#6

Hallo,

zunächst noch ein Nachtrag: Die Meldung bzgl. “managed-keys.bind failed” hat mit diesem Problem nichts zu tun und kann ignoriert werden. Vermutlich haben sie das ja schon aus dem Resultat des beschriebenen Workarounds geschlußfolgert.

Für eine weitere Analyse ist es sinnvoll, den Debug-Level von bind zu erhöhen. Ab UCS 3.1-1 geht das bequem per UCR-Variable ([bug]29562[/bug]).

Auf Ihrem System erweitern Sie bitte die “OPTS”-Zeile der Datei/etc/runit/univention-bind/run um die Option “-d 10”, z.B.:

OPTS="-d 10 -c /etc/bind/named.conf -p 7777 -u bind -f"

Nach einem Neustart von univention-bind sollten die Debug-Meldungen nach “/var/cache/bind/named.run” protokolliert werden. Letzteres kann ich gerade nicht verifizieren, auf UCS 3.1-1 geht das Logging nach /var/log/daemon.log.
Für univention-bind-proxy sollten Sie analog vorgehen.

In den Protokollen sieht man dann hoffentlich, welches Objekt als letztes verarbeitet wurde.

Wenn Sie selber mit den Debugging-Informationen nicht weiterkommen, wäre es sinnvoll, wenn Sie die Ausgabe des oben genannten “dig axfr” und von “univention-ldapsearch -xLLL -b cn=dns,$(ucr get ldap/base)” entweder hier anhängen oder über http://upload.univention.de/ bereitstellen könnten.

Viele Grüße,
Dirk Ahrnke


#7

Hallo,

hier nun die Ergebnisse nach Erhöhung des Loglevels.
/var/cache/bind/named.run

[code]28-Jun-2013 13:20:07.433 now using logging configuration from config file
28-Jun-2013 13:20:07.433 client @0xb4cca008: udprecv
28-Jun-2013 13:20:07.433 client @0xb4c89008: udprecv
28-Jun-2013 13:20:07.433 client @0xb4c48008: accept
28-Jun-2013 13:20:07.433 client @0xb4c07008: udprecv
28-Jun-2013 13:20:07.433 client @0xb4bc6008: udprecv
28-Jun-2013 13:20:07.433 client @0xb4b85008: accept
28-Jun-2013 13:20:07.433 client @0xb4b44008: udprecv
28-Jun-2013 13:20:07.433 client @0xb4b03008: udprecv
28-Jun-2013 13:20:07.433 client @0xb4ac2008: accept
28-Jun-2013 13:20:07.433 load_configuration: success
28-Jun-2013 13:20:07.433 zone 0.IN-ADDR.ARPA/IN: starting load
28-Jun-2013 13:20:07.433 zone 0.IN-ADDR.ARPA/IN: number of nodes in database: 0
28-Jun-2013 13:20:07.433 zone 0.IN-ADDR.ARPA/IN: loaded
28-Jun-2013 13:20:07.433 zone_settimer: zone 0.IN-ADDR.ARPA/IN: enter
28-Jun-2013 13:20:07.433 zone 127.IN-ADDR.ARPA/IN: starting load
28-Jun-2013 13:20:07.433 zone 127.IN-ADDR.ARPA/IN: number of nodes in database: 0
28-Jun-2013 13:20:07.433 zone 127.IN-ADDR.ARPA/IN: loaded
28-Jun-2013 13:20:07.433 zone_settimer: zone 127.IN-ADDR.ARPA/IN: enter
28-Jun-2013 13:20:07.433 zone 254.169.IN-ADDR.ARPA/IN: starting load
28-Jun-2013 13:20:07.433 zone 254.169.IN-ADDR.ARPA/IN: number of nodes in database: 0
28-Jun-2013 13:20:07.433 zone 254.169.IN-ADDR.ARPA/IN: loaded
28-Jun-2013 13:20:07.433 zone_settimer: zone 254.169.IN-ADDR.ARPA/IN: enter
28-Jun-2013 13:20:07.433 zone 2.0.192.IN-ADDR.ARPA/IN: starting load
28-Jun-2013 13:20:07.433 zone 2.0.192.IN-ADDR.ARPA/IN: number of nodes in database: 0
28-Jun-2013 13:20:07.433 zone 2.0.192.IN-ADDR.ARPA/IN: loaded
28-Jun-2013 13:20:07.433 zone_settimer: zone 2.0.192.IN-ADDR.ARPA/IN: enter
28-Jun-2013 13:20:07.433 zone 88.168.192.in-addr.arpa/IN: starting load
28-Jun-2013 13:20:07.434 zone 88.168.192.in-addr.arpa/IN: number of nodes in database: 0
28-Jun-2013 13:20:07.434 zone 88.168.192.in-addr.arpa/IN: loaded
28-Jun-2013 13:20:07.435 zone 88.168.192.in-addr.arpa/IN: could not find NS and/or SOA records
28-Jun-2013 13:20:07.435 zone 88.168.192.in-addr.arpa/IN: has 0 SOA records
28-Jun-2013 13:20:07.435 zone 88.168.192.in-addr.arpa/IN: has no NS records
28-Jun-2013 13:20:07.435 zone 88.168.192.in-addr.arpa/IN: not loaded due to errors.
28-Jun-2013 13:20:07.435 zone 100.51.198.IN-ADDR.ARPA/IN: starting load
28-Jun-2013 13:20:07.435 zone 100.51.198.IN-ADDR.ARPA/IN: number of nodes in database: 0
28-Jun-2013 13:20:07.435 zone 100.51.198.IN-ADDR.ARPA/IN: loaded
28-Jun-2013 13:20:07.435 zone_settimer: zone 100.51.198.IN-ADDR.ARPA/IN: enter
28-Jun-2013 13:20:07.435 zone 113.0.203.IN-ADDR.ARPA/IN: starting load
28-Jun-2013 13:20:07.435 zone 113.0.203.IN-ADDR.ARPA/IN: number of nodes in database: 0
28-Jun-2013 13:20:07.435 zone 113.0.203.IN-ADDR.ARPA/IN: loaded
28-Jun-2013 13:20:07.435 zone_settimer: zone 113.0.203.IN-ADDR.ARPA/IN: enter
28-Jun-2013 13:20:07.435 zone 255.255.255.255.IN-ADDR.ARPA/IN: starting load
28-Jun-2013 13:20:07.435 zone 255.255.255.255.IN-ADDR.ARPA/IN: number of nodes in database: 0
28-Jun-2013 13:20:07.435 zone 255.255.255.255.IN-ADDR.ARPA/IN: loaded
28-Jun-2013 13:20:07.435 zone_settimer: zone 255.255.255.255.IN-ADDR.ARPA/IN: enter
28-Jun-2013 13:20:07.435 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/IN: starting load

… Teile entfernt


28-Jun-2013 13:20:12.455 soa_query: zone digitronic-berlin.de/IN: enter
28-Jun-2013 13:20:12.456 dns_request_createvia
28-Jun-2013 13:20:12.456 request_render
28-Jun-2013 13:20:12.456 requestmgr_attach: 0xb6ddf508: eref 1 iref 1
28-Jun-2013 13:20:12.456 mgr_gethash
28-Jun-2013 13:20:12.456 req_send: request 0xb6deff08
28-Jun-2013 13:20:12.456 dns_request_createvia: request 0xb6deff08
28-Jun-2013 13:20:12.456 req_senddone: request 0xb6deff08
28-Jun-2013 13:20:12.456 zone_timer: zone A.E.F.IP6.ARPA/IN: enter
28-Jun-2013 13:20:12.456 zone_maintenance: zone A.E.F.IP6.ARPA/IN: enter
28-Jun-2013 13:20:12.456 zone_settimer: zone A.E.F.IP6.ARPA/IN: enter
28-Jun-2013 13:20:12.456 zone_settimer: zone A.E.F.IP6.ARPA/IN: settimer inactive
28-Jun-2013 13:20:12.456 zone_timer: zone 8.B.D.0.1.0.0.2.IP6.ARPA/IN: enter
28-Jun-2013 13:20:12.456 zone_maintenance: zone 8.B.D.0.1.0.0.2.IP6.ARPA/IN: enter
28-Jun-2013 13:20:12.456 zone_settimer: zone 8.B.D.0.1.0.0.2.IP6.ARPA/IN: enter
28-Jun-2013 13:20:12.456 zone_settimer: zone 8.B.D.0.1.0.0.2.IP6.ARPA/IN: settimer inactive
28-Jun-2013 13:20:12.456 running
28-Jun-2013 13:20:12.456 client 127.0.0.1#53828: UDP request
28-Jun-2013 13:20:12.456 client 127.0.0.1#53828: using view ‘_default’
28-Jun-2013 13:20:12.456 client 127.0.0.1#53828: request is not signed
28-Jun-2013 13:20:12.456 client 127.0.0.1#53828: recursion available
28-Jun-2013 13:20:12.456 client 127.0.0.1#53828: query
28-Jun-2013 13:20:12.456 client 127.0.0.1#53828: ns_client_attach: ref = 1
28-Jun-2013 13:20:12.456 client 127.0.0.1#53828: query failed (SERVFAIL) for digitronic-berlin.de/IN/SOA at query.c:5193
28-Jun-2013 13:20:12.456 client 127.0.0.1#53828: error
28-Jun-2013 13:20:12.456 client 127.0.0.1#53828: send
28-Jun-2013 13:20:12.456 client 127.0.0.1#53828: sendto
28-Jun-2013 13:20:12.456 client 127.0.0.1#53828: senddone
28-Jun-2013 13:20:12.456 client 127.0.0.1#53828: next
28-Jun-2013 13:20:12.456 client 127.0.0.1#53828: ns_client_detach: ref = 0
28-Jun-2013 13:20:12.456 client 127.0.0.1#53828: endrequest
28-Jun-2013 13:20:12.456 req_response: request 0xb6deff08: success
28-Jun-2013 13:20:12.456 client @0xb4c07008: udprecv
28-Jun-2013 13:20:12.456 req_cancel: request 0xb6deff08
28-Jun-2013 13:20:12.456 req_sendevent: request 0xb6deff08
28-Jun-2013 13:20:12.456 refresh_callback: zone digitronic-berlin.de/IN: enter
28-Jun-2013 13:20:12.456 dns_request_getresponse: request 0xb6deff08
28-Jun-2013 13:20:12.456 zone digitronic-berlin.de/IN: refresh: rcode (SERVFAIL) retrying without EDNS master 127.0.0.1#7777 (source 0.0.0.0#0)
28-Jun-2013 13:20:12.456 dns_request_destroy: request 0xb6deff08
28-Jun-2013 13:20:12.457 req_destroy: request 0xb6deff08
28-Jun-2013 13:20:12.457 requestmgr_detach: 0xb6ddf508: eref 1 iref 0
28-Jun-2013 13:20:12.457 queue_soa_query: zone digitronic-berlin.de/IN: enter
28-Jun-2013 13:20:12.955 soa_query: zone 88.168.192.in-addr.arpa/IN: enter
28-Jun-2013 13:20:12.955 dns_request_createvia
28-Jun-2013 13:20:12.955 request_render
28-Jun-2013 13:20:12.955 requestmgr_attach: 0xb6ddf508: eref 1 iref 1
28-Jun-2013 13:20:12.955 mgr_gethash
28-Jun-2013 13:20:12.955 req_send: request 0xb6deff08
28-Jun-2013 13:20:12.955 dns_request_createvia: request 0xb6deff08
28-Jun-2013 13:20:12.955 soa_query: zone digitronic-berlin.de/IN: enter
28-Jun-2013 13:20:12.955 dns_request_createvia
28-Jun-2013 13:20:12.955 request_render
28-Jun-2013 13:20:12.955 requestmgr_attach: 0xb6ddf508: eref 1 iref 2
28-Jun-2013 13:20:12.955 mgr_gethash
28-Jun-2013 13:20:12.955 req_send: request 0xb6defe18
28-Jun-2013 13:20:12.955 dns_request_createvia: request 0xb6defe18
28-Jun-2013 13:20:12.955 req_senddone: request 0xb6deff08
28-Jun-2013 13:20:12.955 req_senddone: request 0xb6defe18
28-Jun-2013 13:20:12.955 client 127.0.0.1#22623: UDP request
28-Jun-2013 13:20:12.955 client 127.0.0.1#22623: UDP request
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: using view ‘_default’
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: request is not signed
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: recursion available
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: query
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: ns_client_attach: ref = 1
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: query failed (SERVFAIL) for digitronic-berlin.de/IN/SOA at query.c:5193
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: error
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: send
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: sendto
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: senddone
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: next
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: ns_client_detach: ref = 0
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: endrequest
28-Jun-2013 13:20:12.956 client @0xb4c07008: udprecv
28-Jun-2013 13:20:12.956 req_response: request 0xb6defe18: success
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: using view ‘_default’
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: request is not signed
28-Jun-2013 13:20:12.956 req_cancel: request 0xb6defe18
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: recursion available
28-Jun-2013 13:20:12.956 req_sendevent: request 0xb6defe18
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: query
28-Jun-2013 13:20:12.956 refresh_callback: zone digitronic-berlin.de/IN: enter
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: ns_client_attach: ref = 1
28-Jun-2013 13:20:12.956 dns_request_getresponse: request 0xb6defe18
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: query failed (SERVFAIL) for 88.168.192.in-addr.arpa/IN/SOA at query.c:5193
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: error
28-Jun-2013 13:20:12.956 zone digitronic-berlin.de/IN: refresh: unexpected rcode (SERVFAIL) from master 127.0.0.1#7777 (source 0.0.0.0#0)
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: send
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: sendto
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: senddone
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: next
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: ns_client_detach: ref = 0
28-Jun-2013 13:20:12.956 client 127.0.0.1#22623: endrequest
28-Jun-2013 13:20:12.956 client @0xb4bc6008: udprecv
28-Jun-2013 13:20:12.956 dns_request_destroy: request 0xb6defe18
28-Jun-2013 13:20:12.956 req_destroy: request 0xb6defe18
28-Jun-2013 13:20:12.956 requestmgr_detach: 0xb6ddf508: eref 1 iref 1
28-Jun-2013 13:20:12.956 queue_soa_query: zone digitronic-berlin.de/IN: enter
28-Jun-2013 13:20:12.956 soa_query: zone digitronic-berlin.de/IN: enter
28-Jun-2013 13:20:12.956 cancel_refresh: zone digitronic-berlin.de/IN: enter
28-Jun-2013 13:20:12.956 zone_settimer: zone digitronic-berlin.de/IN: enter
28-Jun-2013 13:20:12.956 req_response: request 0xb6deff08: success
28-Jun-2013 13:20:12.956 req_cancel: request 0xb6deff08
28-Jun-2013 13:20:12.956 req_sendevent: request 0xb6deff08
28-Jun-2013 13:20:12.956 refresh_callback: zone 88.168.192.in-addr.arpa/IN: enter
28-Jun-2013 13:20:12.956 dns_request_getresponse: request 0xb6deff08
28-Jun-2013 13:20:12.956 zone 88.168.192.in-addr.arpa/IN: refresh: rcode (SERVFAIL) retrying without EDNS master 127.0.0.1#7777 (source 0.0.0.0#0)
28-Jun-2013 13:20:12.957 dns_request_destroy: request 0xb6deff08
28-Jun-2013 13:20:12.957 req_destroy: request 0xb6deff08
28-Jun-2013 13:20:12.957 requestmgr_detach: 0xb6ddf508: eref 1 iref 0
28-Jun-2013 13:20:12.957 queue_soa_query: zone 88.168.192.in-addr.arpa/IN: enter
28-Jun-2013 13:20:13.456 soa_query: zone 88.168.192.in-addr.arpa/IN: enter
28-Jun-2013 13:20:13.456 dns_request_createvia
28-Jun-2013 13:20:13.457 request_render
28-Jun-2013 13:20:13.457 requestmgr_attach: 0xb6ddf508: eref 1 iref 1
28-Jun-2013 13:20:13.457 mgr_gethash
28-Jun-2013 13:20:13.457 req_send: request 0xb6deff08
28-Jun-2013 13:20:13.457 dns_request_createvia: request 0xb6deff08
28-Jun-2013 13:20:13.457 req_senddone: request 0xb6deff08
28-Jun-2013 13:20:13.457 client 127.0.0.1#60841: UDP request
28-Jun-2013 13:20:13.457 client 127.0.0.1#60841: using view ‘_default’
28-Jun-2013 13:20:13.457 client 127.0.0.1#60841: request is not signed
28-Jun-2013 13:20:13.457 client 127.0.0.1#60841: recursion available
28-Jun-2013 13:20:13.457 client 127.0.0.1#60841: query
28-Jun-2013 13:20:13.457 client 127.0.0.1#60841: ns_client_attach: ref = 1
28-Jun-2013 13:20:13.457 client 127.0.0.1#60841: query failed (SERVFAIL) for 88.168.192.in-addr.arpa/IN/SOA at query.c:5193
28-Jun-2013 13:20:13.457 client 127.0.0.1#60841: error
28-Jun-2013 13:20:13.457 client 127.0.0.1#60841: send
28-Jun-2013 13:20:13.457 client 127.0.0.1#60841: sendto
28-Jun-2013 13:20:13.457 client 127.0.0.1#60841: senddone
28-Jun-2013 13:20:13.457 client 127.0.0.1#60841: next
28-Jun-2013 13:20:13.457 client 127.0.0.1#60841: ns_client_detach: ref = 0
28-Jun-2013 13:20:13.457 client 127.0.0.1#60841: endrequest
28-Jun-2013 13:20:13.457 client @0xb4c07008: udprecv
28-Jun-2013 13:20:13.457 req_response: request 0xb6deff08: success
28-Jun-2013 13:20:13.457 req_cancel: request 0xb6deff08
28-Jun-2013 13:20:13.457 req_sendevent: request 0xb6deff08
28-Jun-2013 13:20:13.457 refresh_callback: zone 88.168.192.in-addr.arpa/IN: enter
28-Jun-2013 13:20:13.457 dns_request_getresponse: request 0xb6deff08
28-Jun-2013 13:20:13.457 zone 88.168.192.in-addr.arpa/IN: refresh: unexpected rcode (SERVFAIL) from master 127.0.0.1#7777 (source 0.0.0.0#0)
28-Jun-2013 13:20:13.457 dns_request_destroy: request 0xb6deff08
28-Jun-2013 13:20:13.457 req_destroy: request 0xb6deff08
28-Jun-2013 13:20:13.457 requestmgr_detach: 0xb6ddf508: eref 1 iref 0
28-Jun-2013 13:20:13.457 queue_soa_query: zone 88.168.192.in-addr.arpa/IN: enter
28-Jun-2013 13:20:13.457 soa_query: zone 88.168.192.in-addr.arpa/IN: enter
28-Jun-2013 13:20:13.457 cancel_refresh: zone 88.168.192.in-addr.arpa/IN: enter
28-Jun-2013 13:20:13.457 zone_settimer: zone 88.168.192.in-addr.arpa/IN: enter
28-Jun-2013 13:21:06.455 zone_timer: zone digitronic-berlin.de/IN: enter
28-Jun-2013 13:21:06.455 zone_maintenance: zone digitronic-berlin.de/IN: enter
28-Jun-2013 13:21:06.455 queue_soa_query: zone digitronic-berlin.de/IN: enter
28-Jun-2013 13:21:06.455 zone_settimer: zone digitronic-berlin.de/IN: enter
28-Jun-2013 13:21:06.455 zone_settimer: zone digitronic-berlin.de/IN: settimer inactive
28-Jun-2013 13:21:06.455 soa_query: zone digitronic-berlin.de/IN: enter
28-Jun-2013 13:21:06.455 dns_request_createvia
28-Jun-2013 13:21:06.455 request_render
28-Jun-2013 13:21:06.455 requestmgr_attach: 0xb6ddf508: eref 1 iref 1
28-Jun-2013 13:21:06.455 mgr_gethash
28-Jun-2013 13:21:06.455 req_send: request 0xb6deff08
28-Jun-2013 13:21:06.455 dns_request_createvia: request 0xb6deff08
28-Jun-2013 13:21:06.455 req_senddone: request 0xb6deff08
28-Jun-2013 13:21:06.455 client 127.0.0.1#41829: UDP request
28-Jun-2013 13:21:06.455 client 127.0.0.1#41829: using view ‘_default’
28-Jun-2013 13:21:06.455 client 127.0.0.1#41829: request is not signed
28-Jun-2013 13:21:06.455 client 127.0.0.1#41829: recursion available
28-Jun-2013 13:21:06.455 client 127.0.0.1#41829: query
28-Jun-2013 13:21:06.455 client 127.0.0.1#41829: ns_client_attach: ref = 1
28-Jun-2013 13:21:06.456 client 127.0.0.1#41829: query failed (SERVFAIL) for digitronic-berlin.de/IN/SOA at query.c:5193
28-Jun-2013 13:21:06.456 client 127.0.0.1#41829: error
28-Jun-2013 13:21:06.456 client 127.0.0.1#41829: send
28-Jun-2013 13:21:06.456 client 127.0.0.1#41829: sendto
28-Jun-2013 13:21:06.456 client 127.0.0.1#41829: senddone
28-Jun-2013 13:21:06.456 client 127.0.0.1#41829: next
28-Jun-2013 13:21:06.456 client 127.0.0.1#41829: ns_client_detach: ref = 0
28-Jun-2013 13:21:06.456 client 127.0.0.1#41829: endrequest
28-Jun-2013 13:21:06.456 req_response: request 0xb6deff08: success
28-Jun-2013 13:21:06.456 client @0xb4bc6008: udprecv
28-Jun-2013 13:21:06.456 req_cancel: request 0xb6deff08
28-Jun-2013 13:21:06.456 req_sendevent: request 0xb6deff08
28-Jun-2013 13:21:06.456 refresh_callback: zone digitronic-berlin.de/IN: enter
28-Jun-2013 13:21:06.456 dns_request_getresponse: request 0xb6deff08
28-Jun-2013 13:21:06.456 zone digitronic-berlin.de/IN: refresh: rcode (SERVFAIL) retrying without EDNS master 127.0.0.1#7777 (source 0.0.0.0#0)
28-Jun-2013 13:21:06.456 dns_request_destroy: request 0xb6deff08
28-Jun-2013 13:21:06.456 req_destroy: request 0xb6deff08
28-Jun-2013 13:21:06.456 requestmgr_detach: 0xb6ddf508: eref 1 iref 0
28-Jun-2013 13:21:06.456 queue_soa_query: zone digitronic-berlin.de/IN: enter
28-Jun-2013 13:21:06.955 soa_query: zone digitronic-berlin.de/IN: enter
28-Jun-2013 13:21:06.955 dns_request_createvia
28-Jun-2013 13:21:06.955 request_render
28-Jun-2013 13:21:06.955 requestmgr_attach: 0xb6ddf508: eref 1 iref 1
28-Jun-2013 13:21:06.955 mgr_gethash
28-Jun-2013 13:21:06.955 req_send: request 0xb4ad10f8
28-Jun-2013 13:21:06.955 dns_request_createvia: request 0xb4ad10f8
28-Jun-2013 13:21:06.955 req_senddone: request 0xb4ad10f8
28-Jun-2013 13:21:06.956 client 127.0.0.1#7563: UDP request
28-Jun-2013 13:21:06.956 client 127.0.0.1#7563: using view ‘_default’
28-Jun-2013 13:21:06.956 client 127.0.0.1#7563: request is not signed
28-Jun-2013 13:21:06.956 client 127.0.0.1#7563: recursion available
28-Jun-2013 13:21:06.956 client 127.0.0.1#7563: query
28-Jun-2013 13:21:06.956 client 127.0.0.1#7563: ns_client_attach: ref = 1
28-Jun-2013 13:21:06.956 client 127.0.0.1#7563: query failed (SERVFAIL) for digitronic-berlin.de/IN/SOA at query.c:5193
28-Jun-2013 13:21:06.956 client 127.0.0.1#7563: error
28-Jun-2013 13:21:06.956 client 127.0.0.1#7563: send
28-Jun-2013 13:21:06.956 client 127.0.0.1#7563: sendto
28-Jun-2013 13:21:06.956 client 127.0.0.1#7563: senddone
28-Jun-2013 13:21:06.956 client 127.0.0.1#7563: next
28-Jun-2013 13:21:06.956 client 127.0.0.1#7563: ns_client_detach: ref = 0
28-Jun-2013 13:21:06.956 req_response: request 0xb4ad10f8: success
28-Jun-2013 13:21:06.956 client 127.0.0.1#7563: endrequest
28-Jun-2013 13:21:06.956 req_cancel: request 0xb4ad10f8
28-Jun-2013 13:21:06.956 client @0xb4c07008: udprecv
28-Jun-2013 13:21:06.956 req_sendevent: request 0xb4ad10f8
28-Jun-2013 13:21:06.956 refresh_callback: zone digitronic-berlin.de/IN: enter
28-Jun-2013 13:21:06.956 dns_request_getresponse: request 0xb4ad10f8
28-Jun-2013 13:21:06.956 zone digitronic-berlin.de/IN: refresh: unexpected rcode (SERVFAIL) from master 127.0.0.1#7777 (source 0.0.0.0#0)
28-Jun-2013 13:21:06.956 dns_request_destroy: request 0xb4ad10f8
28-Jun-2013 13:21:06.956 req_destroy: request 0xb4ad10f8
28-Jun-2013 13:21:06.956 requestmgr_detach: 0xb6ddf508: eref 1 iref 0
28-Jun-2013 13:21:06.956 queue_soa_query: zone digitronic-berlin.de/IN: enter
28-Jun-2013 13:21:06.956 soa_query: zone digitronic-berlin.de/IN: enter
28-Jun-2013 13:21:06.956 cancel_refresh: zone digitronic-berlin.de/IN: enter
28-Jun-2013 13:21:06.956 zone_settimer: zone digitronic-berlin.de/IN: enter
28-Jun-2013 13:21:09.455 zone_timer: zone 88.168.192.in-addr.arpa/IN: enter
28-Jun-2013 13:21:09.455 zone_maintenance: zone 88.168.192.in-addr.arpa/IN: enter
28-Jun-2013 13:21:09.455 queue_soa_query: zone 88.168.192.in-addr.arpa/IN: enter
28-Jun-2013 13:21:09.455 zone_settimer: zone 88.168.192.in-addr.arpa/IN: enter
28-Jun-2013 13:21:09.455 zone_settimer: zone 88.168.192.in-addr.arpa/IN: settimer inactive
28-Jun-2013 13:21:09.455 soa_query: zone 88.168.192.in-addr.arpa/IN: enter
28-Jun-2013 13:21:09.455 dns_request_createvia
28-Jun-2013 13:21:09.456 request_render
28-Jun-2013 13:21:09.456 requestmgr_attach: 0xb6ddf508: eref 1 iref 1
28-Jun-2013 13:21:09.456 mgr_gethash
28-Jun-2013 13:21:09.456 req_send: request 0xb6deff08
28-Jun-2013 13:21:09.456 dns_request_createvia: request 0xb6deff08
28-Jun-2013 13:21:09.456 req_senddone: request 0xb6deff08
28-Jun-2013 13:21:09.456 client 127.0.0.1#11363: UDP request
28-Jun-2013 13:21:09.456 client 127.0.0.1#11363: using view ‘_default’
28-Jun-2013 13:21:09.456 client 127.0.0.1#11363: request is not signed
28-Jun-2013 13:21:09.456 client 127.0.0.1#11363: recursion available
28-Jun-2013 13:21:09.456 client 127.0.0.1#11363: query
28-Jun-2013 13:21:09.456 client 127.0.0.1#11363: ns_client_attach: ref = 1
28-Jun-2013 13:21:09.456 client 127.0.0.1#11363: query failed (SERVFAIL) for 88.168.192.in-addr.arpa/IN/SOA at query.c:5193
28-Jun-2013 13:21:09.456 client 127.0.0.1#11363: error
28-Jun-2013 13:21:09.456 client 127.0.0.1#11363: send
28-Jun-2013 13:21:09.456 client 127.0.0.1#11363: sendto
28-Jun-2013 13:21:09.456 client 127.0.0.1#11363: senddone
28-Jun-2013 13:21:09.456 client 127.0.0.1#11363: next
28-Jun-2013 13:21:09.456 client 127.0.0.1#11363: ns_client_detach: ref = 0
28-Jun-2013 13:21:09.456 client 127.0.0.1#11363: endrequest
28-Jun-2013 13:21:09.456 client @0xb4bc6008: udprecv
28-Jun-2013 13:21:09.456 req_response: request 0xb6deff08: success
28-Jun-2013 13:21:09.456 req_cancel: request 0xb6deff08
28-Jun-2013 13:21:09.456 req_sendevent: request 0xb6deff08
28-Jun-2013 13:21:09.456 refresh_callback: zone 88.168.192.in-addr.arpa/IN: enter
28-Jun-2013 13:21:09.456 dns_request_getresponse: request 0xb6deff08
28-Jun-2013 13:21:09.456 zone 88.168.192.in-addr.arpa/IN: refresh: rcode (SERVFAIL) retrying without EDNS master 127.0.0.1#7777 (source 0.0.0.0#0)
28-Jun-2013 13:21:09.456 dns_request_destroy: request 0xb6deff08
28-Jun-2013 13:21:09.456 req_destroy: request 0xb6deff08
28-Jun-2013 13:21:09.456 requestmgr_detach: 0xb6ddf508: eref 1 iref 0
28-Jun-2013 13:21:09.456 queue_soa_query: zone 88.168.192.in-addr.arpa/IN: enter
28-Jun-2013 13:21:09.955 soa_query: zone 88.168.192.in-addr.arpa/IN: enter
28-Jun-2013 13:21:09.956 dns_request_createvia
28-Jun-2013 13:21:09.956 request_render
28-Jun-2013 13:21:09.956 requestmgr_attach: 0xb6ddf508: eref 1 iref 1
28-Jun-2013 13:21:09.956 mgr_gethash
28-Jun-2013 13:21:09.956 req_send: request 0xb4ad13c8
28-Jun-2013 13:21:09.956 dns_request_createvia: request 0xb4ad13c8
28-Jun-2013 13:21:09.956 req_senddone: request 0xb4ad13c8
28-Jun-2013 13:21:09.956 client 127.0.0.1#61363: UDP request
28-Jun-2013 13:21:09.956 client 127.0.0.1#61363: using view ‘_default’
28-Jun-2013 13:21:09.956 client 127.0.0.1#61363: request is not signed
28-Jun-2013 13:21:09.956 client 127.0.0.1#61363: recursion available
28-Jun-2013 13:21:09.956 client 127.0.0.1#61363: query
28-Jun-2013 13:21:09.956 client 127.0.0.1#61363: ns_client_attach: ref = 1
28-Jun-2013 13:21:09.956 client 127.0.0.1#61363: query failed (SERVFAIL) for 88.168.192.in-addr.arpa/IN/SOA at query.c:5193
28-Jun-2013 13:21:09.956 client 127.0.0.1#61363: error
28-Jun-2013 13:21:09.956 client 127.0.0.1#61363: send
28-Jun-2013 13:21:09.956 client 127.0.0.1#61363: sendto
28-Jun-2013 13:21:09.956 client 127.0.0.1#61363: senddone
28-Jun-2013 13:21:09.956 client 127.0.0.1#61363: next
28-Jun-2013 13:21:09.956 client 127.0.0.1#61363: ns_client_detach: ref = 0
28-Jun-2013 13:21:09.956 req_response: request 0xb4ad13c8: success
28-Jun-2013 13:21:09.956 client 127.0.0.1#61363: endrequest
28-Jun-2013 13:21:09.956 req_cancel: request 0xb4ad13c8
28-Jun-2013 13:21:09.956 client @0xb4c07008: udprecv
28-Jun-2013 13:21:09.956 req_sendevent: request 0xb4ad13c8
28-Jun-2013 13:21:09.956 refresh_callback: zone 88.168.192.in-addr.arpa/IN: enter
28-Jun-2013 13:21:09.956 dns_request_getresponse: request 0xb4ad13c8
28-Jun-2013 13:21:09.956 zone 88.168.192.in-addr.arpa/IN: refresh: unexpected rcode (SERVFAIL) from master 127.0.0.1#7777 (source 0.0.0.0#0)
28-Jun-2013 13:21:09.957 dns_request_destroy: request 0xb4ad13c8
28-Jun-2013 13:21:09.957 req_destroy: request 0xb4ad13c8
28-Jun-2013 13:21:09.957 requestmgr_detach: 0xb6ddf508: eref 1 iref 0
28-Jun-2013 13:21:09.957 queue_soa_query: zone 88.168.192.in-addr.arpa/IN: enter
28-Jun-2013 13:21:09.957 soa_query: zone 88.168.192.in-addr.arpa/IN: enter
28-Jun-2013 13:21:09.957 cancel_refresh: zone 88.168.192.in-addr.arpa/IN: enter
28-Jun-2013 13:21:09.957 zone_settimer: zone 88.168.192.in-addr.arpa/IN: enter

[/code]

; <<>> DiG 9.8.0-P4 <<>> @127.0.0.1 -p7777 digitronic-berlin.de axfr
; (1 server found)
;; global options: +cmd
; Transfer failed.

univention-ldapsearch -xLLL -b cn=dns,$(ucr get ldap/base)

[code]dn: cn=dns,dc=digitronic-berlin,dc=de
description: Containing all DNS Objects as per default Settings
cn: dns
objectClass: organizationalRole
objectClass: univentionObject
univentionObjectType: container/cn

dn: zoneName=digitronic-berlin.de,cn=dns,dc=digitronic-berlin,dc=de
dNSTTL: 10800
relativeDomainName: @
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/forward_zone
aRecord: 192.168.88.228
nSRecord: janus.digitronic-berlin.de.
sOARecord: janus.digitronic-berlin.de. root.digitronic-berlin.de. 67 28800 720
0 604800 10800

dn: relativeDomainName=janus,zoneName=digitronic-berlin.de,cn=dns,dc=digitroni
c-berlin,dc=de
aRecord: 192.168.88.228
relativeDomainName: janus
dNSTTL: 80600
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitronic-berlin,dc=de
nSRecord: janus.digitronic-berlin.de.
dNSTTL: 10800
relativeDomainName: @
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/reverse_zone
sOARecord: janus.digitronic-berlin.de. root.digitronic-berlin.de. 36 28800 720
0 604800 10800

dn: relativeDomainName=228,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 228
pTRRecord: janus.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=_ldap._tcp,zoneName=digitronic-berlin.de,cn=dns,dc=digi
tronic-berlin,dc=de
relativeDomainName: _ldap._tcp
dNSTTL: 10800
zoneName: digitronic-berlin.de
sRVRecord: 0 100 389 janus.digitronic-berlin.de.
sRVRecord: 0 100 7389 janus.digitronic-berlin.de.
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/srv_record

dn: relativeDomainName=_domaincontroller_master._tcp,zoneName=digitronic-berli
n.de,cn=dns,dc=digitronic-berlin,dc=de
relativeDomainName: _domaincontroller_master._tcp
sRVRecord: 0 0 0 janus.digitronic-berlin.de.
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/srv_record

dn: relativeDomainName=_kerberos,zoneName=digitronic-berlin.de,cn=dns,dc=digit
ronic-berlin,dc=de
relativeDomainName: _kerberos
dNSTTL: 80600
tXTRecord: DIGITRONIC-BERLIN.DE
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/txt_record

dn: relativeDomainName=_kerberos._tcp,zoneName=digitronic-berlin.de,cn=dns,dc=
digitronic-berlin,dc=de
relativeDomainName: _kerberos._tcp
dNSTTL: 10800
zoneName: digitronic-berlin.de
sRVRecord: 0 100 88 janus.digitronic-berlin.de.
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/srv_record

dn: relativeDomainName=_kerberos._udp,zoneName=digitronic-berlin.de,cn=dns,dc=
digitronic-berlin,dc=de
relativeDomainName: _kerberos._udp
dNSTTL: 10800
zoneName: digitronic-berlin.de
sRVRecord: 0 100 88 janus.digitronic-berlin.de.
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/srv_record

dn: relativeDomainName=_kerberos-adm._tcp,zoneName=digitronic-berlin.de,cn=dns
,dc=digitronic-berlin,dc=de
relativeDomainName: _kerberos-adm._tcp
dNSTTL: 10800
zoneName: digitronic-berlin.de
sRVRecord: 0 100 88 janus.digitronic-berlin.de.
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/srv_record

dn: relativeDomainName=univention-directory-manager,zoneName=digitronic-berlin
.de,cn=dns,dc=digitronic-berlin,dc=de
relativeDomainName: univention-directory-manager
dNSTTL: 80600
cNAMERecord: janus
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/alias

dn: relativeDomainName=rhea,zoneName=digitronic-berlin.de,cn=dns,dc=digitronic
-berlin,dc=de
aRecord: 192.168.88.231
relativeDomainName: rhea
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=dione,zoneName=digitronic-berlin.de,cn=dns,dc=digitroni
c-berlin,dc=de
aRecord: 192.168.88.232
relativeDomainName: dione
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=callisto,zoneName=digitronic-berlin.de,cn=dns,dc=digitr
onic-berlin,dc=de
aRecord: 192.168.88.230
relativeDomainName: callisto
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=ganymed,zoneName=digitronic-berlin.de,cn=dns,dc=digitro
nic-berlin,dc=de
aRecord: 192.168.88.233
relativeDomainName: ganymed
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=jupiter,zoneName=digitronic-berlin.de,cn=dns,dc=digitro
nic-berlin,dc=de
aRecord: 192.168.88.234
relativeDomainName: jupiter
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=atlas,zoneName=digitronic-berlin.de,cn=dns,dc=digitroni
c-berlin,dc=de
aRecord: 192.168.77.227
relativeDomainName: atlas
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=uranus,zoneName=digitronic-berlin.de,cn=dns,dc=digitron
ic-berlin,dc=de
aRecord: 192.168.88.225
relativeDomainName: uranus
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=saturn,zoneName=digitronic-berlin.de,cn=dns,dc=digitron
ic-berlin,dc=de
aRecord: 192.168.88.226
relativeDomainName: saturn
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=titan,zoneName=digitronic-berlin.de,cn=dns,dc=digitroni
c-berlin,dc=de
aRecord: 192.168.88.229
relativeDomainName: titan
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=europa,zoneName=digitronic-berlin.de,cn=dns,dc=digitron
ic-berlin,dc=de
aRecord: 192.168.88.236
relativeDomainName: europa
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=merkur,zoneName=digitronic-berlin.de,cn=dns,dc=digitron
ic-berlin,dc=de
aRecord: 192.168.88.237
relativeDomainName: merkur
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=io,zoneName=digitronic-berlin.de,cn=dns,dc=digitronic-b
erlin,dc=de
aRecord: 192.168.88.238
relativeDomainName: io
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=mimas,zoneName=digitronic-berlin.de,cn=dns,dc=digitroni
c-berlin,dc=de
aRecord: 192.168.88.239
relativeDomainName: mimas
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=venus,zoneName=digitronic-berlin.de,cn=dns,dc=digitroni
c-berlin,dc=de
aRecord: 192.168.88.242
relativeDomainName: venus
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=neptun,zoneName=digitronic-berlin.de,cn=dns,dc=digitron
ic-berlin,dc=de
aRecord: 192.168.88.244
relativeDomainName: neptun
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=samsung,zoneName=digitronic-berlin.de,cn=dns,dc=digitro
nic-berlin,dc=de
aRecord: 192.168.88.249
relativeDomainName: samsung
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=elmeg,zoneName=digitronic-berlin.de,cn=dns,dc=digitroni
c-berlin,dc=de
aRecord: 192.168.88.250
relativeDomainName: elmeg
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=r1200,zoneName=digitronic-berlin.de,cn=dns,dc=digitroni
c-berlin,dc=de
aRecord: 192.168.88.253
relativeDomainName: r1200
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=r3000,zoneName=digitronic-berlin.de,cn=dns,dc=digitroni
c-berlin,dc=de
aRecord: 192.168.88.254
relativeDomainName: r3000
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=thetsys,zoneName=digitronic-berlin.de,cn=dns,dc=digitro
nic-berlin,dc=de
aRecord: 192.168.88.246
relativeDomainName: thetsys
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=233,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 233
pTRRecord: ganymed.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=234,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 234
pTRRecord: jupiter.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=222,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 222
pTRRecord: phobos.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=223,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 223
pTRRecord: proteus.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=224,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 224
pTRRecord: triton.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=225,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 225
pTRRecord: uranus.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=226,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 226
pTRRecord: saturn.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=227,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 227
pTRRecord: atlas2.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=229,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 229
pTRRecord: titan.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=230,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 230
pTRRecord: callisto.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=231,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 231
pTRRecord: rhea.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=232,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 232
pTRRecord: dione.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=236,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 236
pTRRecord: europa.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=237,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 237
pTRRecord: merkur.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=238,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 238
pTRRecord: io.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=239,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 239
pTRRecord: mimas.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=242,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 242
pTRRecord: venus.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=243,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 243
pTRRecord: pluto2.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=244,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 244
pTRRecord: neptun.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=245,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 245
pTRRecord: mars2.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=246,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 246
pTRRecord: thetsys.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=248,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 248
pTRRecord: dell.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=249,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 249
pTRRecord: samsung.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=250,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 250
pTRRecord: elmeg.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=253,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 253
pTRRecord: r1200.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=254,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 254
pTRRecord: r3000.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=sip,zoneName=digitronic-berlin.de,cn=dns,dc=digitronic-
berlin,dc=de
relativeDomainName: sip
dNSTTL: 10800
cNAMERecord: elmeg
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/alias

dn: relativeDomainName=deimos,zoneName=digitronic-berlin.de,cn=dns,dc=digitron
ic-berlin,dc=de
aRecord: 192.168.88.251
relativeDomainName: deimos
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=251,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 251
pTRRecord: deimos.digitronic-berlin.de
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=proteus,zoneName=digitronic-berlin.de,cn=dns,dc=digitro
nic-berlin,dc=de
aRecord: 192.168.88.223
relativeDomainName: proteus
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=triton,zoneName=digitronic-berlin.de,cn=dns,dc=digitron
ic-berlin,dc=de
aRecord: 192.168.88.224
relativeDomainName: triton
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=phobos,zoneName=digitronic-berlin.de,cn=dns,dc=digitron
ic-berlin,dc=de
aRecord: 192.168.88.222
relativeDomainName: phobos
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=www,zoneName=digitronic-berlin.de,cn=dns,dc=digitronic-
berlin,dc=de
relativeDomainName: www
dNSTTL: 10800
zoneName: digitronic-berlin.de
aRecord: 85.13.129.163
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=dsl1,zoneName=digitronic-berlin.de,cn=dns,dc=digitronic
-berlin,dc=de
aRecord: 217.91.183.5
relativeDomainName: dsl1
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=dsl2,zoneName=digitronic-berlin.de,cn=dns,dc=digitronic
-berlin,dc=de
aRecord: 217.91.178.94
relativeDomainName: dsl2
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=rt4402,zoneName=digitronic-berlin.de,cn=dns,dc=digitron
ic-berlin,dc=de
aRecord: 192.168.88.153
relativeDomainName: rt4402
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=ariel,zoneName=digitronic-berlin.de,cn=dns,dc=digitroni
c-berlin,dc=de
aRecord: 192.168.88.151
relativeDomainName: ariel
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=hybird,zoneName=digitronic-berlin.de,cn=dns,dc=digitron
ic-berlin,dc=de
aRecord: 192.168.88.252
relativeDomainName: hybird
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=252,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 252
pTRRecord: hybird.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=151,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 151
pTRRecord: arial.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=dell,zoneName=digitronic-berlin.de,cn=dns,dc=digitronic
-berlin,dc=de
aRecord: 192.168.88.248
relativeDomainName: dell
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=larissa,zoneName=digitronic-berlin.de,cn=dns,dc=digitro
nic-berlin,dc=de
aRecord: 192.168.88.221
relativeDomainName: larissa
dNSTTL: 10800
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record

dn: relativeDomainName=221,zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitron
ic-berlin,dc=de
relativeDomainName: 221
pTRRecord: larissa.digitronic-berlin.de.
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/ptr_record

dn: relativeDomainName=mars,zoneName=digitronic-berlin.de,cn=dns,dc=digitronic
-berlin,dc=de
aRecord: 192.168.88.245
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record
dNSTTL: 10800
relativeDomainName: mars
zoneName: digitronic-berlin.de

[/code]

Immer noch ratlos!

Viele Grüße
Hans-Jürgen Wegerich


#8

Hallo,

ich habe die Daten aus Ihrem LDAP in ein Testsystem eingespielt und konnte das Verhalten dort nicht beobachten, die Informationen sind also generell konsistent.
Auffällig sind denke ich die folgenden Meldungen aus Ihrem ersten Post:Jun 3 18:15:33 janus named[10109]: zone 88.168.192.in-addr.arpa/IN: could not find NS and/or SOA records Jun 3 18:15:33 janus named[10109]: zone 88.168.192.in-addr.arpa/IN: has 0 SOA records Jun 3 18:15:33 janus named[10109]: zone 88.168.192.in-addr.arpa/IN: has no NS records Jun 3 18:15:33 janus named[10109]: zone 88.168.192.in-addr.arpa/IN: not loaded due to errors. Jun 3 18:15:33 janus named[10109]: zone digitronic-berlin.de/IN: could not find NS and/or SOA records Jun 3 18:15:33 janus named[10109]: zone digitronic-berlin.de/IN: has 0 SOA records Jun 3 18:15:33 janus named[10109]: zone digitronic-berlin.de/IN: has no NS records Jun 3 18:15:33 janus named[10109]: zone digitronic-berlin.de/IN: not loaded due to errors.

Dies deckt sich nicht mit der Ausgabe des ldapsearch Befehls aus ihrem letzten Posting, dort sind an beiden Zonen SOA Records gesetzt und auch der NS Eintrag an der Forward-Zone existiert:[code]dn: zoneName=digitronic-berlin.de,cn=dns,dc=digitronic-berlin,dc=de
dNSTTL: 10800
relativeDomainName: @
zoneName: digitronic-berlin.de
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/forward_zone
aRecord: 192.168.88.228
nSRecord: janus.digitronic-berlin.de.
sOARecord: janus.digitronic-berlin.de. root.digitronic-berlin.de. 67 28800 7200 604800 10800

dn: zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitronic-berlin,dc=de
nSRecord: janus.digitronic-berlin.de.
dNSTTL: 10800
relativeDomainName: @
zoneName: 88.168.192.in-addr.arpa
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/reverse_zone
sOARecord: janus.digitronic-berlin.de. root.digitronic-berlin.de. 36 28800 7200 604800 10800[/code]

Haben sich die Meldungen beim Start/Neustart der Bind-Dienste seit Ihrem ersten Posting verändert? Bitte prüfen Sie dies einmal indem Sie den Bind-Cache entfernen und univention-bind neu starten:/etc/init.d/univention-bind stop rm -rf /var/cache/bind/* /etc/init.d/univention-bind start

Bereits vorgenommene manuelle Anpassungen (z.B. bzgl. der managed-keys) sollten Sie in jedem Fall vorab Rückgängig machen.

Mit freundlichen Grüßen
Janis Meybohm


#9

Hallo,

ich war mit einem anderen Thema stark beschäftigt, weshalb ich leider erst heute reagieren kann. Die Sache mit dem bind ist schon ziemlich unerfreulich. Den Cache habe ich gemäß Hinweis komplett entfernt und bind9 neu gestartet. Leider ohne Veränderung.
Hier die syslog-Ausgabe:

Jul 9 16:59:40 janus named[17774]: shutting down Jul 9 16:59:40 janus named[17774]: stopping command channel on 127.0.0.1#55555 Jul 9 16:59:40 janus named[17774]: no longer listening on ::#7777 Jul 9 16:59:40 janus named[17774]: no longer listening on 127.0.0.1#7777 Jul 9 16:59:40 janus named[17774]: no longer listening on 192.168.88.228#7777 Jul 9 16:59:46 janus named[17776]: shutting down Jul 9 16:59:46 janus named[17776]: stopping command channel on 127.0.0.1#953 Jul 9 16:59:46 janus named[17776]: no longer listening on ::#53 Jul 9 16:59:46 janus named[17776]: no longer listening on 127.0.0.1#53 Jul 9 16:59:46 janus named[17776]: no longer listening on 192.168.88.228#53 Jul 9 16:59:46 janus named[17776]: exiting Jul 9 16:59:46 janus named[17856]: starting BIND 9.8.0-P4 -d 10 -c /etc/bind/named.conf -p 7777 -u bind -f Jul 9 16:59:46 janus named[17856]: 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-dlz-postgres=no' '--with-dlz-mysql=no' '--with-dlz-bdb=yes' '--with-dlz-filesystem=yes' '--with-dlz-ldap=yes' '--with-dlz-stub=yes' '--with-dlz-dlopen' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' 'LDFLAGS=' 'CPPFLAGS=' Jul 9 16:59:46 janus named[17856]: adjusted limit on open files from 1024 to 1048576 Jul 9 16:59:46 janus named[17856]: found 2 CPUs, using 2 worker threads Jul 9 16:59:46 janus named[17856]: using up to 4096 sockets Jul 9 16:59:46 janus named[17856]: loading configuration from '/etc/bind/named.conf' Jul 9 16:59:46 janus named[17856]: reading built-in trusted keys from file '/etc/bind/bind.keys' Jul 9 16:59:46 janus named[17856]: using default UDP/IPv4 port range: [1024, 65535] Jul 9 16:59:46 janus named[17856]: using default UDP/IPv6 port range: [1024, 65535] Jul 9 16:59:46 janus named[17856]: listening on IPv6 interfaces, port 7777 Jul 9 16:59:46 janus named[17856]: listening on IPv4 interface lo, 127.0.0.1#7777 Jul 9 16:59:46 janus named[17856]: listening on IPv4 interface eth0, 192.168.88.228#7777 Jul 9 16:59:46 janus named[17856]: generating session key for dynamic DNS Jul 9 16:59:46 janus named[17856]: set up managed keys zone for view _default, file 'managed-keys.bind' Jul 9 16:59:46 janus named[17856]: automatic empty zone: 0.IN-ADDR.ARPA Jul 9 16:59:46 janus named[17856]: automatic empty zone: 127.IN-ADDR.ARPA Jul 9 16:59:46 janus named[17856]: automatic empty zone: 254.169.IN-ADDR.ARPA Jul 9 16:59:46 janus named[17856]: automatic empty zone: 2.0.192.IN-ADDR.ARPA Jul 9 16:59:46 janus named[17856]: automatic empty zone: 100.51.198.IN-ADDR.ARPA Jul 9 16:59:46 janus named[17856]: automatic empty zone: 113.0.203.IN-ADDR.ARPA Jul 9 16:59:46 janus named[17856]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA Jul 9 16:59:46 janus named[17856]: 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 9 16:59:46 janus named[17856]: 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 9 16:59:46 janus named[17856]: automatic empty zone: D.F.IP6.ARPA Jul 9 16:59:46 janus named[17856]: automatic empty zone: 8.E.F.IP6.ARPA Jul 9 16:59:46 janus named[17856]: automatic empty zone: 9.E.F.IP6.ARPA Jul 9 16:59:46 janus named[17856]: automatic empty zone: A.E.F.IP6.ARPA Jul 9 16:59:46 janus named[17856]: automatic empty zone: B.E.F.IP6.ARPA Jul 9 16:59:46 janus named[17856]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA Jul 9 16:59:46 janus named[17856]: command channel listening on 127.0.0.1#55555 Jul 9 16:59:46 janus named[17856]: zone 88.168.192.in-addr.arpa/IN: could not find NS and/or SOA records Jul 9 16:59:46 janus named[17856]: zone 88.168.192.in-addr.arpa/IN: has 0 SOA records Jul 9 16:59:46 janus named[17856]: zone 88.168.192.in-addr.arpa/IN: has no NS records Jul 9 16:59:46 janus named[17856]: zone 88.168.192.in-addr.arpa/IN: not loaded due to errors. Jul 9 16:59:46 janus named[17856]: zone digitronic-berlin.de/IN: could not find NS and/or SOA records Jul 9 16:59:46 janus named[17856]: zone digitronic-berlin.de/IN: has 0 SOA records Jul 9 16:59:46 janus named[17856]: zone digitronic-berlin.de/IN: has no NS records Jul 9 16:59:46 janus named[17856]: zone digitronic-berlin.de/IN: not loaded due to errors. Jul 9 16:59:46 janus named[17856]: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found Jul 9 16:59:46 janus named[17856]: managed-keys-zone ./IN: loaded serial 0 Jul 9 16:59:46 janus named[17856]: running Jul 9 16:59:51 janus named[17873]: starting BIND 9.8.0-P4 -d 10 -c /etc/bind/named.conf.proxy -u bind -f Jul 9 16:59:51 janus named[17873]: 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-dlz-postgres=no' '--with-dlz-mysql=no' '--with-dlz-bdb=yes' '--with-dlz-filesystem=yes' '--with-dlz-ldap=yes' '--with-dlz-stub=yes' '--with-dlz-dlopen' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' 'LDFLAGS=' 'CPPFLAGS=' Jul 9 16:59:51 janus named[17873]: adjusted limit on open files from 1024 to 1048576 Jul 9 16:59:51 janus named[17873]: found 2 CPUs, using 2 worker threads Jul 9 16:59:51 janus named[17873]: using up to 4096 sockets Jul 9 16:59:51 janus named[17873]: loading configuration from '/etc/bind/named.conf.proxy' Jul 9 16:59:51 janus named[17873]: reading built-in trusted keys from file '/etc/bind/bind.keys' Jul 9 16:59:51 janus named[17873]: using default UDP/IPv4 port range: [1024, 65535] Jul 9 16:59:51 janus named[17873]: using default UDP/IPv6 port range: [1024, 65535] Jul 9 16:59:51 janus named[17873]: listening on IPv6 interfaces, port 53 Jul 9 16:59:51 janus named[17873]: listening on IPv4 interface lo, 127.0.0.1#53 Jul 9 16:59:51 janus named[17873]: listening on IPv4 interface eth0, 192.168.88.228#53 Jul 9 16:59:51 janus named[17873]: generating session key for dynamic DNS Jul 9 16:59:51 janus named[17873]: set up managed keys zone for view _default, file 'managed-keys.bind' Jul 9 16:59:51 janus named[17873]: automatic empty zone: 254.169.IN-ADDR.ARPA Jul 9 16:59:51 janus named[17873]: automatic empty zone: 2.0.192.IN-ADDR.ARPA Jul 9 16:59:51 janus named[17873]: automatic empty zone: 100.51.198.IN-ADDR.ARPA Jul 9 16:59:51 janus named[17873]: automatic empty zone: 113.0.203.IN-ADDR.ARPA Jul 9 16:59:51 janus named[17873]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA Jul 9 16:59:51 janus named[17873]: 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 9 16:59:51 janus named[17873]: 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 9 16:59:51 janus named[17873]: automatic empty zone: D.F.IP6.ARPA Jul 9 16:59:51 janus named[17873]: automatic empty zone: 8.E.F.IP6.ARPA Jul 9 16:59:51 janus named[17873]: automatic empty zone: 9.E.F.IP6.ARPA Jul 9 16:59:51 janus named[17873]: automatic empty zone: A.E.F.IP6.ARPA Jul 9 16:59:51 janus named[17873]: automatic empty zone: B.E.F.IP6.ARPA Jul 9 16:59:51 janus named[17873]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA Jul 9 16:59:51 janus named[17873]: command channel listening on 127.0.0.1#953 Jul 9 16:59:51 janus named[17873]: zone ./IN: has 0 SOA records Jul 9 16:59:51 janus named[17873]: zone ./IN: has no NS records Jul 9 16:59:51 janus named[17873]: zone ./IN: not loaded due to errors. Jul 9 16:59:51 janus named[17873]: zone 0.in-addr.arpa/IN: loaded serial 1 Jul 9 16:59:51 janus named[17873]: zone 127.in-addr.arpa/IN: loaded serial 1 Jul 9 16:59:51 janus named[17873]: zone 255.in-addr.arpa/IN: loaded serial 1 Jul 9 16:59:51 janus named[17873]: zone localhost/IN: loaded serial 2 Jul 9 16:59:51 janus named[17873]: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found Jul 9 16:59:51 janus named[17873]: managed-keys-zone ./IN: loaded serial 0 Jul 9 16:59:51 janus named[17873]: running Jul 9 16:59:51 janus named[17873]: zone digitronic-berlin.de/IN: refresh: unexpected rcode (SERVFAIL) from master 127.0.0.1#7777 (source 0.0.0.0#0) Jul 9 16:59:51 janus named[17873]: zone 88.168.192.in-addr.arpa/IN: refresh: unexpected rcode (SERVFAIL) from master 127.0.0.1#7777 (source 0.0.0.0#0)

Ich kann keine Veränderung zu dem ersten Log erkennen. Auch verstehe ich nicht, wieso laut ldapsearch die Zonendaten i.O. sind, diese aber beim Start von bind scheinbar nicht gefunden werden. Ich kenne mich leider zu wenig mit den sehr speziellen LDAP-Geschichten bei UCS-Systemen aus. Falls das Problem nicht lösbar ist, werde ich die Zonendaten wie früher in eine Textdatei schreiben.

mfg.
Hans-Jürgen Wegerich


#10

Hallo,

vielleicht eine zu triviale Vermutung, aber wenn es so ist, daß im LDAP eigentlich alles da ist und der BIND das nicht sieht: wissen wir, ob der Bind auch wirklich diesen LDAP befragt? Man findet es in der Bind-Konfiguration:

grep ldap /etc/bind/univention.conf.d/*

Wenn dort alles stimmt, würde ich als nächstes den Loglevel des LDAP Daemons erhöhen

univention-config-registry set ldap/debug/level=256
/etc/init.d/slapd restart

und einen Start des BIND protokollieren.


#11

Hallo,

danke für den Hinweis. Ich habe den Debug-Level erhöht und sehe nun tatsächlich eine Slapd-Fehlercode beim Start von bind:

Jul 24 09:43:57 janus slapd[21679]: conn=1001 op=3 SRCH base="dc=digitronic-berlin,dc=de" scope=2 deref=0 filter="(&(objectClass=posixAccount)(uid=bind))" Jul 24 09:43:57 janus slapd[21679]: conn=1001 op=3 SEARCH RESULT tag=101 err=0 nentries=0 text= Jul 24 09:43:57 janus slapd[21679]: conn=1001 op=4 SRCH base="dc=digitronic-berlin,dc=de" scope=2 deref=0 filter="(&(objectClass=posixGroup)(memberUid=bind))" Jul 24 09:43:57 janus slapd[21679]: conn=1001 op=4 SRCH attr=gidNumber Jul 24 09:43:57 janus slapd[21679]: conn=1001 op=4 SEARCH RESULT tag=101 err=0 nentries=0 text= Jul 24 09:43:57 janus named[21818]: starting BIND 9.8.0-P4 -d 10 -c /etc/bind/named.conf.proxy -u bind -f Jul 24 09:43:57 janus named[21818]: 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-dlz-postgres=no' '--with-dlz-mysql=no' '--with-dlz-bdb=yes' '--with-dlz-filesystem=yes' '--with-dlz-ldap=yes' '--with-dlz-stub=yes' '--with-dlz-dlopen' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' 'LDFLAGS=' 'CPPFLAGS=' Jul 24 09:43:57 janus named[21818]: adjusted limit on open files from 1024 to 1048576 Jul 24 09:43:57 janus named[21818]: found 2 CPUs, using 2 worker threads Jul 24 09:43:57 janus named[21818]: using up to 4096 sockets Jul 24 09:43:57 janus named[21818]: loading configuration from '/etc/bind/named.conf.proxy' Jul 24 09:43:57 janus named[21818]: reading built-in trusted keys from file '/etc/bind/bind.keys' Jul 24 09:43:57 janus named[21818]: using default UDP/IPv4 port range: [1024, 65535] Jul 24 09:43:57 janus named[21818]: using default UDP/IPv6 port range: [1024, 65535] Jul 24 09:43:57 janus named[21818]: listening on IPv6 interfaces, port 53 Jul 24 09:43:57 janus named[21818]: listening on IPv4 interface lo, 127.0.0.1#53 Jul 24 09:43:57 janus named[21818]: listening on IPv4 interface eth0, 192.168.88.228#53 Jul 24 09:43:57 janus named[21818]: generating session key for dynamic DNS Jul 24 09:43:57 janus named[21818]: set up managed keys zone for view _default, file 'managed-keys.bind' Jul 24 09:43:57 janus named[21818]: automatic empty zone: 254.169.IN-ADDR.ARPA Jul 24 09:43:57 janus named[21818]: automatic empty zone: 2.0.192.IN-ADDR.ARPA Jul 24 09:43:57 janus named[21818]: automatic empty zone: 100.51.198.IN-ADDR.ARPA Jul 24 09:43:57 janus named[21818]: automatic empty zone: 113.0.203.IN-ADDR.ARPA Jul 24 09:43:57 janus named[21818]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA Jul 24 09:43:57 janus named[21818]: 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 24 09:43:57 janus named[21818]: 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 24 09:43:57 janus named[21818]: automatic empty zone: D.F.IP6.ARPA Jul 24 09:43:57 janus named[21818]: automatic empty zone: 8.E.F.IP6.ARPA Jul 24 09:43:57 janus named[21818]: automatic empty zone: 9.E.F.IP6.ARPA Jul 24 09:43:57 janus named[21818]: automatic empty zone: A.E.F.IP6.ARPA Jul 24 09:43:57 janus named[21818]: automatic empty zone: B.E.F.IP6.ARPA Jul 24 09:43:57 janus named[21818]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA Jul 24 09:43:57 janus named[21818]: command channel listening on 127.0.0.1#953 Jul 24 09:43:57 janus named[21818]: zone ./IN: has 0 SOA records Jul 24 09:43:57 janus named[21818]: zone ./IN: has no NS records Jul 24 09:43:57 janus named[21818]: zone ./IN: not loaded due to errors. Jul 24 09:43:57 janus named[21818]: zone 0.in-addr.arpa/IN: loaded serial 1 Jul 24 09:43:57 janus named[21818]: zone 127.in-addr.arpa/IN: loaded serial 1 Jul 24 09:43:57 janus named[21818]: zone 255.in-addr.arpa/IN: loaded serial 1 Jul 24 09:43:57 janus named[21818]: zone localhost/IN: loaded serial 2 Jul 24 09:43:57 janus named[21818]: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found Jul 24 09:43:57 janus named[21818]: managed-keys-zone ./IN: loaded serial 0 Jul 24 09:43:57 janus named[21818]: running Jul 24 09:43:58 janus named[21827]: starting BIND 9.8.0-P4 -d 10 -c /etc/bind/named.conf -p 7777 -u bind -f Jul 24 09:43:58 janus named[21827]: 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-dlz-postgres=no' '--with-dlz-mysql=no' '--with-dlz-bdb=yes' '--with-dlz-filesystem=yes' '--with-dlz-ldap=yes' '--with-dlz-stub=yes' '--with-dlz-dlopen' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' 'LDFLAGS=' 'CPPFLAGS=' Jul 24 09:43:58 janus named[21827]: adjusted limit on open files from 1024 to 1048576 Jul 24 09:43:58 janus named[21827]: found 2 CPUs, using 2 worker threads Jul 24 09:43:58 janus named[21827]: using up to 4096 sockets Jul 24 09:43:58 janus named[21827]: loading configuration from '/etc/bind/named.conf' Jul 24 09:43:58 janus named[21827]: reading built-in trusted keys from file '/etc/bind/bind.keys' Jul 24 09:43:58 janus named[21827]: using default UDP/IPv4 port range: [1024, 65535] Jul 24 09:43:58 janus named[21827]: using default UDP/IPv6 port range: [1024, 65535] Jul 24 09:43:59 janus named[21827]: listening on IPv6 interfaces, port 7777 Jul 24 09:43:59 janus named[21827]: listening on IPv4 interface lo, 127.0.0.1#7777 Jul 24 09:43:59 janus named[21827]: listening on IPv4 interface eth0, 192.168.88.228#7777 Jul 24 09:43:59 janus named[21827]: generating session key for dynamic DNS Jul 24 09:44:00 janus named[21827]: set up managed keys zone for view _default, file 'managed-keys.bind' Jul 24 09:44:00 janus named[21827]: automatic empty zone: 0.IN-ADDR.ARPA Jul 24 09:44:00 janus named[21827]: automatic empty zone: 127.IN-ADDR.ARPA Jul 24 09:44:00 janus named[21827]: automatic empty zone: 254.169.IN-ADDR.ARPA Jul 24 09:44:00 janus named[21827]: automatic empty zone: 2.0.192.IN-ADDR.ARPA Jul 24 09:44:00 janus named[21827]: automatic empty zone: 100.51.198.IN-ADDR.ARPA Jul 24 09:44:00 janus named[21827]: automatic empty zone: 113.0.203.IN-ADDR.ARPA Jul 24 09:44:00 janus named[21827]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA Jul 24 09:44:00 janus named[21827]: 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 24 09:44:00 janus named[21827]: 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 24 09:44:00 janus named[21827]: automatic empty zone: D.F.IP6.ARPA Jul 24 09:44:00 janus named[21827]: automatic empty zone: 8.E.F.IP6.ARPA Jul 24 09:44:00 janus named[21827]: automatic empty zone: 9.E.F.IP6.ARPA Jul 24 09:44:00 janus named[21827]: automatic empty zone: A.E.F.IP6.ARPA Jul 24 09:44:00 janus named[21827]: automatic empty zone: B.E.F.IP6.ARPA Jul 24 09:44:00 janus named[21827]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA Jul 24 09:44:00 janus named[21827]: command channel listening on 127.0.0.1#55555 Jul 24 09:44:00 janus slapd[21679]: conn=1006 fd=26 ACCEPT from IP=192.168.88.228:35994 (IP=0.0.0.0:389) Jul 24 09:44:00 janus slapd[21679]: conn=1006 op=0 BIND dn="" method=128 Jul 24 09:44:00 janus slapd[21679]: conn=1006 op=0 RESULT tag=97 err=0 text= Jul 24 09:44:00 janus slapd[21679]: conn=1006 op=1 SRCH base="zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitronic-berlin,dc=de" scope=2 deref=0 filter="(&(zoneName=88.168.192.in-addr.arpa)(relativeDomainName=@))" Jul 24 09:44:00 janus slapd[21679]: OVER: rs->sr_err != LDAP_SUCCESS on "zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitronic-berlin,dc=de" ERR: 0x20 Jul 24 09:44:00 janus slapd[21679]: conn=1006 op=1 SEARCH RESULT tag=101 err=32 nentries=0 text= Jul 24 09:44:00 janus named[21827]: zone 88.168.192.in-addr.arpa/IN: could not find NS and/or SOA records Jul 24 09:44:00 janus named[21827]: zone 88.168.192.in-addr.arpa/IN: has 0 SOA records Jul 24 09:44:00 janus named[21827]: zone 88.168.192.in-addr.arpa/IN: has no NS records Jul 24 09:44:00 janus named[21827]: zone 88.168.192.in-addr.arpa/IN: not loaded due to errors. Jul 24 09:44:00 janus slapd[21679]: conn=1007 fd=28 ACCEPT from IP=192.168.88.228:35995 (IP=0.0.0.0:389) Jul 24 09:44:00 janus slapd[21679]: conn=1007 op=0 BIND dn="" method=128 Jul 24 09:44:00 janus slapd[21679]: conn=1007 op=0 RESULT tag=97 err=0 text= Jul 24 09:44:00 janus slapd[21679]: conn=1007 op=1 SRCH base="zoneName=digitronic-berlin.de,cn=dns,dc=digitronic-berlin,dc=de" scope=2 deref=0 filter="(&(zoneName=digitronic-berlin.de)(relativeDomainName=@))" Jul 24 09:44:00 janus slapd[21679]: OVER: rs->sr_err != LDAP_SUCCESS on "zoneName=digitronic-berlin.de,cn=dns,dc=digitronic-berlin,dc=de" ERR: 0x20 Jul 24 09:44:00 janus slapd[21679]: conn=1007 op=1 SEARCH RESULT tag=101 err=32 nentries=0 text= Jul 24 09:44:00 janus named[21827]: zone digitronic-berlin.de/IN: could not find NS and/or SOA records Jul 24 09:44:00 janus named[21827]: zone digitronic-berlin.de/IN: has 0 SOA records Jul 24 09:44:00 janus named[21827]: zone digitronic-berlin.de/IN: has no NS records Jul 24 09:44:00 janus named[21827]: zone digitronic-berlin.de/IN: not loaded due to errors. Jul 24 09:44:00 janus named[21827]: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found Jul 24 09:44:00 janus named[21827]: managed-keys-zone ./IN: loaded serial 0 Jul 24 09:44:00 janus named[21827]: running

Ich weiß leider nicht, was diese Fehler ERR:0x20 bzw. err=32 bedeuten. Auch in den /etc/bind/univention.conf.d/* kann ich keine Fehler entdecken.

grep ldap /etc/bind/univention.conf.d/*

/etc/bind/univention.conf.d/88.168.192.in-addr.arpa: database "ldap ldap://192.168.88.228/zoneName=88.168.192.in-addr.arpa,cn=dns,dc=digitronic-berlin,dc=de 172800"; /etc/bind/univention.conf.d/digitronic-berlin.de: database "ldap ldap://192.168.88.228/zoneName=digitronic-berlin.de,cn=dns,dc=digitronic-berlin,dc=de 172800";

Gruß Hans-Jürgen
(für jeden Hinweis dankbar)


#12

Hallo,

Wenn ich das richtig interpretiere, versucht der BIND sich anonym am LDAP zu binden:

Fehler 0x20 ist LDAP_NO_SUCH_OBJECT, er sagt also, daß er das Objekt nicht kennt. Aus vorherigen Posts entnehme ich aber, daß univention-ldapsearch das Objekt findet? Der Unterschied ist, daß sich univention-ldapsearch hinter den Kulissen mit dem DN des Maschinen-Accounts und dem Paßwort in /etc/machine.secret ausweist. Das sollte der BIND eigentlich auch tun, glaube ich. Oder am LDAP sind ACLs verändert, die das Auslesen des DNS-Objektes für anonyme Anfragen verhindern.

Ich kann leider hier nicht vergleichen, da bei uns Samba4 als DNS Backend benutzt wird. Sie müßten (hoffe ich) auf jeden Fall UCR-Variablen betreffs DNS finden, die dies konfigurieren.

Freundliche Grüße
Frank Greif.


#13

Das sollte er eigentlich nicht. In der Database-Zeile sollte auch der Bindname/-paßwort stehen.

EDIT: Zumindest wenn die UCR-Variable ldap/acl/read/anonymous auf no steht. Nach dem Upgrade auf UCS 3 sollte sie aber so viel ich weiß auf yes stehen. Sofern das dann nicht verändert wurde, liegt das Problem vermutlich woanders


#14

Prima! Das war’s!
Bei uns stand die UCR-Variable ldap/acl/read/anonymous auf no. Nachdem ich sie auf “yes” gesetzt habe, “lebt” der bind wieder. :slight_smile:
Ich danke allen, die mitgewirkt haben, dieses Problem zu lösen.

Grüße aus dem Admin-Raum (28°C)
Hans-Jürgen

@greif: Ich habe mir nicht gemerkt wie der Debuglevel vorher stand. Sollte ich ihn auf 0 stellen oder welcher Wert ist sinnvoll?


#15

Hm es ist ja erstmal prima, daß der Bind wieder läuft. Allerdings fände ich es schon wichtig herauszufinden wieso die Dateien ohne angabe des LDAP-Bind-Accounts erzeugt werden. Da ist schon noch was im argen