I creates some DNS entries through CLI; UMC-Web shows 'dc0' twice, once with IP addresses, once without: request: {"options":{"superordinate":"zoneName=phahn.test,dc=pt42m,dc=intranet","hidden":false,"objectType":"dns/dns","objectProperty":"None","objectPropertyValue":"","container":"zoneName=phahn.test,dc=pt42m,dc=intranet","scope":"one","fields":["name","$value$","labelObjectType"]},"flavor":"dns/dns"} response: {"status": 200, "message": null, "result": [ {"$dn$": "relativeDomainName=dc0,zoneName=phahn.test,dc=pt42m,dc=intranet", "name": "dc0", "$value$": [["192.168.122.4", "2001:4dd0:ff00:8c42:ff17:0123:4567:89ab"]], "$childs$": false, "labelObjectType": "Host Record", "path": "intranet.pt42m:/phahn.test", "$operations$": ["add", "edit", "remove", "search"], "$flags$": [], "objectType": "dns/host_record"}, {"$dn$": "relativeDomainName=dc0,zoneName=phahn.test,dc=pt42m,dc=intranet", "name": "dc0", "$value$": [null], "$childs$": false, "labelObjectType": "Host Record", "path": "intranet.pt42m:/phahn.test", "$operations$": ["add", "edit", "remove", "search"], "$flags$": [], "objectType": "dns/host_record"}]}
Is UDM CLI showing it twice, too? How did you create it?
The problem is that this object is detected as dns/txt_record and dns/host_record. There is somewhere already a bug for this. root@dc0:~# udm dns/txt_record list --superordinate zoneName=phahn.test,dc=pt42m,dc=intranet DN: relativeDomainName=dc0,zoneName=phahn.test,dc=pt42m,dc=intranet ARG: None txt: Text name: dc0 zonettl: 3 hours root@dc0:~# udm dns/host_record list --superordinate zoneName=phahn.test,dc=pt42m,dc=intranet DN: relativeDomainName=dc0,zoneName=phahn.test,dc=pt42m,dc=intranet ARG: None a: 192.168.122.4 a: 2001:4dd0:ff00:8c42:ff17:0123:4567:89ab txt: Text mx: 10 dc0.pt42m.intranet name: dc0 zonettl: 3 hours
Created attachment 8655 [details] Screenshot
I thinks this is the reverse of Bug #36642
*** Bug 39864 has been marked as a duplicate of this bug. ***
Fixed with git:18746283071edd46d06602f4b76c621949d43874 since UCS 4.2 July 2017 *** This bug has been marked as a duplicate of bug 40839 ***