Bug 23820 - IP Adressen aller Samba4 DCs sind am Foreward-Zone-Objekt hinterlegt
IP Adressen aller Samba4 DCs sind am Foreward-Zone-Objekt hinterlegt
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Samba4
UCS 3.0
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: Bugzilla Mailingliste
:
Depends on: 23481
Blocks:
  Show dependency treegraph
 
Reported: 2011-09-26 18:18 CEST by Arvid Requate
Modified: 2016-10-11 08:02 CEST (History)
1 user (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:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2011-09-26 18:18:23 CEST
Im Moment werden für Bug 23481 alle IP-Adressen aller Samba4 DCs an das Zonen-Objekt der Forward-Zone  hinzugefügt. Es sollte noch geklärt werden, ob das in verteilten Umgebungen zu Problemen führt, wenn Windows-Clients für die GPO-Evaluation beliebige DCs verwenden. Wenn möglich könnte das per Sites gesteuert werden.

root@master5:/usr/share/doc/bind9# host deadlock5.local
deadlock5.local has address 10.201.5.2
deadlock5.local has address 10.201.5.3
deadlock5.local has address 10.201.5.1
root@master5:/usr/share/doc/bind9# host deadlock5.local
deadlock5.local has address 10.201.5.1
deadlock5.local has address 10.201.5.2
deadlock5.local has address 10.201.5.3

root@master5:/usr/share/doc/bind9# univention-ldapsearch -LLL -b
cn=dns,dc=deadlock5,dc=local zoneName=deadlock5.local -s one aRecord
dn: zoneName=deadlock5.local,cn=dns,dc=deadlock5,dc=local
aRecord: 10.201.5.1
aRecord: 10.201.5.2
aRecord: 10.201.5.3

+++ This bug was initially created as a clone of Bug #23481 +++
Comment 1 Stefan Gohmann univentionstaff 2016-10-11 08:02:24 CEST
This issue has been filed against UCS 3.0.

UCS 3.0 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please reopen.