Bug 39514 – Configure ISC DHCP to do DDNS PTR record updates for Windows Clients

Bug 39514 - Configure ISC DHCP to do DDNS PTR record updates for Windows Clients


Summary:	Configure ISC DHCP to do DDNS PTR record updates for Windows Clients

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	DHCP
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	UCS 4.1-x
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-10-12 18:53 CEST by Arvid Requate
Modified:	2019-01-03 07:18 CET (History)
CC List:	2 users (show)

See Also:	23412 32427 301 39806
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):	Usability
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Arvid Requate

2015-10-12 18:53:55 CEST

Windows Clients in a Samba/AD domain configured to used DHCP by default ask the DHCP server to register the PTR record. To this end they send the "Client FQDN" option (option 81). It looks like the ISC DHCP server can be configured to behave similar to a Windows DHCP server at this point. Amongst other settings the following two lines seem to be required in dhcpd.conf

	option server.ddns-hostname = option fqdn.hostname;
	option server.ddns-domainname = option fqdn.domainname;

See also https://forge.univention.org/bugzilla/show_bug.cgi?id=23412.

This way of updating PTR records may help avoid problems of object ownership which Windows Clients face when they try to update PTR records which have been created by a different client earlier. I collected an noted more details at Ticket#:  2015100821000533.

See also https://forge.univention.org/bugzilla/show_bug.cgi?id=32427

Comment 1 Arvid Requate

2015-11-12 11:57:15 CET

More precise information about the issue mentioned above is now on Bug 39806.

Comment 2 Stefan Gohmann

2019-01-03 07:18:10 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.