Univention Bugzilla – Bug 49196
Add Diagnostic plugin to check for issues with the legacy DNS-Zone location in Samba/AD
Last modified: 2020-12-07 09:05:35 CET
We should add Diagnostic plugin to check for issues with the legacy DNS-Zone location in Samba/AD: There are two specific problem indicators: * Problem 1: connector/s4/mapping/dns/position is not set to legacy, even though there are is a forward DNS zone in the legacy position. In that case, bind9 takes the legacy data, but the S4-Connector doesn't sync it and you have an inconsistent situation with respect to UDM/OpenLDAP and the view in UMC. * Problem 2: There have been cases where samba_dnsupdate wrote a single object "DC=_msdcs" into the forward DNS zone at the legacy position (CN=MicrosoftDNS,CN=System). If that happened, the bind9 server refuses to resolve records like "gc._msdcs.$(hostname -d)" even they are present in the DNS zone (and shown in zone transfers, e.g. host -al). Both situations should be detectable quite clearly. And at least the second one can be resolved easily with a "fix it" button. If this happens, we should ad a link to and SDB article with addtinal explanation, because, especially in the first situation, manual work is required to merge the DNS data into a consistent state again. https://help.univention.com/t/dns-probleme-im-samba4/7193 would be a possible candidate for this SDB article but maybe we also need a more specialized article for that.
This issue has been filed against UCS 4.2. UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.
This is still relevant so I increased the UCS version