UCS (backup) not resolving internal DNS


#1

We have 2 Univention Corporate Servers.
DNS from the master server is giving results for both internal and external domain names.
The backup server only resolves external domain names.

I checked the configuration, but can’t find out what’s wrong.
Your support is welcome.


#2

I found the following, but that didn’t solve the issue.
sdb.univention.de/content/20/254 … ailed.html


#3

This information is logged in daemon.log

The file /var/cache/bind/finalist.lcl.zone does not exist.

Oct 21 11:51:03 p-ucs-backup named[22459]: starting BIND 9.8.4-rpz2+rl005.12-P1 -c /etc/bind/named.conf -p 7777 -u bind -f -d 99
Oct 21 11:51:03 p-ucs-backup named[22459]: built with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/var' '--enable-threads' '--enable-largefile' '--with-libtool' '--enable-shared' '--enable-static' '--with-openssl=/usr' '--with-gssapi=/usr' '--with-gnu-ld' '--with-geoip=/usr' '--enable-ipv6' '--with-dlz-dlopen' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2'
Oct 21 11:51:03 p-ucs-backup named[22459]: ----------------------------------------------------
Oct 21 11:51:03 p-ucs-backup named[22459]: BIND 9 is maintained by Internet Systems Consortium,
Oct 21 11:51:03 p-ucs-backup named[22459]: Inc. (ISC), a non-profit 501(c)(3) public-benefit 
Oct 21 11:51:03 p-ucs-backup named[22459]: corporation.  Support and training for BIND 9 are 
Oct 21 11:51:03 p-ucs-backup named[22459]: available at https://www.isc.org/support
Oct 21 11:51:03 p-ucs-backup named[22459]: ----------------------------------------------------
Oct 21 11:51:03 p-ucs-backup named[22459]: adjusted limit on open files from 4096 to 1048576
Oct 21 11:51:03 p-ucs-backup named[22459]: found 4 CPUs, using 4 worker threads
Oct 21 11:51:03 p-ucs-backup named[22459]: using up to 4096 sockets
Oct 21 11:51:03 p-ucs-backup named[22459]: loading configuration from '/etc/bind/named.conf'
Oct 21 11:51:03 p-ucs-backup named[22459]: reading built-in trusted keys from file '/etc/bind/bind.keys'
Oct 21 11:51:03 p-ucs-backup named[22459]: using default UDP/IPv4 port range: [1024, 65535]
Oct 21 11:51:03 p-ucs-backup named[22459]: using default UDP/IPv6 port range: [1024, 65535]
Oct 21 11:51:03 p-ucs-backup named[22459]: listening on IPv6 interfaces, port 7777
Oct 21 11:51:03 p-ucs-backup named[22459]: listening on IPv4 interface lo, 127.0.0.1#7777
Oct 21 11:51:03 p-ucs-backup named[22459]: listening on IPv4 interface eth0, 10.120.10.9#7777
Oct 21 11:51:03 p-ucs-backup named[22459]: listening on IPv4 interface docker0, 172.17.42.1#7777
Oct 21 11:51:03 p-ucs-backup named[22459]: generating session key for dynamic DNS
Oct 21 11:51:03 p-ucs-backup named[22459]: sizing zone task pool based on 3 zones
Oct 21 11:51:03 p-ucs-backup named[22459]: set up managed keys zone for view _default, file 'managed-keys.bind'
Oct 21 11:51:03 p-ucs-backup named[22459]: Warning: 'empty-zones-enable/disable-empty-zone' not set: disabling RFC 1918 empty zones
Oct 21 11:51:03 p-ucs-backup named[22459]: automatic empty zone: 0.IN-ADDR.ARPA
Oct 21 11:51:03 p-ucs-backup named[22459]: automatic empty zone: 127.IN-ADDR.ARPA
Oct 21 11:51:03 p-ucs-backup named[22459]: automatic empty zone: 254.169.IN-ADDR.ARPA
Oct 21 11:51:03 p-ucs-backup named[22459]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Oct 21 11:51:03 p-ucs-backup named[22459]: automatic empty zone: 100.51.198.IN-ADDR.ARPA
Oct 21 11:51:03 p-ucs-backup named[22459]: automatic empty zone: 113.0.203.IN-ADDR.ARPA
Oct 21 11:51:03 p-ucs-backup named[22459]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Oct 21 11:51:03 p-ucs-backup named[22459]: 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
Oct 21 11:51:03 p-ucs-backup named[22459]: 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
Oct 21 11:51:03 p-ucs-backup named[22459]: automatic empty zone: D.F.IP6.ARPA
Oct 21 11:51:03 p-ucs-backup named[22459]: automatic empty zone: 8.E.F.IP6.ARPA
Oct 21 11:51:03 p-ucs-backup named[22459]: automatic empty zone: 9.E.F.IP6.ARPA
Oct 21 11:51:03 p-ucs-backup named[22459]: automatic empty zone: A.E.F.IP6.ARPA
Oct 21 11:51:03 p-ucs-backup named[22459]: automatic empty zone: B.E.F.IP6.ARPA
Oct 21 11:51:03 p-ucs-backup named[22459]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
Oct 21 11:51:03 p-ucs-backup named[22459]: command channel listening on 127.0.0.1#55555
Oct 21 11:51:03 p-ucs-backup named[22459]: now using logging configuration from config file
Oct 21 11:51:03 p-ucs-backup named[22459]: load_configuration: success
Oct 21 11:51:03 p-ucs-backup named[22459]: client @0x56244095ef50: udprecv
Oct 21 11:51:03 p-ucs-backup named[22459]: socket 0x7f8a89247010: socket_recv: event 0x7f8a891a1148 -> task 0x7f8a89225900
Oct 21 11:51:03 p-ucs-backup named[22459]: sockmgr 0x7f8a89218010: watcher got message -3 for socket 512
Oct 21 11:51:03 p-ucs-backup named[22459]: sockmgr 0x7f8a89218010: watcher got message -2 for socket -1
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 0.IN-ADDR.ARPA/IN: starting load
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 0.IN-ADDR.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 0.IN-ADDR.ARPA/IN: loaded; checking validity
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 0.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 120.10.in-addr.arpa/IN: starting load
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 120.10.in-addr.arpa/IN: number of nodes in database: 0
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 120.10.in-addr.arpa/IN: loaded; checking validity
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 120.10.in-addr.arpa/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 127.IN-ADDR.ARPA/IN: starting load
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 127.IN-ADDR.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 127.IN-ADDR.ARPA/IN: loaded; checking validity
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 127.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 254.169.IN-ADDR.ARPA/IN: starting load
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 254.169.IN-ADDR.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 254.169.IN-ADDR.ARPA/IN: loaded; checking validity
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 254.169.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 2.0.192.IN-ADDR.ARPA/IN: starting load
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 2.0.192.IN-ADDR.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 2.0.192.IN-ADDR.ARPA/IN: loaded; checking validity
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 2.0.192.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 168.192.in-addr.arpa/IN: starting load
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 168.192.in-addr.arpa/IN: number of nodes in database: 0
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 168.192.in-addr.arpa/IN: loaded; checking validity
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 168.192.in-addr.arpa/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 100.51.198.IN-ADDR.ARPA/IN: starting load
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 100.51.198.IN-ADDR.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 100.51.198.IN-ADDR.ARPA/IN: loaded; checking validity
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 100.51.198.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 113.0.203.IN-ADDR.ARPA/IN: starting load
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 113.0.203.IN-ADDR.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 113.0.203.IN-ADDR.ARPA/IN: loaded; checking validity
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 113.0.203.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 255.255.255.255.IN-ADDR.ARPA/IN: starting load
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 255.255.255.255.IN-ADDR.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 255.255.255.255.IN-ADDR.ARPA/IN: loaded; checking validity
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 255.255.255.255.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: 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
Oct 21 11:51:03 p-ucs-backup named[22459]: 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: number of nodes in database: 0
Oct 21 11:51:03 p-ucs-backup named[22459]: 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: loaded; checking validity
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: 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: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: 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/IN: starting load
Oct 21 11:51:03 p-ucs-backup named[22459]: 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/IN: number of nodes in database: 0
Oct 21 11:51:03 p-ucs-backup named[22459]: 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/IN: loaded; checking validity
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: 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/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 8.B.D.0.1.0.0.2.IP6.ARPA/IN: starting load
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 8.B.D.0.1.0.0.2.IP6.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 8.B.D.0.1.0.0.2.IP6.ARPA/IN: loaded; checking validity
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 8.B.D.0.1.0.0.2.IP6.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone D.F.IP6.ARPA/IN: starting load
Oct 21 11:51:03 p-ucs-backup named[22459]: zone D.F.IP6.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:03 p-ucs-backup named[22459]: zone D.F.IP6.ARPA/IN: loaded; checking validity
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone D.F.IP6.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 8.E.F.IP6.ARPA/IN: starting load
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 8.E.F.IP6.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 8.E.F.IP6.ARPA/IN: loaded; checking validity
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 8.E.F.IP6.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 9.E.F.IP6.ARPA/IN: starting load
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 9.E.F.IP6.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:03 p-ucs-backup named[22459]: zone 9.E.F.IP6.ARPA/IN: loaded; checking validity
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 9.E.F.IP6.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone A.E.F.IP6.ARPA/IN: starting load
Oct 21 11:51:03 p-ucs-backup named[22459]: zone A.E.F.IP6.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:03 p-ucs-backup named[22459]: zone A.E.F.IP6.ARPA/IN: loaded; checking validity
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone A.E.F.IP6.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone B.E.F.IP6.ARPA/IN: starting load
Oct 21 11:51:03 p-ucs-backup named[22459]: zone B.E.F.IP6.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:03 p-ucs-backup named[22459]: zone B.E.F.IP6.ARPA/IN: loaded; checking validity
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone B.E.F.IP6.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone finalist.lcl/IN: starting load
Oct 21 11:51:03 p-ucs-backup named[22459]: zone finalist.lcl/IN: number of nodes in database: 0
Oct 21 11:51:03 p-ucs-backup named[22459]: zone finalist.lcl/IN: loaded; checking validity
Oct 21 11:51:03 p-ucs-backup named[22459]: zone finalist.lcl/IN: NS 'p-ucs-master.finalist.lcl' has no address records (A or AAAA)
Oct 21 11:51:03 p-ucs-backup named[22459]: zone finalist.lcl/IN: NS 'p-ucs-backup.finalist.lcl' has no address records (A or AAAA)
Oct 21 11:51:03 p-ucs-backup named[22459]: zone finalist.lcl/IN: not loaded due to errors.
Oct 21 11:51:03 p-ucs-backup named[22459]: managed-keys-zone ./IN: starting load
Oct 21 11:51:03 p-ucs-backup named[22459]: managed-keys-zone ./IN: number of nodes in database: 1
Oct 21 11:51:03 p-ucs-backup named[22459]: managed-keys-zone ./IN: journal rollforward completed successfully: up to date
Oct 21 11:51:03 p-ucs-backup named[22459]: managed-keys-zone ./IN: loaded; checking validity
Oct 21 11:51:03 p-ucs-backup named[22459]: managed-keys-zone ./IN: synchronizing trusted keys
Oct 21 11:51:03 p-ucs-backup named[22459]: decrement_reference: delete from rbt: 0x7f8a80c8f698 .
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: managed-keys-zone ./IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: managed-keys-zone ./IN: settimer inactive
Oct 21 11:51:03 p-ucs-backup named[22459]: managed-keys-zone ./IN: loaded serial 4
Oct 21 11:51:03 p-ucs-backup named[22459]: zone authors.bind/CH: starting load
Oct 21 11:51:03 p-ucs-backup named[22459]: zone authors.bind/CH: number of nodes in database: 0
Oct 21 11:51:03 p-ucs-backup named[22459]: zone authors.bind/CH: loaded; checking validity
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone authors.bind/CH: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone hostname.bind/CH: starting load
Oct 21 11:51:03 p-ucs-backup named[22459]: zone hostname.bind/CH: number of nodes in database: 0
Oct 21 11:51:03 p-ucs-backup named[22459]: zone hostname.bind/CH: loaded; checking validity
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone hostname.bind/CH: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone version.bind/CH: starting load
Oct 21 11:51:03 p-ucs-backup named[22459]: zone version.bind/CH: number of nodes in database: 0
Oct 21 11:51:03 p-ucs-backup named[22459]: zone version.bind/CH: loaded; checking validity
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone version.bind/CH: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone id.server/CH: starting load
Oct 21 11:51:03 p-ucs-backup named[22459]: zone id.server/CH: number of nodes in database: 0
Oct 21 11:51:03 p-ucs-backup named[22459]: zone id.server/CH: loaded; checking validity
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone id.server/CH: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: dns_zone_maintenance: zone 168.192.in-addr.arpa/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 168.192.in-addr.arpa/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: dns_zone_maintenance: zone finalist.lcl/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone finalist.lcl/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone finalist.lcl/IN: settimer inactive
Oct 21 11:51:03 p-ucs-backup named[22459]: dns_zone_maintenance: zone 120.10.in-addr.arpa/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 120.10.in-addr.arpa/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: dns_zone_maintenance: managed-keys-zone ./IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: managed-keys-zone ./IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: managed-keys-zone ./IN: settimer inactive
Oct 21 11:51:03 p-ucs-backup named[22459]: dns_zone_maintenance: zone 0.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 0.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: dns_zone_maintenance: zone 127.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 127.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: dns_zone_maintenance: zone 254.169.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 254.169.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: dns_zone_maintenance: zone 2.0.192.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 2.0.192.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: dns_zone_maintenance: zone 100.51.198.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 100.51.198.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: dns_zone_maintenance: zone 113.0.203.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 113.0.203.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: dns_zone_maintenance: zone 255.255.255.255.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 255.255.255.255.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: dns_zone_maintenance: 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: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: 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: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: dns_zone_maintenance: 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/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: 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/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: dns_zone_maintenance: zone D.F.IP6.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone D.F.IP6.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: dns_zone_maintenance: zone 8.E.F.IP6.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 8.E.F.IP6.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: dns_zone_maintenance: zone 9.E.F.IP6.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 9.E.F.IP6.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: dns_zone_maintenance: zone A.E.F.IP6.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone A.E.F.IP6.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: dns_zone_maintenance: zone B.E.F.IP6.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone B.E.F.IP6.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: dns_zone_maintenance: zone 8.B.D.0.1.0.0.2.IP6.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone 8.B.D.0.1.0.0.2.IP6.ARPA/IN: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: dns_zone_maintenance: zone version.bind/CH: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone version.bind/CH: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: dns_zone_maintenance: zone hostname.bind/CH: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone hostname.bind/CH: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: dns_zone_maintenance: zone authors.bind/CH: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone authors.bind/CH: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: dns_zone_maintenance: zone id.server/CH: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: zone_settimer: zone id.server/CH: enter
Oct 21 11:51:03 p-ucs-backup named[22459]: running
Oct 21 11:51:03 p-ucs-backup named[22459]: client @0x56244095f500: udprecv
Oct 21 11:51:03 p-ucs-backup named[22459]: socket 0x7f8a89247010: socket_recv: event 0x7f8a89160148 -> task 0x7f8a892259b0
Oct 21 11:51:03 p-ucs-backup named[22459]: client @0x562440a340b0: udprecv
Oct 21 11:51:03 p-ucs-backup named[22459]: socket 0x7f8a89247490: socket_recv: event 0x7f8a810d7148 -> task 0x7f8a89225d20
Oct 21 11:51:03 p-ucs-backup named[22459]: client @0x562440a4d900: udprecv
Oct 21 11:51:03 p-ucs-backup named[22459]: socket 0x7f8a89247490: socket_recv: event 0x7f8a81096148 -> task 0x7f8a89225dd0
Oct 21 11:51:03 p-ucs-backup named[22459]: client @0x562440a5baf0: udprecv
ok: run: univention-bind-proxy: (pid 22478) 0s, normally down
Oct 21 11:51:08 p-ucs-backup named[22478]: starting BIND 9.8.4-rpz2+rl005.12-P1 -c /etc/bind/named.conf.proxy -u bind -f -d 99
Oct 21 11:51:08 p-ucs-backup named[22478]: built with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/var' '--enable-threads' '--enable-largefile' '--with-libtool' '--enable-shared' '--enable-static' '--with-openssl=/usr' '--with-gssapi=/usr' '--with-gnu-ld' '--with-geoip=/usr' '--enable-ipv6' '--with-dlz-dlopen' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2'
Oct 21 11:51:08 p-ucs-backup named[22478]: ----------------------------------------------------
Oct 21 11:51:08 p-ucs-backup named[22478]: BIND 9 is maintained by Internet Systems Consortium,
Oct 21 11:51:08 p-ucs-backup named[22478]: Inc. (ISC), a non-profit 501(c)(3) public-benefit 
Oct 21 11:51:08 p-ucs-backup named[22478]: corporation.  Support and training for BIND 9 are 
Oct 21 11:51:08 p-ucs-backup named[22478]: available at https://www.isc.org/support
Oct 21 11:51:08 p-ucs-backup named[22478]: ----------------------------------------------------
Oct 21 11:51:08 p-ucs-backup named[22478]: adjusted limit on open files from 4096 to 1048576
Oct 21 11:51:08 p-ucs-backup named[22478]: found 4 CPUs, using 4 worker threads
Oct 21 11:51:08 p-ucs-backup named[22478]: using up to 4096 sockets
Oct 21 11:51:08 p-ucs-backup named[22478]: loading configuration from '/etc/bind/named.conf.proxy'
Oct 21 11:51:08 p-ucs-backup named[22478]: reading built-in trusted keys from file '/etc/bind/bind.keys'
Oct 21 11:51:08 p-ucs-backup named[22478]: using default UDP/IPv4 port range: [1024, 65535]
Oct 21 11:51:08 p-ucs-backup named[22478]: using default UDP/IPv6 port range: [1024, 65535]
Oct 21 11:51:08 p-ucs-backup named[22478]: listening on IPv6 interfaces, port 53
Oct 21 11:51:08 p-ucs-backup named[22478]: listening on IPv4 interface lo, 127.0.0.1#53
Oct 21 11:51:08 p-ucs-backup named[22478]: listening on IPv4 interface eth0, 10.120.10.9#53
Oct 21 11:51:08 p-ucs-backup named[22478]: listening on IPv4 interface docker0, 172.17.42.1#53
Oct 21 11:51:08 p-ucs-backup named[22478]: generating session key for dynamic DNS
Oct 21 11:51:08 p-ucs-backup named[22478]: sizing zone task pool based on 8 zones
Oct 21 11:51:08 p-ucs-backup named[22478]: set up managed keys zone for view _default, file 'managed-keys.bind'
Oct 21 11:51:08 p-ucs-backup named[22478]: Warning: 'empty-zones-enable/disable-empty-zone' not set: disabling RFC 1918 empty zones
Oct 21 11:51:08 p-ucs-backup named[22478]: automatic empty zone: 254.169.IN-ADDR.ARPA
Oct 21 11:51:08 p-ucs-backup named[22478]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Oct 21 11:51:08 p-ucs-backup named[22478]: automatic empty zone: 100.51.198.IN-ADDR.ARPA
Oct 21 11:51:08 p-ucs-backup named[22478]: automatic empty zone: 113.0.203.IN-ADDR.ARPA
Oct 21 11:51:08 p-ucs-backup named[22478]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Oct 21 11:51:08 p-ucs-backup named[22478]: 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
Oct 21 11:51:08 p-ucs-backup named[22478]: 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
Oct 21 11:51:08 p-ucs-backup named[22478]: automatic empty zone: D.F.IP6.ARPA
Oct 21 11:51:08 p-ucs-backup named[22478]: automatic empty zone: 8.E.F.IP6.ARPA
Oct 21 11:51:08 p-ucs-backup named[22478]: automatic empty zone: 9.E.F.IP6.ARPA
Oct 21 11:51:08 p-ucs-backup named[22478]: automatic empty zone: A.E.F.IP6.ARPA
Oct 21 11:51:08 p-ucs-backup named[22478]: automatic empty zone: B.E.F.IP6.ARPA
Oct 21 11:51:08 p-ucs-backup named[22478]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
Oct 21 11:51:08 p-ucs-backup named[22478]: command channel listening on 127.0.0.1#953
Oct 21 11:51:08 p-ucs-backup named[22478]: now using logging configuration from config file
Oct 21 11:51:08 p-ucs-backup named[22478]: sockmgr 0x7f7bc860c010: watcher got message -3 for socket 24
Oct 21 11:51:08 p-ucs-backup named[22478]: sockmgr 0x7f7bc860c010: watcher got message -2 for socket -1
Oct 21 11:51:08 p-ucs-backup named[22478]: client @0x55ea28586f50: udprecv
Oct 21 11:51:08 p-ucs-backup named[22478]: socket 0x7f7bc863c010: socket_recv: event 0x7f7bc8595148 -> task 0x7f7bc8619900
Oct 21 11:51:08 p-ucs-backup named[22478]: client @0x55ea285cd560: udprecv
Oct 21 11:51:08 p-ucs-backup named[22478]: socket 0x7f7bc863c010: socket_recv: event 0x7f7bc84d2148 -> task 0x7f7bc8619b10
Oct 21 11:51:08 p-ucs-backup named[22478]: client @0x55ea28658510: accept
Oct 21 11:51:08 p-ucs-backup named[22478]: client @0x55ea2865c0b0: udprecv
Oct 21 11:51:08 p-ucs-backup named[22478]: socket 0x7f7bc863c490: socket_recv: event 0x7f7bc04cb148 -> task 0x7f7bc8619d20
Oct 21 11:51:08 p-ucs-backup named[22478]: client @0x55ea28675900: udprecv
Oct 21 11:51:08 p-ucs-backup named[22478]: socket 0x7f7bc863c490: socket_recv: event 0x7f7bc048a148 -> task 0x7f7bc8619dd0
Oct 21 11:51:08 p-ucs-backup named[22478]: client @0x55ea28683af0: udprecv
Oct 21 11:51:08 p-ucs-backup named[22478]: socket 0x7f7bc863c490: socket_recv: event 0x7f7bc0449148 -> task 0x7f7bc8619e80
Oct 21 11:51:08 p-ucs-backup named[22478]: client @0x55ea28691ce0: udprecv
Oct 21 11:51:08 p-ucs-backup named[22478]: socket 0x7f7bc863c490: socket_recv: event 0x7f7bc0408148 -> task 0x7f7bc8619f30
Oct 21 11:51:08 p-ucs-backup named[22478]: client @0x55ea2869fed0: accept
Oct 21 11:51:08 p-ucs-backup named[22478]: client @0x55ea286ae800: udprecv
Oct 21 11:51:08 p-ucs-backup named[22478]: socket 0x7f7bc863c910: socket_recv: event 0x7f7bc0386148 -> task 0x7f7bc863e170
Oct 21 11:51:08 p-ucs-backup named[22478]: client @0x55ea286bcb60: udprecv
Oct 21 11:51:08 p-ucs-backup named[22478]: socket 0x7f7bc863c910: socket_recv: event 0x7f7bc0345148 -> task 0x7f7bc863e220
Oct 21 11:51:08 p-ucs-backup named[22478]: client @0x55ea286caec0: udprecv
Oct 21 11:51:08 p-ucs-backup named[22478]: socket 0x7f7bc863c910: socket_recv: event 0x7f7bc0304148 -> task 0x7f7bc863e2d0
Oct 21 11:51:08 p-ucs-backup named[22478]: client @0x55ea286d9220: udprecv
Oct 21 11:51:08 p-ucs-backup named[22478]: socket 0x7f7bc863c910: socket_recv: event 0x7f7bc02c3148 -> task 0x7f7bc863e380
Oct 21 11:51:08 p-ucs-backup named[22478]: client @0x55ea286e7580: accept
Oct 21 11:51:08 p-ucs-backup named[22478]: client @0x55ea286f5eb0: udprecv
Oct 21 11:51:08 p-ucs-backup named[22478]: socket 0x7f7bc863cd90: socket_recv: event 0x7f7bc0241148 -> task 0x7f7bc863e590
Oct 21 11:51:08 p-ucs-backup named[22478]: client @0x55ea28704210: udprecv
Oct 21 11:51:08 p-ucs-backup named[22478]: socket 0x7f7bc863cd90: socket_recv: event 0x7f7bc0200148 -> task 0x7f7bc863e640
Oct 21 11:51:08 p-ucs-backup named[22478]: client @0x55ea28712570: udprecv
Oct 21 11:51:08 p-ucs-backup named[22478]: socket 0x7f7bc863cd90: socket_recv: event 0x7f7bc01bf148 -> task 0x7f7bc863e6f0
Oct 21 11:51:08 p-ucs-backup named[22478]: client @0x55ea287208d0: udprecv
Oct 21 11:51:08 p-ucs-backup named[22478]: socket 0x7f7bc863cd90: socket_recv: event 0x7f7bc017e148 -> task 0x7f7bc863e7a0
Oct 21 11:51:08 p-ucs-backup named[22478]: client @0x55ea2872ec30: accept
Oct 21 11:51:08 p-ucs-backup named[22478]: load_configuration: success
Oct 21 11:51:08 p-ucs-backup named[22478]: client @0x55ea28587500: udprecv
Oct 21 11:51:08 p-ucs-backup named[22478]: socket 0x7f7bc863c010: socket_recv: event 0x7f7bc8554148 -> task 0x7f7bc86199b0
Oct 21 11:51:08 p-ucs-backup named[22478]: client @0x55ea285ccfb0: udprecv
Oct 21 11:51:08 p-ucs-backup named[22478]: socket 0x7f7bc863c010: socket_recv: event 0x7f7bc8513148 -> task 0x7f7bc8619a60
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 0.in-addr.arpa/IN: starting load
Oct 21 11:51:08 p-ucs-backup named[22478]: sockmgr 0x7f7bc860c010: watcher got message -3 for socket 512
Oct 21 11:51:08 p-ucs-backup named[22478]: sockmgr 0x7f7bc860c010: watcher got message -3 for socket 20
Oct 21 11:51:08 p-ucs-backup named[22478]: sockmgr 0x7f7bc860c010: watcher got message -3 for socket 513
Oct 21 11:51:08 p-ucs-backup named[22478]: sockmgr 0x7f7bc860c010: watcher got message -3 for socket 21
Oct 21 11:51:08 p-ucs-backup named[22478]: sockmgr 0x7f7bc860c010: watcher got message -3 for socket 514
Oct 21 11:51:08 p-ucs-backup named[22478]: sockmgr 0x7f7bc860c010: watcher got message -3 for socket 22
Oct 21 11:51:08 p-ucs-backup named[22478]: sockmgr 0x7f7bc860c010: watcher got message -3 for socket 515
Oct 21 11:51:08 p-ucs-backup named[22478]: sockmgr 0x7f7bc860c010: watcher got message -3 for socket 23
Oct 21 11:51:08 p-ucs-backup named[22478]: sockmgr 0x7f7bc860c010: watcher got message -2 for socket -1
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 0.in-addr.arpa/IN: number of nodes in database: 1
Oct 21 11:51:08 p-ucs-backup named[22478]: no journal file, but that's OK
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 0.in-addr.arpa/IN: journal rollforward completed successfully: no journal
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 0.in-addr.arpa/IN: loaded; checking validity
Oct 21 11:51:08 p-ucs-backup named[22478]: decrement_reference: delete from rbt: 0x7f7bc8611d78 0.in-addr.arpa
Oct 21 11:51:08 p-ucs-backup named[22478]: zone_settimer: zone 0.in-addr.arpa/IN: enter
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 0.in-addr.arpa/IN: loaded serial 1
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 120.10.in-addr.arpa/IN: starting load
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 120.10.in-addr.arpa/IN: number of nodes in database: 2
Oct 21 11:51:08 p-ucs-backup named[22478]: no journal file, but that's OK
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 120.10.in-addr.arpa/IN: journal rollforward completed successfully: no journal
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 120.10.in-addr.arpa/IN: loaded; checking validity
Oct 21 11:51:08 p-ucs-backup named[22478]: zone_settimer: zone 120.10.in-addr.arpa/IN: enter
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 120.10.in-addr.arpa/IN: loaded serial 6
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 127.in-addr.arpa/IN: starting load
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 127.in-addr.arpa/IN: number of nodes in database: 2
Oct 21 11:51:08 p-ucs-backup named[22478]: no journal file, but that's OK
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 127.in-addr.arpa/IN: journal rollforward completed successfully: no journal
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 127.in-addr.arpa/IN: loaded; checking validity
Oct 21 11:51:08 p-ucs-backup named[22478]: decrement_reference: delete from rbt: 0x7f7bc8611de0 127.in-addr.arpa
Oct 21 11:51:08 p-ucs-backup named[22478]: zone_settimer: zone 127.in-addr.arpa/IN: enter
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 127.in-addr.arpa/IN: loaded serial 1
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 254.169.IN-ADDR.ARPA/IN: starting load
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 254.169.IN-ADDR.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 254.169.IN-ADDR.ARPA/IN: loaded; checking validity
Oct 21 11:51:08 p-ucs-backup named[22478]: zone_settimer: zone 254.169.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 2.0.192.IN-ADDR.ARPA/IN: starting load
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 2.0.192.IN-ADDR.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 2.0.192.IN-ADDR.ARPA/IN: loaded; checking validity
Oct 21 11:51:08 p-ucs-backup named[22478]: zone_settimer: zone 2.0.192.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 168.192.in-addr.arpa/IN: starting load
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 168.192.in-addr.arpa/IN: number of nodes in database: 2
Oct 21 11:51:08 p-ucs-backup named[22478]: no journal file, but that's OK
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 168.192.in-addr.arpa/IN: journal rollforward completed successfully: no journal
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 168.192.in-addr.arpa/IN: loaded; checking validity
Oct 21 11:51:08 p-ucs-backup named[22478]: zone_settimer: zone 168.192.in-addr.arpa/IN: enter
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 168.192.in-addr.arpa/IN: loaded serial 10
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 100.51.198.IN-ADDR.ARPA/IN: starting load
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 100.51.198.IN-ADDR.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 100.51.198.IN-ADDR.ARPA/IN: loaded; checking validity
Oct 21 11:51:08 p-ucs-backup named[22478]: zone_settimer: zone 100.51.198.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 113.0.203.IN-ADDR.ARPA/IN: starting load
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 113.0.203.IN-ADDR.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 113.0.203.IN-ADDR.ARPA/IN: loaded; checking validity
Oct 21 11:51:08 p-ucs-backup named[22478]: zone_settimer: zone 113.0.203.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 255.in-addr.arpa/IN: starting load
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 255.in-addr.arpa/IN: number of nodes in database: 1
Oct 21 11:51:08 p-ucs-backup named[22478]: no journal file, but that's OK
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 255.in-addr.arpa/IN: journal rollforward completed successfully: no journal
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 255.in-addr.arpa/IN: loaded; checking validity
Oct 21 11:51:08 p-ucs-backup named[22478]: decrement_reference: delete from rbt: 0x7f7bc8611e48 255.in-addr.arpa
Oct 21 11:51:08 p-ucs-backup named[22478]: zone_settimer: zone 255.in-addr.arpa/IN: enter
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 255.in-addr.arpa/IN: loaded serial 1
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 255.255.255.255.IN-ADDR.ARPA/IN: starting load
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 255.255.255.255.IN-ADDR.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 255.255.255.255.IN-ADDR.ARPA/IN: loaded; checking validity
Oct 21 11:51:08 p-ucs-backup named[22478]: zone_settimer: zone 255.255.255.255.IN-ADDR.ARPA/IN: enter
Oct 21 11:51:08 p-ucs-backup named[22478]: 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
Oct 21 11:51:08 p-ucs-backup named[22478]: 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: number of nodes in database: 0
Oct 21 11:51:08 p-ucs-backup named[22478]: 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: loaded; checking validity
Oct 21 11:51:08 p-ucs-backup named[22478]: zone_settimer: 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: enter
Oct 21 11:51:08 p-ucs-backup named[22478]: 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/IN: starting load
Oct 21 11:51:08 p-ucs-backup named[22478]: 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/IN: number of nodes in database: 0
Oct 21 11:51:08 p-ucs-backup named[22478]: 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/IN: loaded; checking validity
Oct 21 11:51:08 p-ucs-backup named[22478]: zone_settimer: 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/IN: enter
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 8.B.D.0.1.0.0.2.IP6.ARPA/IN: starting load
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 8.B.D.0.1.0.0.2.IP6.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 8.B.D.0.1.0.0.2.IP6.ARPA/IN: loaded; checking validity
Oct 21 11:51:08 p-ucs-backup named[22478]: zone_settimer: zone 8.B.D.0.1.0.0.2.IP6.ARPA/IN: enter
Oct 21 11:51:08 p-ucs-backup named[22478]: zone D.F.IP6.ARPA/IN: starting load
Oct 21 11:51:08 p-ucs-backup named[22478]: zone D.F.IP6.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:08 p-ucs-backup named[22478]: zone D.F.IP6.ARPA/IN: loaded; checking validity
Oct 21 11:51:08 p-ucs-backup named[22478]: zone_settimer: zone D.F.IP6.ARPA/IN: enter
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 8.E.F.IP6.ARPA/IN: starting load
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 8.E.F.IP6.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 8.E.F.IP6.ARPA/IN: loaded; checking validity
Oct 21 11:51:08 p-ucs-backup named[22478]: zone_settimer: zone 8.E.F.IP6.ARPA/IN: enter
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 9.E.F.IP6.ARPA/IN: starting load
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 9.E.F.IP6.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:08 p-ucs-backup named[22478]: zone 9.E.F.IP6.ARPA/IN: loaded; checking validity
Oct 21 11:51:08 p-ucs-backup named[22478]: zone_settimer: zone 9.E.F.IP6.ARPA/IN: enter
Oct 21 11:51:08 p-ucs-backup named[22478]: zone A.E.F.IP6.ARPA/IN: starting load
Oct 21 11:51:08 p-ucs-backup named[22478]: zone A.E.F.IP6.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:08 p-ucs-backup named[22478]: zone A.E.F.IP6.ARPA/IN: loaded; checking validity
Oct 21 11:51:08 p-ucs-backup named[22478]: zone_settimer: zone A.E.F.IP6.ARPA/IN: enter
Oct 21 11:51:08 p-ucs-backup named[22478]: zone B.E.F.IP6.ARPA/IN: starting load
Oct 21 11:51:08 p-ucs-backup named[22478]: zone B.E.F.IP6.ARPA/IN: number of nodes in database: 0
Oct 21 11:51:08 p-ucs-backup named[22478]: zone B.E.F.IP6.ARPA/IN: loaded; checking validity
Oct 21 11:51:08 p-ucs-backup named[22478]: zone_settimer: zone B.E.F.IP6.ARPA/IN: enter
Oct 21 11:51:08 p-ucs-backup named[22478]: zone finalist.lcl/IN: no master file
Oct 21 11:51:08 p-ucs-backup named[22478]: zone_settimer: zone finalist.lcl/IN: enter
Oct 21 11:51:08 p-ucs-backup named[22478]: zone localhost/IN: starting load
Oct 21 11:51:08 p-ucs-backup named[22478]: zone localhost/IN: number of nodes in database: 1
Oct 21 11:51:08 p-ucs-backup named[22478]: no journal file, but that's OK
Oct 21 11:51:08 p-ucs-backup named[22478]: zone localhost/IN: journal rollforward completed successfully: no journal
Oct 21 11:51:08 p-ucs-backup named[22478]: zone localhost/IN: loaded; checking validity
Oct 21 11:51:08 p-ucs-backup named[22478]: decrement_reference: delete from rbt: 0x7f7bc00fcd30 localhost
Oct 21 11:51:08 p-ucs-backup named[22478]: zone_settimer: zone localhost/IN: enter
Oct 21 11:51:08 p-ucs-backup named[22478]: zone localhost/IN: loaded serial 2
Oct 21 11:51:08 p-ucs-backup named[22478]: managed-keys-zone ./IN: starting load
Oct 21 11:51:08 p-ucs-backup named[22478]: managed-keys-zone ./IN: number of nodes in database: 1
Oct 21 11:51:08 p-ucs-backup named[22478]: managed-keys-zone ./IN: journal rollforward completed successfully: up to date
Oct 21 11:51:08 p-ucs-backup named[22478]: managed-keys-zone ./IN: loaded; checking validity
Oct 21 11:51:08 p-ucs-backup named[22478]: managed-keys-zone ./IN: synchronizing trusted keys
Oct 21 11:51:08 p-ucs-backup named[22478]: decrement_reference: delete from rbt: 0x7f7bc01097a0 .
Oct 21 11:51:08 p-ucs-backup named[22478]: zone_settimer: managed-keys-zone ./IN: enter
Oct 21 11:51:08 p-ucs-backup named[22478]: zone_settimer: managed-keys-zone ./IN: settimer inactive
Oct 21 11:51:08 p-ucs-backup named[22478]: managed-keys-zone ./IN: loaded serial 4
Oct 21 11:51:08 p-ucs-backup named[22478]: zone authors.bind/CH: starting load
Oct 21 11:51:08 p-ucs-backup named[22478]: zone authors.bind/CH: number of nodes in database: 0
Oct 21 11:51:08 p-ucs-backup named[22478]: zone authors.bind/CH: loaded; checking validity
Oct 21 11:51:08 p-ucs-backup named[22478]: zone_settimer: zone authors.bind/CH: enter
Oct 21 11:51:08 p-ucs-backup named[22478]: zone hostname.bind/CH: starting load
Oct 21 11:51:09 p-ucs-backup named[22459]: socket 0x7f8a89247490: dispatch_recv:  event 0x7f8a81096148 -> task 0x7f8a89225dd0
Oct 21 11:51:09 p-ucs-backup named[22459]: socket 0x7f8a89247490: internal_recv: task 0x7f8a89225dd0 got event 0x7f8a89247550
Oct 21 11:51:09 p-ucs-backup named[22459]: socket 0x7f8a89247490 127.0.0.1#30375: packet received correctly
Oct 21 11:51:09 p-ucs-backup named[22459]: socket 0x7f8a89247490: processing cmsg 0x7f8a8920f1c0
Oct 21 11:51:09 p-ucs-backup named[22459]: client 127.0.0.1#30375: UDP request
Oct 21 11:51:09 p-ucs-backup named[22459]: client 127.0.0.1#30375: using view '_default'
Oct 21 11:51:09 p-ucs-backup named[22459]: client 127.0.0.1#30375: request is not signed
Oct 21 11:51:09 p-ucs-backup named[22459]: client 127.0.0.1#30375: recursion available
Oct 21 11:51:09 p-ucs-backup named[22459]: client 127.0.0.1#30375: query
Oct 21 11:51:09 p-ucs-backup named[22459]: client 127.0.0.1#30375: ns_client_attach: ref = 1
Oct 21 11:51:09 p-ucs-backup named[22459]: client 127.0.0.1#30375: query failed (SERVFAIL) for finalist.lcl/IN/SOA at query.c:5851
Oct 21 11:51:09 p-ucs-backup named[22459]: client 127.0.0.1#30375: error
Oct 21 11:51:09 p-ucs-backup named[22459]: client 127.0.0.1#30375: send
Oct 21 11:51:09 p-ucs-backup named[22459]: client 127.0.0.1#30375: sendto
Oct 21 11:51:09 p-ucs-backup named[22459]: client 127.0.0.1#30375: senddone
Oct 21 11:51:09 p-ucs-backup named[22459]: client 127.0.0.1#30375: next
Oct 21 11:51:09 p-ucs-backup named[22459]: client 127.0.0.1#30375: ns_client_detach: ref = 0
Oct 21 11:51:09 p-ucs-backup named[22459]: client 127.0.0.1#30375: endrequest
Oct 21 11:51:09 p-ucs-backup named[22459]: client @0x562440a4d900: udprecv
Oct 21 11:51:09 p-ucs-backup named[22459]: socket 0x7f8a89247490: socket_recv: event 0x7f8a81096148 -> task 0x7f8a89225dd0
Oct 21 11:51:09 p-ucs-backup named[22459]: sockmgr 0x7f8a89218010: watcher got message -3 for socket 513
Oct 21 11:51:09 p-ucs-backup named[22459]: sockmgr 0x7f8a89218010: watcher got message -2 for socket -1
Oct 21 11:51:18 p-ucs-backup named[22459]: req_timeout: request 0x7f8a89229eb0
Oct 21 11:51:18 p-ucs-backup named[22459]: req_send: request 0x7f8a89229eb0
Oct 21 11:51:18 p-ucs-backup named[22459]: req_senddone: request 0x7f8a89229eb0
Oct 21 11:51:18 p-ucs-backup named[22478]: socket 0x7f7bc863c490: dispatch_recv:  event 0x7f7bc04cb148 -> task 0x7f7bc8619d20
Oct 21 11:51:18 p-ucs-backup named[22478]: socket 0x7f7bc863c490: internal_recv: task 0x7f7bc8619d20 got event 0x7f7bc863c550
Oct 21 11:51:18 p-ucs-backup named[22478]: socket 0x7f7bc863c490 127.0.0.1#34797: packet received correctly
Oct 21 11:51:18 p-ucs-backup named[22478]: socket 0x7f7bc863c490: processing cmsg 0x7f7bc86031c0
Oct 21 11:51:18 p-ucs-backup named[22478]: client 127.0.0.1#34797: UDP request
Oct 21 11:51:18 p-ucs-backup named[22478]: client 127.0.0.1#34797: using view '_default'
Oct 21 11:51:18 p-ucs-backup named[22478]: client 127.0.0.1#34797: request is not signed
Oct 21 11:51:18 p-ucs-backup named[22478]: client 127.0.0.1#34797: recursion available
Oct 21 11:51:18 p-ucs-backup named[22478]: client 127.0.0.1#34797: notify
Oct 21 11:51:18 p-ucs-backup named[22478]: client 127.0.0.1#34797: received notify for zone '168.192.in-addr.arpa'
Oct 21 11:51:18 p-ucs-backup named[22478]: zone 168.192.in-addr.arpa/IN: notify from 127.0.0.1#34797: zone is up to date
Oct 21 11:51:18 p-ucs-backup named[22478]: client 127.0.0.1#34797: send
Oct 21 11:51:18 p-ucs-backup named[22478]: client 127.0.0.1#34797: sendto
Oct 21 11:51:18 p-ucs-backup named[22478]: client 127.0.0.1#34797: senddone
Oct 21 11:51:18 p-ucs-backup named[22478]: client 127.0.0.1#34797: next
Oct 21 11:51:18 p-ucs-backup named[22459]: socket 0x7f8a80ca2490: dispatch_recv:  event 0x7f8a80ca4ed8 -> task 0x7f8a80c97bc0
Oct 21 11:51:18 p-ucs-backup named[22459]: socket 0x7f8a80ca2490: internal_recv: task 0x7f8a80c97bc0 got event 0x7f8a80ca2550
Oct 21 11:51:18 p-ucs-backup named[22459]: socket 0x7f8a80ca2490 127.0.0.1#53: packet received correctly
Oct 21 11:51:18 p-ucs-backup named[22459]: socket 0x7f8a80ca2490: processing cmsg 0x7f8a8920f760
Oct 21 11:51:18 p-ucs-backup named[22459]: dispatch 0x5624409af780: got packet: requests 2, buffers 1, recvs 1
Oct 21 11:51:18 p-ucs-backup named[22459]: dispatch 0x5624409af780: got valid DNS message header, /QR 1, id 7376
Oct 21 11:51:18 p-ucs-backup named[22459]: dispatch 0x5624409af780: search for response in bucket 5422: found
Oct 21 11:51:18 p-ucs-backup named[22459]: dispatch 0x5624409af780 response 0x7f8a8924c3b0 127.0.0.1#53: [a] Sent event 0x7f8a89230b50 buffer 0x5624409a2090 len 4096 to task 0x7f8a89225640
Oct 21 11:51:18 p-ucs-backup named[22459]: socket 0x7f8a80ca2490: socket_recv: event 0x7f8a8922a280 -> task 0x7f8a80c97bc0
Oct 21 11:51:18 p-ucs-backup named[22459]: req_response: request 0x7f8a89229eb0: success
Oct 21 11:51:18 p-ucs-backup named[22459]: dispatch 0x5624409af780 response 0x7f8a8924c3b0 127.0.0.1#53: detaching from task 0x7f8a89225640
Oct 21 11:51:18 p-ucs-backup named[22459]: req_cancel: request 0x7f8a89229eb0
Oct 21 11:51:18 p-ucs-backup named[22459]: dispatch 0x5624409af780: detach: refcount 2
Oct 21 11:51:18 p-ucs-backup named[22459]: req_sendevent: request 0x7f8a89229eb0
Oct 21 11:51:18 p-ucs-backup named[22459]: dns_request_getresponse: request 0x7f8a89229eb0
Oct 21 11:51:18 p-ucs-backup named[22459]: zone 168.192.in-addr.arpa/IN: notify response from 127.0.0.1#53: NOERROR
Oct 21 11:51:18 p-ucs-backup named[22459]: dns_request_destroy: request 0x7f8a89229eb0
Oct 21 11:51:18 p-ucs-backup named[22459]: req_destroy: request 0x7f8a89229eb0
Oct 21 11:51:18 p-ucs-backup named[22459]: requestmgr_detach: 0x7f8a80c8b010: eref 1 iref 1
Oct 21 11:51:18 p-ucs-backup named[22459]: sockmgr 0x7f8a89218010: watcher got message -3 for socket 516
Oct 21 11:51:18 p-ucs-backup named[22459]: sockmgr 0x7f8a89218010: watcher got message -2 for socket -1
Oct 21 11:51:18 p-ucs-backup named[22478]: client 127.0.0.1#34797: endrequest
Oct 21 11:51:18 p-ucs-backup named[22478]: sockmgr 0x7f7bc860c010: watcher got message -3 for socket 513
Oct 21 11:51:18 p-ucs-backup named[22478]: sockmgr 0x7f7bc860c010: watcher got message -2 for socket -1
Oct 21 11:51:18 p-ucs-backup named[22478]: client @0x55ea2865c0b0: udprecv
Oct 21 11:51:18 p-ucs-backup named[22478]: socket 0x7f7bc863c490: socket_recv: event 0x7f7bc04cb148 -> task 0x7f7bc8619d20
Oct 21 11:51:19 p-ucs-backup named[22459]: req_timeout: request 0x7f8a80ca6010
Oct 21 11:51:19 p-ucs-backup named[22459]: req_send: request 0x7f8a80ca6010
Oct 21 11:51:19 p-ucs-backup named[22459]: req_senddone: request 0x7f8a80ca6010
Oct 21 11:51:19 p-ucs-backup named[22478]: socket 0x7f7bc863c490: dispatch_recv:  event 0x7f7bc048a148 -> task 0x7f7bc8619dd0
Oct 21 11:51:19 p-ucs-backup named[22478]: socket 0x7f7bc863c490: internal_recv: task 0x7f7bc8619dd0 got event 0x7f7bc863c550
Oct 21 11:51:19 p-ucs-backup named[22478]: socket 0x7f7bc863c490 127.0.0.1#34797: packet received correctly
Oct 21 11:51:19 p-ucs-backup named[22478]: socket 0x7f7bc863c490: processing cmsg 0x7f7bc86031c0
Oct 21 11:51:19 p-ucs-backup named[22478]: client 127.0.0.1#34797: UDP request
Oct 21 11:51:19 p-ucs-backup named[22478]: client 127.0.0.1#34797: using view '_default'
Oct 21 11:51:19 p-ucs-backup named[22478]: client 127.0.0.1#34797: request is not signed
Oct 21 11:51:19 p-ucs-backup named[22478]: client 127.0.0.1#34797: recursion available
Oct 21 11:51:19 p-ucs-backup named[22478]: client 127.0.0.1#34797: notify
Oct 21 11:51:19 p-ucs-backup named[22478]: client 127.0.0.1#34797: received notify for zone '120.10.in-addr.arpa'
Oct 21 11:51:19 p-ucs-backup named[22478]: zone 120.10.in-addr.arpa/IN: notify from 127.0.0.1#34797: zone is up to date
Oct 21 11:51:19 p-ucs-backup named[22478]: client 127.0.0.1#34797: send
Oct 21 11:51:19 p-ucs-backup named[22478]: client 127.0.0.1#34797: sendto
Oct 21 11:51:19 p-ucs-backup named[22478]: client 127.0.0.1#34797: senddone
Oct 21 11:51:19 p-ucs-backup named[22478]: client 127.0.0.1#34797: next
Oct 21 11:51:19 p-ucs-backup named[22459]: socket 0x7f8a80ca2490: dispatch_recv:  event 0x7f8a8922a280 -> task 0x7f8a80c97bc0
Oct 21 11:51:19 p-ucs-backup named[22478]: client 127.0.0.1#34797: endrequest
Oct 21 11:51:19 p-ucs-backup named[22478]: client @0x55ea28675900: udprecv
Oct 21 11:51:19 p-ucs-backup named[22478]: socket 0x7f7bc863c490: socket_recv: event 0x7f7bc048a148 -> task 0x7f7bc8619dd0
Oct 21 11:51:19 p-ucs-backup named[22478]: sockmgr 0x7f7bc860c010: watcher got message -3 for socket 513
Oct 21 11:51:19 p-ucs-backup named[22478]: sockmgr 0x7f7bc860c010: watcher got message -2 for socket -1
Oct 21 11:51:19 p-ucs-backup named[22459]: socket 0x7f8a80ca2490: internal_recv: task 0x7f8a80c97bc0 got event 0x7f8a80ca2550
Oct 21 11:51:19 p-ucs-backup named[22459]: socket 0x7f8a80ca2490 127.0.0.1#53: packet received correctly
Oct 21 11:51:19 p-ucs-backup named[22459]: socket 0x7f8a80ca2490: processing cmsg 0x7f8a8920f760
Oct 21 11:51:19 p-ucs-backup named[22459]: dispatch 0x5624409af780: got packet: requests 1, buffers 1, recvs 1
Oct 21 11:51:19 p-ucs-backup named[22459]: dispatch 0x5624409af780: got valid DNS message header, /QR 1, id 4094
Oct 21 11:51:19 p-ucs-backup named[22459]: dispatch 0x5624409af780: search for response in bucket 987: found
Oct 21 11:51:19 p-ucs-backup named[22459]: dispatch 0x5624409af780 response 0x7f8a8924c498 127.0.0.1#53: [a] Sent event 0x7f8a89230b50 buffer 0x562440e8c9e0 len 4096 to task 0x7f8a892256f0
Oct 21 11:51:19 p-ucs-backup named[22459]: socket 0x7f8a80ca2490: socket_recv: event 0x7f8a80ca4ed8 -> task 0x7f8a80c97bc0
Oct 21 11:51:19 p-ucs-backup named[22459]: sockmgr 0x7f8a89218010: watcher got message -3 for socket 516
Oct 21 11:51:19 p-ucs-backup named[22459]: sockmgr 0x7f8a89218010: watcher got message -2 for socket -1
Oct 21 11:51:19 p-ucs-backup named[22459]: req_response: request 0x7f8a80ca6010: success
Oct 21 11:51:19 p-ucs-backup named[22459]: dispatch 0x5624409af780 response 0x7f8a8924c498 127.0.0.1#53: detaching from task 0x7f8a892256f0
Oct 21 11:51:19 p-ucs-backup named[22459]: req_cancel: request 0x7f8a80ca6010
Oct 21 11:51:19 p-ucs-backup named[22459]: dispatch 0x5624409af780: detach: refcount 0
Oct 21 11:51:19 p-ucs-backup named[22459]: req_sendevent: request 0x7f8a80ca6010
Oct 21 11:51:19 p-ucs-backup named[22459]: dns_request_getresponse: request 0x7f8a80ca6010
Oct 21 11:51:19 p-ucs-backup named[22459]: zone 120.10.in-addr.arpa/IN: notify response from 127.0.0.1#53: NOERROR
Oct 21 11:51:19 p-ucs-backup named[22459]: dns_request_destroy: request 0x7f8a80ca6010
Oct 21 11:51:19 p-ucs-backup named[22459]: req_destroy: request 0x7f8a80ca6010
Oct 21 11:51:19 p-ucs-backup named[22459]: requestmgr_detach: 0x7f8a80c8b010: eref 1 iref 0
Oct 21 11:51:19 p-ucs-backup named[22459]: dispatch 0x5624409af780: got packet: requests 0, buffers 1, recvs 1
Oct 21 11:51:19 p-ucs-backup named[22459]: dispatch 0x5624409af780: shutting down; detaching from sock 0x7f8a80ca2490, task 0x7f8a80c97bc0
Oct 21 11:51:19 p-ucs-backup named[22459]: socket 0x7f8a80ca2490: destroying
Oct 21 11:51:19 p-ucs-backup named[22459]: dispatchmgr 0x7f8a8921c270: destroy_mgr_ok: shuttingdown=0, listnonempty=1, epool=8, rpool=0, dpool=8
Oct 21 11:51:19 p-ucs-backup named[22459]: sockmgr 0x7f8a89218010: watcher got message -5 for socket 516
Oct 21 11:51:19 p-ucs-backup named[22459]: sockmgr 0x7f8a89218010: watcher got message -2 for socket -1

#4

Hey,

that’s a strange problem indeed. Can you please execute the following commands on your DC Master and post their output here:

univention-ldapsearch '(|(relativeDomainName=p-ucs-master)(relativeDomainName=p-ucs-backup))' univention-ldapsearch -b cn=dc,cn=computers,$(ucr get ldap/base) dn aRecord

Kind regards,
mosu


#5

Thanks Mosu,

This is the output.

root@p-ucs-master:~# univention-ldapsearch '(|(relativeDomainName=p-ucs-master)(relativeDomainName=p-ucs-backup))'
# extended LDIF
#
# LDAPv3
# base <dc=finalist,dc=lcl> (default) with scope subtree
# filter: (|(relativeDomainName=p-ucs-master)(relativeDomainName=p-ucs-backup))
# requesting: ALL
#

# p-ucs-master, finalist.lcl, dns, finalist.lcl
dn: relativeDomainName=p-ucs-master,zoneName=finalist.lcl,cn=dns,dc=finalist,d
 c=lcl
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
univentionObjectType: dns/host_record
dNSTTL: 80600
relativeDomainName: p-ucs-master
zoneName: finalist.lcl
aRecord: 192.168.0.154

# p-ucs-backup, finalist.lcl, dns, finalist.lcl
dn: relativeDomainName=p-ucs-backup,zoneName=finalist.lcl,cn=dns,dc=finalist,d
 c=lcl
objectClass: top
objectClass: dNSZone
objectClass: univentionObject
aRecord: 10.120.10.9
univentionObjectType: dns/host_record
relativeDomainName: p-ucs-backup
zoneName: finalist.lcl

# search result
search: 3
result: 0 Success

# numResponses: 3
# numEntries: 2
root@p-ucs-master:~# univention-ldapsearch -b cn=dc,cn=computers,$(ucr get ldap/base) dn aRecord
# extended LDIF
#
# LDAPv3
# base <cn=dc,cn=computers,dc=finalist,dc=lcl> with scope subtree
# filter: (objectclass=*)
# requesting: dn aRecord 
#

# dc, computers, finalist.lcl
dn: cn=dc,cn=computers,dc=finalist,dc=lcl

# p-ucs-backup, dc, computers, finalist.lcl
dn: cn=p-ucs-backup,cn=dc,cn=computers,dc=finalist,dc=lcl
aRecord: 10.120.10.9

# p-ucs-master, dc, computers, finalist.lcl
dn: cn=p-ucs-master,cn=dc,cn=computers,dc=finalist,dc=lcl
aRecord: 192.168.0.154

# search result
search: 3
result: 0 Success

# numResponses: 4
# numEntries: 3

#6

Hey,

alright, that looks good so far. Please re-run the same commands on the DC Backup and paste their output here.

Additionally please make sure that the Directory Listener mechanism is still up-to-date on the DC Backup. For that compare the content (a single number) of the file “/var/lib/univention-ldap/last_id” on the DC Master with the content of the file “/var/lib/univention-directory-listener/notifier_id” on the DC Backup. They should match.

Kind regards,
mosu


#7

Hi,

The last_id and notifier_id are equal.

From the backup server:

root@p-ucs-backup:~# univention-ldapsearch '(|(relativeDomainName=p-ucs-master)(relativeDomainName=p-ucs-backup))'
# extended LDIF
#
# LDAPv3
# base <dc=finalist,dc=lcl> (default) with scope subtree
# filter: (|(relativeDomainName=p-ucs-master)(relativeDomainName=p-ucs-backup))
# requesting: ALL
#

# search result
search: 3
result: 0 Success

# numResponses: 1
root@p-ucs-backup:~# univention-ldapsearch -b cn=dc,cn=computers,$(ucr get ldap/base) dn aRecord
# extended LDIF
#
# LDAPv3
# base <cn=dc,cn=computers,dc=finalist,dc=lcl> with scope subtree
# filter: (objectclass=*)
# requesting: dn aRecord 
#

# dc, computers, finalist.lcl
dn: cn=dc,cn=computers,dc=finalist,dc=lcl

# p-ucs-backup, dc, computers, finalist.lcl
dn: cn=p-ucs-backup,cn=dc,cn=computers,dc=finalist,dc=lcl
aRecord: 10.120.10.9

# p-ucs-master, dc, computers, finalist.lcl
dn: cn=p-ucs-master,cn=dc,cn=computers,dc=finalist,dc=lcl
aRecord: 192.168.0.154

# search result
search: 3
result: 0 Success

# numResponses: 4
# numEntries: 3

#8

Hey,

well, the first command from the DC Backup shows that the LDAP server content is incomplete compared to the DC Master, even though the listener IDs are identical. I don’t want to hazard a guess as to why that’s the case.

I suggest you simply re-join the DC Backup to the domain by running “univention-join” on the DC Backup. During that process the whole LDAP directory will be copied from the master.

Kind regards,
mosu


#9

Hi Mosu,

The rejoin failed with the following message:

root@p-ucs-backup:~/.ssh# univention-join
univention-join: joins a computer to an ucs domain
copyright (c) 2001-2016 Univention GmbH, Germany

Enter DC Master Account : root
Enter DC Master Password: 

Search DC Master:                                          done
Check DC Master:                                           done
Stop LDAP Server:                                          done
Stop Samba Server:                                         done
Search ldap/base                                           done
Start LDAP Server:                                         done
Search LDAP binddn Insufficient access (50)


**************************************************************************
* Join failed!                                                           *
* Contact your system administrator                                      *
**************************************************************************
* Message:  binddn for user root not found. 
**************************************************************************

#10

You have to use the account ‘Administrator’ (or an other Domain Admin account) and not the local root user.


#11

It also fails with my account. The user is in the Domain Admins group.

root@p-ucs-backup:~/.ssh# univention-join
univention-join: joins a computer to an ucs domain
copyright (c) 2001-2016 Univention GmbH, Germany

Enter DC Master Account : remko.gerbranda
Enter DC Master Password: 

Search DC Master:                                          done
Check DC Master:                                           done
Stop LDAP Server:                                          done
Stop Samba Server:                                         done
Search ldap/base                                           done
Start LDAP Server:                                         done
Search LDAP binddn ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)
Insufficient access (50)


**************************************************************************
* Join failed!                                                           *
* Contact your system administrator                                      *
**************************************************************************
* Message:  binddn for user remko.gerbranda not found. 
**************************************************************************

#12

Hey,

use “administrator”.

Kind regards,
mosu


#13

Hi Mosu,

Thanks for your support. The issue is solved.

I used ‘administrator’ to perform the join.

Actually this is an answer to my earlier question: removal of user ‘Administrator’ (Removal of user “Administrator”)

This user is required for the join. Maybe renaming works, but removal will break the join functionality.


#14

Hey.

great! Have a nice weekend.

Kind regards,
mosu