Univention Bugzilla – Bug 33043
IP change does not automatically update reverse zone
Last modified: 2018-04-13 13:29:23 CEST
UDM compute objects provides a reference to the DNS reverse zone object object as a LDAP dn in obj.info['dnsEntryZoneReverse']. When changing the IP address by modifying obj.info['ip'], this entry is not automatically updated and - even worse - prevents the update when the new IP address is located in a different subnet. It must be updated manually. As this information is not stored in LDAP, UDM should update that reference by itself. In the UMC frontent: For a selected "DNS reverse zone" only those IP adresses should be shown in the "IP address" combo-box, which are valid for that zone. Otherwise the user gets the following error message after saving the changes: > Reverse zone and IP address are incompatible PS: simpleComputer already has a cleanup() method, which looks like it is doing the required updates. Unfortunately is calls .open() as its first action, which makes is unusable for doing a cleanup of an already existing object.
In my tests, I changed via UDM (CLI and UMC) a DC slave's IP address (same subnet), and this change was also correctly reflected into the reverse zone.
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4. If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
This issue has been filed against UCS 3.2. UCS 3.2 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 use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.