Univention Bugzilla – Bug 45100
Whitespaces are not stripped from user entry yielding in stopped DNS service
Last modified: 2024-03-04 16:12:42 CET
A user reported at Ticket#2017072021000272 Creating a DNS entry with the setting `Forward Lookup Zone` does check for included whitespaces. Appending a white space at the end puts it into the configuration of the nameserver and results in a nameserver going offline. Error occurred with UCS 4.2-0 errata95 The syslog provides the following error messages: Jul 20 00:06:56 sr-master-01 named[4026]: zone blackboardXXXX.XXXX.de\032/NONE: has 0 SOA records Jul 20 00:06:56 sr-master-01 named[4026]: zone blackboardXXXX.XXXX.de\032/NONE: has no NS records Jul 20 00:06:56 sr-master-01 named[4026]: samba_dlz: Failed to configure zone 'blackboardXXXX.XXXX.de ' Jul 20 00:06:56 sr-master-01 named[4026]: loading configuration: bad zone Jul 20 00:06:56 sr-master-01 named[4026]: exiting (due to fatal error)
A not runnning DNS service is a 7-crash.
MR: https://git.knut.univention.de/univention/ucs/-/merge_requests/844
Another customer reported something similar with UCS 5.0-5 errata813. Create a Forward Zone with an included space character is possible with UMC. This resulted in a stopped bind service. snip from syslog (forward zone "Space Zone" on a test machine): Oct 12 13:56:18 mf2primary named[13978]: zone Space\032Zone/NONE: has 0 SOA records Oct 12 13:56:18 mf2primary named[13978]: zone Space\032Zone/NONE: has no NS records Oct 12 13:56:18 mf2primary named[13978]: samba_dlz: Failed to configure zone 'Space Zone' Oct 12 13:56:18 mf2primary named[13978]: loading configuration: bad zone Oct 12 13:56:18 mf2primary named[13978]: exiting (due to fatal error) Bug was reproducible with 5.0-5 errata830.
We were in the situation that on a replica the DNS was down and not willing to start. So without DNS no replication -> the correction (deleting that zone spaces in the name) would not arrive on the replica. We switched to dns/backend=ldap and bind was willing to start again. We switched back to samba4 as dns/backend after the replication of the zone had arrived. Perhaps it helps others.
*** This bug has been marked as a duplicate of bug 50385 ***