Bug 40746 - Add option to automatically create DNS reverse entries on A record creation
Add option to automatically create DNS reverse entries on A record creation
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - DNS
UCS 4.1
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-22 15:31 CET by Florian Best
Modified: 2019-01-03 07:18 CET (History)
1 user (show)

See Also:
What kind of report is it?: Feature Request
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

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2016-02-22 15:31:47 CET
There should be an option/check to create a Pointer (PTR-Record) automatically when creating a DNS Host entry (A/AAAA record) for the forward zone.

We need to clarify the following question before implementing this feature:
Every PTR-Record needs a Superordinate (Reverse Zone). What should be done if this reverse zone doesn't exists yet?
Create it automatically, too?
→ Which "nameserver" (NS record) should be used for it?
→→ ucr.get('ldap/master') ?
If we can't create it automatically how should this made clear to the user which creates the object?
→ Display an error message after creation?
→ Display a warning in the long description (easiest)?
→ Create an input field to enter it?
→ Disable the checkbox (I think this is not easy to implement).
Comment 1 Florian Best univentionstaff 2016-02-22 15:51:01 CET
How should changed be treated?
Should we remove or change the old pointer records if one changes the IP address(es)?
Comment 2 Stefan Gohmann univentionstaff 2019-01-03 07:18:30 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.