Bug 1394727
| Summary: | [RFE] Backport RFC standard DDNS updates support from 4.3.5 ESV version | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Rupesh Patel <rupatel> |
| Component: | dhcp | Assignee: | Pavel Zhukov <pzhukov> |
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> |
| Severity: | medium | Docs Contact: | Ioanna Gkioka <igkioka> |
| Priority: | medium | ||
| Version: | 7.4 | CC: | jstodola, pasik, pzhukov, rupatel, salmy, thozza |
| Target Milestone: | rc | Keywords: | FutureFeature, Patch |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-04-10 08:00:52 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1298243, 1420851, 1465887, 1465928 | ||
|
Description
Rupesh Patel
2016-11-14 10:27:43 UTC
Hi Rupesh, can you please retest it with RHEL-7Beta compose? The patch is present there. 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. 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. 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 |