OK, valid point. For now, until we publish a fix, dnsForward/ReverseZone and dhcpServer must be set explicitly if a custom IP is used with a network. btw. why does the customer need to assign a network at all if nothing from it isn't used at all?
I apologize if there was not enough information on the bug. I have been able to reproduce the customer statement on my test system and no DNS entries are created for the object that I previously created correctly via UDM. My Test-System: univention-app info UCS: 5.0-6 errata974 ucr search --brief role samba4/role: DC server/role: domaincontroller_master system/setup/boot/select/role: true I add attachments to clarify the failure. Used commands to create the object: udm computers/ipmanagedclient create --position "cn=memberserver,cn=computers,dc=miro,dc=intranet" --set name="test30UDM" --set ip="172.168.178.30" --set network="cn=UCS-Net,cn=networks,dc=miro,dc=intranet" udm computers/ipmanagedclient list --filter cn=test30UDM cn=test30UDM DN: cn=test30UDM,cn=memberserver,cn=computers,dc=miro,dc=intranet description: None domain: None fqdn: None ip: 172.168.178.30 name: test30UDM network: cn=UCS-Net,cn=networks,dc=miro,dc=intranet ---------------------------------------------------------- udm computers/ipmanagedclient create --position "cn=memberserver,cn=computers,dc=miro,dc=intranet" --set name="testUDM" --set ip="172.168.178.11" --set network="cn=UCS-Net,cn=networks,dc=miro,dc=intranet" After i add the DNS entries manually via UMC, i get of course the DNS Settings, but this is the regression at this point. udm computers/ipmanagedclient list --filter cn=testUDM cn=testUDM DN: cn=testUDM,cn=memberserver,cn=computers,dc=miro,dc=intranet description: None dnsEntryZoneForward: zoneName=ucs-net.intranet,cn=dns,dc=miro,dc=intranet 172.168.178.11 dnsEntryZoneReverse: zoneName=178.168.172.in-addr.arpa,cn=dns,dc=miro,dc=intranet 172.168.178.11 domain: ucs-net.intranet fqdn: testUDM.ucs-net.intranet ip: 172.168.178.11 name: testUDM network: cn=UCS-Net,cn=networks,dc=miro,dc=intranet ----------------------------------------------------------- In the past we had 2 errata updates for the UDM, so those could be the source for the failure. https://errata.software-univention.de/#/?erratum=5.0x740 https://errata.software-univention.de/#/?erratum=5.0x739 Information from the customer, before the updates were installed, the DNS entries were created correctly. He compared it with a system UCS 5.0-4 errata 726 on which it works correctly.
Created attachment 11200 [details] test30UDM_none_dns_entries_after_create
Created attachment 11201 [details] testUDM_with_dns_entries_manually_added
univention-directory-manager-modules (15.0.27-2) 2084f4f7fbeb | fix(udm): Fix wrong relativeDomainName assignment ucs-test (10.0.22-9) 29cf5bff75e0 | test(udm): Add tests to check DNS objects after IP assignment Successful build Package: univention-directory-manager-modules Version: 15.0.27-2 Branch: 5.0-0 Scope: errata5.0-8 When the IP address is set when creating a new computer object, the DNS entries for this object were not set correctly since erratum 738. The DNS entries will now be created correctly again. Tests were added to verify that the IP address assignment does work as intended in the future.
OK - univention-directory-manager-modules (15.0.27-2) OK - tests OK - yaml
<https://errata.software-univention.de/#/?erratum=5.0x1071>