Univention Bugzilla – Bug 33114
No LDAP SRV records in S4 domains with subdomains created - stalls join for 10m
Last modified: 2020-07-03 20:53:58 CEST
I've installed a Master with Samba 4 and a Slave without Samba 4. The Master uses deadlock29.local as dns domain, the slave uses subdom.deadlock29.local. During the Slave installation the LDAP SRV records are not created because the slave don't register these records in a S4 domain. That is OK but the 90univention-bind-post.inst waits for the LDAP SRV record creation in the subdomain.
1. Sub-domains are currently broken in USS: Bug #40078 management/univention-ldap/10univention-ldap-server.inst contains this: 82 »···»···/usr/share/univention-admin-tools/univention-dnsedit "$@" --ignore-exists \ 83 »···»···»···"$domainname" add srv ldap tcp 0 100 7389 "$hostname.$domainname." || die ... 87 »···»···/usr/share/univention-directory-manager-tools/univention-dnsedit "$@" --ignore-exists \ 88 »···»···»···"$domainname" remove srv ldap tcp 0 100 7389 "$hostname.$domainname." || die 2. Two different paths for the same tool should be harmonized: # ls -gGd /usr/share/univention-admin-tools /usr/share/univention-directory-manager-tools /usr/share/univention-admin-tools -> univention-directory-manager-tools /usr/share/univention-directory-manager-tools 3. univention-join -dcname master42.$domainname -dcaccount Administrator -dcpwd <(echo univention) hangs in 90univention-bind-post.inst for 10m as described in the original BUG report; after that the missing SRV records are ignored. 4. univention-fix-ucr-dns also fails, as it is unable to find "subdomain.$domain" on the master(!) and this re-configures the Master as a forwarder, as no SRV-RR "_domaincontroller_master._tcp.subdomain.$domain" exists! (original Bug #43217) 5. Later 92univention-management-console-web-server.inst fails as the UDP metadata cannot be downloaded: Could not download IDP metadata for https://ucs-sso.subdomain.$domain/simplesamlphp/saml2/idp/metadata.php
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.