Bug 41559 - Assert DNS reverse zones are prefix-free
Summary: Assert DNS reverse zones are prefix-free
Status: RESOLVED WONTFIX
Alias: None
Product: UCS
Classification: Unclassified
Component: UMC - DNS
Version: UCS 4.1
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: UMC maintainers
QA Contact:
URL:
Keywords:
Depends on: 33472
Blocks:
  Show dependency treegraph
 
Reported: 2016-06-14 13:03 CEST by Philipp Hahn
Modified: 2019-01-03 07:20 CET (History)
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?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.137
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Error handling, Usability
Customer ID:
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2016-06-14 13:03:23 CEST
A customer (with S4) had to DNS reverse zones
 16.172.in-addr.arpa.
 0.16.172.in-addr.arpa.
Somethings™ was very unhappy about that and DNS reverse resolving no longer worked.

The UMC (or the disgnostics module) should warn about one zone being a prefix of another.
Comment 1 Stefan Gohmann univentionstaff 2019-01-03 07:20:45 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.