Univention Bugzilla – Bug 56956
S4 Connector joinscript DNS sync prioritization should be more specific
Last modified: 2024-01-31 15:39:43 CET
Created attachment 11170 [details] Sync.patch In the joinscript 97univention-s4-connector.inst, certain kinds of objects are prioritized, so that all necessary objects (e.g. DNS objects) are synced to Samba4 first, without having to wait for all users etc. We prioritize all DNS objects, but that is not specific enough for some customers. One customer had so many DNS objects, they are only synced after ~10 hours. The attached patch reduced the join time from 20 hours with a failed joinscript to 10 hours and a successful completion. I am not sure if this should be part of the products, since the caveat is that the s4connector will be occupied for the next few hours. But that has been the case before. The time difference can be a lot though, especially in big environments.
Maybe we can also slim down the generic prioritization `objectClass=dNSZone` to just "(|(univentionObjectType=dns/forward_zone)(univentionObjectType=dns/reverse_zone))". Unfortunately in the OpenLDAP schema, all DNS objects match objectclass=dNSZone. If we do that, then we probably also need to explicitly prioritize "(|(univentionObjectType=dns/srv_record)(univentionObjectType=dns/alias))" to get the AD-specific records over early enough.
555748bfa0 | Improve prioritization for initial S4-Connector sync Package: univention-s4-connector Version: 14.0.16-3 Branch: ucs_5.0-0 Scope: errata5.0-6
OK - univention-s4-connector OK - yaml OK - tests
<https://errata.software-univention.de/#/?erratum=5.0x934>