RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1394727 - [RFE] Backport RFC standard DDNS updates support from 4.3.5 ESV version
Summary: [RFE] Backport RFC standard DDNS updates support from 4.3.5 ESV version
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dhcp
Version: 7.4
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Pavel Zhukov
QA Contact: Release Test Team
Ioanna Gkioka
URL:
Whiteboard:
Depends On:
Blocks: 1298243 1420851 1465887 1465928
TreeView+ depends on / blocked
 
Reported: 2016-11-14 10:27 UTC by Rupesh Patel
Modified: 2021-03-11 14:48 UTC (History)
6 users (show)

Fixed In Version: dhcp-4.2.5-62.el7
Doc Type: Release Note
Doc Text:
DHCP now supports standard dynamic DNS updates With this update, the DHCP server allows updating DNS records by using a standard protocol. As a result, DHCP supports standard dynamic DNS updates as described in RFC 2136: https://tools.ietf.org/html/rfc2136.
Clone Of:
Environment:
Last Closed: 2018-04-10 08:00:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0658 0 None None None 2018-04-10 08:01:58 UTC

Description Rupesh Patel 2016-11-14 10:27:43 UTC 
Only "ad-hoc" and "interim" DDNS updates are  available in the RHEL 7 dhcp-4.2.X.
4.3.5 ESV offer RFC standard DDNS updates (ddns-update-style standard; )

RedHat should rebase DHCP 4.2.X to 4.3.X ESV or give both legacy releases and the standard 4.3.X ESV one.
Comment 16 Marek Hruscak 2018-01-25 13:32:14 UTC 
Hi Rupesh,
can you please retest it with RHEL-7Beta compose? The patch is present there.
Comment 17 Rupesh Patel 2018-01-29 16:41:32 UTC 
Hi,

I have checked with customer.  Unfortunately customer has stopped using DDNS. However they mentioned that they have read RHEL7.5 release note.
They are closing service request.
Comment 18 Jan Stodola 2018-02-22 16:12:01 UTC 
Verified using the configuration files available from the link in comment 8.

1) server
[root@localhost ~]# rpm -q dhcp
dhcp-4.2.5-65.el7.x86_64
[root@localhost ~]# grep ddns-update-style /etc/dhcp/dhcpd.conf 
ddns-update-style standard;
[root@localhost ~]#

2) client
[root@localhost ~]# dhclient -H test2 ens9
[root@localhost ~]# nslookup test2.example.com
Server:		192.168.78.1
Address:	192.168.78.1#53

Name:	test2.example.com
Address: 192.168.78.10

[root@localhost ~]#

3) server logs:
named[20184]: client 192.168.78.1#39542/key rndc-key: signer "rndc-key" approved
named[20184]: client 192.168.78.1#39542/key rndc-key: updating zone 'example.com/IN': adding an RR at 'test2.example.com' A
named[20184]: client 192.168.78.1#39542/key rndc-key: updating zone 'example.com/IN': adding an RR at 'test2.example.com' DHCID
dhcpd[20124]: DHCPREQUEST for 192.168.78.10 from 52:54:00:50:a8:01 via ens9
dhcpd[20124]: DHCPACK on 192.168.78.10 to 52:54:00:50:a8:01 (test2) via ens9
dhcpd[20124]: Added new forward map from test2.example.com to 192.168.78.10
named[20184]: client 192.168.78.1#39542/key rndc-key: signer "rndc-key" approved
named[20184]: client 192.168.78.1#39542/key rndc-key: updating zone '78.168.192.in-addr.arpa/IN': deleting rrset at '10.78.168.192.in-addr.arpa' PTR
named[20184]: client 192.168.78.1#39542/key rndc-key: updating zone '78.168.192.in-addr.arpa/IN': adding an RR at '10.78.168.192.in-addr.arpa' PTR
dhcpd[20124]: Added reverse map from 10.78.168.192.in-addr.arpa. to test2.example.com
named[20184]: zone 78.168.192.in-addr.arpa/IN: sending notifies (serial 15)

Tested with dhcp-4.2.5-65.el7.

Moving to VERIFIED.
Comment 21 errata-xmlrpc 2018-04-10 08:00:52 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0658
Note You need to log in before you can comment on or make changes to this bug.