Bug 30890 - 10univention-ldap-server.inst should not add 7398 to _ldap._tcp service record
10univention-ldap-server.inst should not add 7398 to _ldap._tcp service record
Status: CLOSED DUPLICATE of bug 29462
Product: UCS
Classification: Unclassified
Component: LDAP
UCS 3.1
Other Linux
: P5 normal (vote)
: UCS 3.2
Assigned To: Stefan Gohmann
Arvid Requate
: interim-1
Depends on:
  Show dependency treegraph
Reported: 2013-03-25 09:03 CET by Janis Meybohm
Modified: 2013-11-19 06:41 CET (History)
2 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Note You need to log in before you can comment on or make changes to this bug.
Description Janis Meybohm univentionstaff 2013-03-25 09:03:03 CET
10univention-ldap-server.inst should no longer add "$hostname.$domainname." with Port 7398 to the _ldap._tcp service record.

In S4 environments this leads to two different directory services (AD and LDAP) in the service record. In non S4 environments, Port 389 should be used instead.
Comment 1 Moritz Muehlenhoff univentionstaff 2013-05-31 10:44:23 CEST
We will not ship a UCS 3.1-2 release; the next UCS release will be UCS 3.2.

As such, this bug is moved to the new target milestone.
Comment 2 Stefan Gohmann univentionstaff 2013-07-10 10:29:51 CEST
Arvid fixed it already.

*** This bug has been marked as a duplicate of bug 29462 ***
Comment 3 Arvid Requate univentionstaff 2013-08-19 16:25:26 CEST
10univention-ldap-server.inst now doesn't add the record any longer in case DCs with service "Samba 4" are found. On the first Samba4-DC in the domain the record is still created, but get's removed later during join of unviention-samba4.
Comment 4 Stefan Gohmann univentionstaff 2013-11-19 06:41:38 CET
UCS 3.2 has been released:

If this error occurs again, please use "Clone This Bug".