Univention Bugzilla – Bug 31103
In DNS Pointer Objekten werden nicht alle pTRRecords angezeigt
Last modified: 2013-04-19 12:45:58 CEST
Join of a DC Backup failed with this fix: root@backup612:~# /usr/share/univention-admin-tools/univention-dnsedit --ignore-exists --reverse 10.201 add ptr 2.61 backup612.deadlock61.local. Adding PTR record "2.61 backup612.deadlock61.local." to zone 10.201... E: Record exists and points to different address Since the PTR record is a list the check in univention-dnsedit fails: if record['ptr_record'] and not (record['ptr_record'] == ptr or +++ This bug was initially created as a clone of Bug #28667 +++ Created an attachment (id=4693) PTR Record Objekt (UMC) Zum Reproduzieren: Rechnerobjekt mit einer IP, einer DNS Reverse Zone und zwei DNS Forward Zonen anlegen. =============================================================================== # univention, computers, fghj.klyx dn: cn=univention,cn=computers,dc=fghj,dc=klyx cn: univention krb5PrincipalName: host/univention.fghj.klyx@FGHJ.KLYX objectClass: top objectClass: person objectClass: univentionHost objectClass: univentionDomainController objectClass: krb5Principal objectClass: krb5KDCEntry objectClass: posixAccount objectClass: shadowAccount objectClass: sambaSamAccount objectClass: univentionVirtualMachineHostOC objectClass: univentionObject uidNumber: 2008 sambaAcctFlags: [S ] krb5MaxLife: 86400 uid: univention$ krb5MaxRenew: 604800 aRecord: 10.200.28.10 loginShell: /bin/bash univentionObjectType: computers/domaincontroller_slave univentionServerReinstall: 0 krb5KDCFlags: 126 univentionServerRole: slave univentionServerInstallationText: 0 displayName: univention associatedDomain: fghj.klyx sambaSID: S-1-5-21-1220308194-3346195381-2222997512-5016 krb5KeyVersionNumber: 1 sn: univention univentionNetworkLink: cn=default,cn=networks,dc=fghj,dc=klyx homeDirectory: /dev/null gidNumber: 5006 sambaPrimaryGroupSID: S-1-5-21-1220308194-3346195381-2222997512-11013 # univention, fghj.klyx, dns, fghj.klyx dn: relativeDomainName=univention,zoneName=fghj.klyx,cn=dns,dc=fghj,dc=klyx objectClass: top objectClass: dNSZone aRecord: 10.200.28.10 relativeDomainName: univention zoneName: fghj.klyx # univention, test.example, dns, fghj.klyx dn: relativeDomainName=univention,zoneName=test.example,cn=dns,dc=fghj,dc=klyx objectClass: top objectClass: dNSZone aRecord: 10.200.28.10 relativeDomainName: univention zoneName: test.example # 10, 28.200.10.in-addr.arpa, dns, fghj.klyx dn: relativeDomainName=10,zoneName=28.200.10.in-addr.arpa,cn=dns,dc=fghj,dc=kl yx objectClass: top objectClass: dNSZone relativeDomainName: 10 pTRRecord: univention.fghj.klyx. <------------- pTRRecord: univention.test.example. <------------- zoneName: 28.200.10.in-addr.arpa =============================================================================== Die UMC zeigt beim Betrachten des Reverse Pointers aber nur einen davon an (siehe Screenshot).
YAML: 2013-04-18-univention-directory-manager-modules.yaml Fixed in 8.0.143-12.1005.201304182046 for 3.1-1-errata and 8.0.152-1.1004.201304182046 for 3.1-2.
(In reply to comment #1) > YAML: 2013-04-18-univention-directory-manager-modules.yaml > > Fixed in 8.0.143-12.1005.201304182046 for 3.1-1-errata and > 8.0.152-1.1004.201304182046 for 3.1-2. Functionality: 3.1-1-errata: OK 3.1-2: OK Changelog: OK YAML: OK SVN: OK
http://errata.univention.de/ucs/3.1/91.html