X-RT-Interface: Web
Content-Disposition: inline
MIME-Version: 1.0
X-RT-Original-Encoding: utf-8
References: <20111001220718.BE1059F85B4@fafnir.remote.dragon.net>
 <RT-Ticket-26024@isc.org>
Message-ID: <rt-4.4.1-84719-1502996918-684.26024-0-0@isc.org>
Content-Transfer-Encoding: binary
In-Reply-To: <20111001220718.BE1059F85B4@fafnir.remote.dragon.net>
Content-Type: text/plain; charset="utf-8"
X-Mailer: MIME-tools 5.508 (Entity 5.508)
RT-Send-CC:
Content-Length: 1333

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,