Bug 40772 - __add_related_ptrrecords() is broken!
Summary: __add_related_ptrrecords() is broken!
Status: RESOLVED WONTFIX
Alias: None
Product: UCS
Classification: Unclassified
Component: UMC - DNS
Version: UCS 4.1
Hardware: Other Linux
: P5 normal
Target Milestone: UCS 4.x
Assignee: UMC maintainers
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-25 09:08 CET by Florian Best
Modified: 2019-01-03 07:23 CET (History)
0 users

See Also:
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):
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 Florian Best univentionstaff 2016-02-25 09:08:39 CET
There is a function simpleComputer.__add_related_ptrrecords().

The function constructs a wrong search filter:
>>> search_filter = '(|(relativeDomainName=%s)(relativeDomainName=%s)(relativeDomainName=%s))' % (ip_split[0], '.'.join(ip_split[:1]), '.'.join(ip_split[:2]))
→ '(|(relativeDomainName=3)(relativeDomainName=3)(relativeDomainName=3.0))'
This is easily fixed with:
>>> '(|(relativeDomainName=%s)(relativeDomainName=%s)(relativeDomainName=%s))' % (ip_split[0], '.'.join(ip_split[:2]), '.'.join(ip_split[:3]))
→ '(|(relativeDomainName=3)(relativeDomainName=3.0)(relativeDomainName=3.0.10))'

But the function seems to also called with the wrong zoneDN:
It is called with the DN of the forward zone instead of the reverse zone.
So it searches for pointer records underneath of a forward zone.
And will therefore never find one!
Comment 1 Stefan Gohmann univentionstaff 2019-01-03 07:23:23 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.