Bug 33472 - Inappropriate "Address" for PTR RRs
Inappropriate "Address" for PTR RRs
Product: UCS
Classification: Unclassified
Component: UMC - DNS
UCS 3.1
Other Linux
: P5 normal (vote)
: UCS 3.x
Assigned To: UMC maintainers
: 36646 (view as bug list)
Depends on:
Blocks: 41559
  Show dependency treegraph
Reported: 2013-11-19 12:42 CET by Philipp Hahn
Modified: 2017-08-08 07:09 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.069
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Usability
Max CVSS v3 score:


Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2013-11-19 12:42:42 CET
When adding a new PTR RR the input filed is lables as "Adresse (*)" - what actually is expected there is the reverse-prefix.
For a class-C-network entering the octet is somehow guessable, but for class-A and B networks the next question is, if I as a user have to do the reversal or if UDM will do it.

Currently the syntax is a simple syntax=univention.admin.syntax.string, which allows to create invalid DNS entries.

Almost every else we hide the gory details of DNS zones from the user.

1. The input field should be restricted to valid IPv[46] addresses in forward-notation, from which the right "name" is calculated.
2. It should be pre-filled with the right value determined from the containing reverse zone when creating a new entry.
3. A helpful long_description should be added.
Comment 1 Philipp Hahn univentionstaff 2014-11-13 16:51:52 CET
*** Bug 36646 has been marked as a duplicate of this bug. ***
Comment 2 Stefan Gohmann univentionstaff 2017-06-16 20:36:24 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 3 Stefan Gohmann univentionstaff 2017-08-08 07:09:50 CEST
This issue has been filed against UCS 3.1.

UCS 3.1 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.