Bug 41030 – Naming of UDM DNS objects is confusing (e.g., UDM DNS Alias record == CNAME record)

Bug 41030 - Naming of UDM DNS objects is confusing (e.g., UDM DNS Alias record == CNAME record)


Summary:	Naming of UDM DNS objects is confusing (e.g., UDM DNS Alias record == CNAME r...

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UMC - DNS
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-04-11 17:58 CEST by Nico Stöckigt
Modified:	2019-01-03 07:18 CET (History)
CC List:	2 users (show)

See Also:	41004 41003
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	External feedback, Usability
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Nico Stöckigt

2016-04-11 17:58:12 CEST

Customer feels lost when trying to create a CNAME record (Ticket#2016041121000206).

a CNAME record is called ALIAS and even the creation form is not fully clear what values to enter where. A better inline help/hint would be usefull.

For ALIAS (CNAME) as well for 'Host Record's the rfc names should be used (at leased within brackets). Also it is not clear that IPv4 (A) and also IPv6 (AAAA) can be entered at the Host Record form.

Comment 1 Stefan Gohmann

2019-01-03 07:18:20 CET

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.