Univention Bugzilla – Bug 41004
UMC - DNS column "type" more detailed (A CNAME MX TXT AAAA) or additional column
Last modified: 2019-02-06 11:31:38 CET
Currently it is at times not clear which type of record that is: A CNAME MX TXT AAAA - that should be made clear with an additional column or better naming. Ticket#2016040421000274
This seems to be fixed with UCS 4.1 Errata 131-133. An additional column is shown.
(In reply to Nico Stöckigt from comment #1) > This seems to be fixed with UCS 4.1 Errata 131-133. An additional column is > shown. The column doesn't show if it is an A / AAAA / MX / TXT record. It says only 'host' record which is an invention by us.
(In reply to Florian Best from comment #2) > The column doesn't show if it is an A / AAAA / MX / TXT record. It says only > 'host' record which is an invention by us. Should that not be clear be the naming of the UDM object type itself? I would strongly vote for using correct names for DNS records in UDM such that new users will be able to understand the object types directly, i.e.: Alias Record → CNAME Host Record → A/AAAA
(In reply to Florian Best from comment #2) > The column doesn't show if it is an A / AAAA / MX / TXT record. It says only > 'host' record which is an invention by us. That's wrong. It's an "unvention" and should be dumped as soon as possible.
(In reply to Alexander Kläser from comment #3) > (In reply to Florian Best from comment #2) > > The column doesn't show if it is an A / AAAA / MX / TXT record. It says only > > 'host' record which is an invention by us. > > Should that not be clear be the naming of the UDM object type itself? > I would strongly vote for using correct names for DNS records in UDM such > that new users will be able to understand the object types directly, i.e.: > > Alias Record → CNAME > Host Record → A/AAAA Host record is A/AAAA/TXT/MX ! Service Record → SRV Pointer Record → PTR
There is a Customer ID set so I set the flag "Enterprise Customer affected".
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018. Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.