Report information
The Basics
Id:
26024
Status:
resolved
Estimated:
36 hours (2,160 minutes)
Worked:
5 minutes
Users:
mcnally: 5 minutes
Priority:
Medium/Medium
Queue:

People
Owner:
Nobody in particular
Cc:
AdminCc:

BugTracker
Version Fixed:
(no value)
Version Found:
(no value)
Versions Affected:
(no value)
Versions Planned:
4.4.0
Priority:
P1 High
Severity:
S2 Normal
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
(no value)
Area:
bug

Dates
Created:Sat, 01 Oct 2011 18:07:36 -0400
Updated:Thu, 17 Aug 2017 16:12:34 -0400
Closed:Thu, 17 Aug 2017 16:12:34 -0400



This bug tracker is no longer active.

Please go to our Gitlab to submit issues (both feature requests and bug reports) for active projects maintained by Internet Systems Consortium (ISC).

Due to security and confidentiality requirements, full access is limited to the primary maintainers.

Subject: dhcpd 4.2.2 puts temporary addresses in DNS
Date: Sat, 01 Oct 2011 15:07:18 -0700
To: dhcp-bugs@isc.org
From: ebersman@pae.com (Paul Ebersman)
When I request both permanent and temporary ipv6 addresses, I get both addresses but dhcpd does DDNS updates for both in the ip6.arpa zone. dhcpd should not be putting IA_TA addresses in DNS. dhcpd.conf file: ##### option domain-name "remote6.dragon.net"; option domain-name-servers 192.168.167.101; default-lease-time 3600; max-lease-time 7200; log-facility local7; update-static-leases on; authoritative; set vendor-string = option vendor-class-identifier; stash-agent-options true; ddns-update-style interim; ddns-updates on; ddns-domainname "remote6.dragon.net"; ddns-hostname = pick(option fqdn.hostname, option host-name, option dhcp6.fqdn, option fqdn.fqdn, concat("dyn-",binary-to-ascii(16,16,"-", substring(option dhcp6.ia-na, 16, 16)))); update-optimization false; key ddns-key { algorithm HMAC-MD5; secret "XXXX"; }; zone 4.9.2.0.8.3.9.1.1.0.0.2.ip6.arpa { primary ddns.dragon.net; key ddns-key; } zone remote6.dragon.net { primary ns1.dragon.net; key ddns-key; } subnet6 2001:1938:294::/64 { range6 2001:1938:294::200 2001:1938:294::250; range6 2001:1938:294:cafe::/64 temporary; } #####
On Sat Oct 01 22:07:36 2011, ebersman@pae.com wrote:
>
> When I request both permanent and temporary ipv6 addresses, I get both
> addresses but dhcpd does DDNS updates for both in the ip6.arpa
> zone. dhcpd should not be putting IA_TA addresses in DNS.

I'm not sure we can trust this submitter -- he strikes me as a bit suspect --
but someone should probably have a look and give some thought to
whether it's appropriate for dhcpd to act as described..

Setting a severity of "normal" and passing along to dev.


Hello Paul: While I realize this issue was reported a long time ago I am writing to you to follow up. I confirmed through testing that as of our current release, 4.3.6, by default the server does perform DDNS updates for temporary addresses. Whether or not it should remains open to interpretation as the RFCs are a somewhat vague on the subject. RFC 3315 states that: "The server MAY update the DNS for a temporary address, as described in section 4 of RFC 3041." It is possible to turn DDNS updates off on a per pool basis via server configuration as shown below: subnet6 2001:1938:294::/48 { range6 2001:1938:294::200 2001:1938:294::250; pool6 { # Turn off DDNS for temporary addresses ddns-updates off; range6 2001:1938:294:cafe::/64 temporary; } } In general we try to avoid changing default behavior, especially long standing behavior as the risk of breaking installations unexpectedly must be considered. Given the fine grained ability of turning the updates on and off currently provided, we do not anticipate making any code changes regarding this issue. Thank you for taking the time to report the issue to us. I apologize for the lag time in response but as a small non-profit, we have to address issues where there is demand for them. Sincerely, Thomas Markwalder ISC Software Engineering,