Univention Bugzilla – Bug 50662
univention-bind-ldap does not start if many zones are configured
Last modified: 2021-11-24 23:01:28 CET
On a large customer environment with around 200 DNS zones the univention-bind-ldap fails to start because of long time (approx 1 minute) to load the zones. The service has a ExecStartPost configured: /usr/lib/univention-bind/ldap wait-for-startup which waits for 30sec for the bind to start up and tests with rndc. In customer environment this prevented univention-bind-ldap to start and therefore DNS was not working and used outdated zone information. Increasing the timeout in the above file to 120 (instead of 30) resulted in proper start of both bind services. Only applies to UCRV dns/backend=ldap!
This is imho critical for larger UCS@school environments
> This is imho critical for larger UCS@school environments Ok, but aren't they usually running Samba? Then dns/backend=samba4 is the default that should not be changed.
Central Slaves (non-school-servers) and special-use Backups usually don't have Samba installed.
Package: univention-bind Version: 13.0.1-8A~4.4.4.202003301127 Branch: ucs_4.4-0 Scope: errata4.4-4 A timeout for the startup was made configurable via config variable 'dns/timeout-start'
OK: build and installation OK: yaml OK: ucr variable dns/timeout-start tested - verified -
<http://errata.software-univention.de/ucs/4.4/503.html>