Bug 44027 – IPv6 Dualstack: after creation of a ipv6 reverse zone, the zones cannot be changed anymore (only in UMC)

Bug 44027 - IPv6 Dualstack: after creation of a ipv6 reverse zone, the zones cannot be changed anymore (only in UMC)


Summary:	IPv6 Dualstack: after creation of a ipv6 reverse zone, the zones cannot be ch...

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:	UMC maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-03-22 13:06 CET by Jens Thorp-Hansen
Modified:	2019-01-03 07:22 CET (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?:	3: Will affect average number of installed domains
How will those affected feel about the bug?:	3: A User would likely not purchase the product
User Pain:	0.206
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2017032221000203
Bug group (optional):
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 Jens Thorp-Hansen

2017-03-22 13:06:51 CET

In a dualstack setting (ipv4 and ipv6) the UMC seems to have problems with the ipv6 reverse zone. When you create such a reverse zone, you cannot change to the zones in the UMC - the menus do not open. That happens at the DNS and the LDAP section of the UMC.

Workaround is using the UDM, that seems to work.

Comment 1 Stefan Gohmann

2019-01-03 07:22:38 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.