Bug 41784 - distribute multiple DNS suffixes via DHCP
distribute multiple DNS suffixes via DHCP
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: DHCP
UCS 4.1
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-07-13 08:27 CEST by Jens Thorp-Hansen
Modified: 2019-01-03 07:18 CET (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
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.046
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2016071221000271
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jens Thorp-Hansen univentionstaff 2016-07-13 08:27:28 CEST
reference: Ticket#2016071221000271

It should be possible to distribute multiple DNS suffixes via DHCP
Comment 1 Philipp Hahn univentionstaff 2016-07-18 15:05:18 CEST
Arbitrary options like "option domain-search" can be added through the CLI interface of UDM, for example:
 udm dhcp/service modify \
  --dn cn=phahn.qa,cn=dhcp,dc=phahn,dc=qa \
  --set option='domain-search "phahn.qa","univention.de";'


Due to Bug #33614 you currently only can use one option. If you need more, you need to apply a one-line-patch to /usr/share/pyshared/univention/admin/handlers/dhcp/__common.py:61 and replace "univention.admin.mapping.ListToString" with "None".
Comment 2 Stefan Gohmann univentionstaff 2016-12-13 08:10:46 CET
The Enterprise Customer affected flag is set but neither a Ticket number is referenced nor a Customer ID is set. Please set a Ticket number or a Customer ID. Otherwise the Enterprise Customer affected flag will be reset.
Comment 3 Stefan Gohmann univentionstaff 2019-01-03 07:18:59 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.