<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 5/18/17 1:21 PM, professor geek
wrote:<br>
</div>
<blockquote
cite="mid:CAAa9S_nPwDPRUNEKtnM5=B=zNXFbtZDViuq4C5ExNFWA5GLMCg@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html; charset=UTF-8">
<div id="bloop_customfont">
<div id="bloop_customfont">Hello the list,</div>
<div id="bloop_customfont"><br>
</div>
<div id="bloop_customfont">As far as i know same behaviour apply
when we use kea for dhcpv4 and dhcpv6 with ddns for the same
client on the same dns zone.</div>
<div id="bloop_customfont">The only workaround <a
moz-do-not-send="true"
href="http://airmail.calendar/2017-05-18%2012:00:00%20GMT+2">today</a> is
to have separate dns zone for v4 and v6 lease.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Pr</div>
</div>
<div id="bloop_sign_1495128032045867008" class="bloop_sign">
<div><br>
</div>
</div>
<p class="airmail_on">On 18 May 2017 at 18:14:28 , Thomas
Markwalder (<a moz-do-not-send="true"
href="mailto:tmark@isc.org">tmark@isc.org</a>) wrote:</p>
<blockquote type="cite" class="clean_bq"><span>
<div>
<div>
<title></title>
<div class="moz-cite-prefix">On 5/1/17 6:19 AM, Thomas
Markwalder
wrote:<br>
</div>
<blockquote
cite="mid:e3b07e7f-cb7e-5422-032a-77b2f71f8640@isc.org"
type="cite">
<div class="moz-cite-prefix">Hello Pawel:<br>
<br>
<br>
Kea's DDNS process, kea-dhcp-ddns, implements conflict
detection/resolution as described in RFC 4703 (<a
moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.rfc-archive.org/getrfc.php?rfc=4703">http://www.rfc-archive.org/getrfc.php?rfc=4703</a>).
This behavior restricts DDNS updates for a given FQDN
(hostname),
to a single client as identified by its DHCID.
Therefore, if one client creates DNS entries for a
hostname, "<a moz-do-not-send="true"
href="http://example.host.com">example.host.com</a>",
and later a different client attempts
to add/replace/delete those entries, the updates will
be
rejected. The intent is to prevent different clients
from owning the same name.<br>
<br>
I did notice that we do not describe this in our
administrator's
guide as we should. I have created a bug ticket to
update the
documentation (<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://kea.isc.org/ticket/5275#ticket">http://kea.isc.org/ticket/5275#ticket</a>).
We may include a configurable parameter that turns
this policy on
and off. If you this functionality you would like to
see added, your cause would be aided by opening an
enhancement ticket: <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://kea.isc.org/newticket">http://kea.isc.org/newticket</a>
. This helps us know what issues are important to our
users.<br>
<br>
Regards,<br>
<br>
Thomas Markwalder<br>
ISC Software Engineering<br>
<br>
On 5/1/17 4:46 AM, Paweł Socha wrote:<br>
</div>
<blockquote
cite="mid:CADzD43ZomBKoHZTsMs-QMoxHuizFKX6ynhZfc9LO6W7bPvME_g@mail.gmail.com"
type="cite">
<div dir="ltr">Hello everyone,
<div><br>
</div>
<div>I am using kea-dhcp4 with kea-ddns service to
dynamically
allocate new addresses for "named" DNS service.
When a host with
hostname X and IP address A is shut down and new
one with
hostname X goes up, it gets new IP address ( B ),
but in dynamic
dns is still present previous A-X binding, but not
B-X. Removal of
dynamic entry is rejected with RCODE 7 and adding
a new one is
rejected with RCODE 8. When lease for address A is
expired, A-X
binding is successfully removed.</div>
<div>Is there any opportunity to solve hostname
conflict by
overwriting Dynamic DNS entries by the newest
ones? I've tried
everything...</div>
<div><br>
</div>
<div>Thanks!</div>
<div>Pawel</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
Kea-users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Kea-users@lists.isc.org">Kea-users@lists.isc.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/kea-users">https://lists.isc.org/mailman/listinfo/kea-users</a>
</pre>
</blockquote>
<p><br>
</p>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
Kea-users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Kea-users@lists.isc.org">Kea-users@lists.isc.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/kea-users">https://lists.isc.org/mailman/listinfo/kea-users</a>
</pre>
</blockquote>
<p><tt>Hello Pawel:</tt></p>
<p><tt><br>
Just wanted to update you on your feature request to
be able to
turn on/off conflict resolution in kea-dhcp-ddns (aka
D2). We
will keep it in mind for future releases, but has been
deemed
not-in-scope for our next release Kea 1.3 which should
be out
sometime in 2017 (firm date is TBD).</tt></p>
<p><tt><br>
Regards,</tt></p>
<p><tt><br>
</tt></p>
<p><tt>Thomas Markwalder</tt></p>
<p><tt>ISC Software Engineering<br>
</tt></p>
_______________________________________________
<br>
Kea-users mailing list
<br>
<a moz-do-not-send="true"
href="mailto:Kea-users@lists.isc.org">Kea-users@lists.isc.org</a>
<br>
<a moz-do-not-send="true"
href="https://lists.isc.org/mailman/listinfo/kea-users">https://lists.isc.org/mailman/listinfo/kea-users</a>
<br>
</div>
</div>
</span></blockquote>
</blockquote>
<p><tt>Hello Pr:</tt></p>
<p><tt><br>
You're correct. We do have a ticket,
<a class="moz-txt-link-freetext" href="http://kea.isc.org/ticket/4519">http://kea.isc.org/ticket/4519</a>, that calls for Kea to support
receiving DUIDs from v4 clients in order to support dual-stack
environments. It's not on the schedule for 1.3 which is underway
now, but it is on our radar.</tt></p>
<p><tt><br>
Regards,</tt></p>
<p><tt>Thomas Markwalder</tt></p>
<p><tt>ISC Software Engineering<br>
</tt></p>
</body>
</html>