Bug 43516 - DHCP daemon breaks when configuring a Policy for DHCP Dynamic DNS
DHCP daemon breaks when configuring a Policy for DHCP Dynamic DNS
Status: RESOLVED DUPLICATE of bug 16798
Product: UCS
Classification: Unclassified
Component: DHCP
UCS 4.1
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-02-08 13:30 CET by Nico Stöckigt
Modified: 2018-04-13 13:40 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?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.051
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2017020521000087
Bug group (optional):
Max CVSS v3 score:


Attachments
/var/log/syslog (7.23 KB, text/plain)
2017-02-08 13:30 CET, Nico Stöckigt
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nico Stöckigt univentionstaff 2017-02-08 13:30:53 CET
Created attachment 8413 [details]
/var/log/syslog

I configured a 'DHCP Dynamic DNS' policy for the main DHCP Service as follows by only giving a 'DDNS Domainname'. This results in a broken DHCP configuration and also a not working DHCP. Restarting the DHCP daemon will fail.
 [see attachment for relevant syslog]

Deleting the entire entry seems not to be sufficient: 
 # udm policies/dhcp_dnsupdate remove --dn "cn=DNS-Suffix,cn=dnsupdate,cn=dhcp,cn=policies,dc=nvsx,dc=local" --recursive --remove_referring

But I found out, that restarting the DHCP daemon twice might fix the problem.
Comment 1 Philipp Hahn univentionstaff 2017-02-08 13:58:14 CET
You MUST quote the domain name, see Bug #16798 comment 1.

And before you ask: With "dhcp statements" and "dhcp options" (Bug #32557) you can break DHCPd even more - don't use it if you don't understand the implications.

*** This bug has been marked as a duplicate of bug 16798 ***