<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap:break-word"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><div id="bloop_customfont" style="margin:0px">Hello the list,</div><div id="bloop_customfont" style="margin:0px"><br></div><div id="bloop_customfont" style="margin:0px">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" style="margin:0px">The only workaround <a 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 style="font-family:'helvetica Neue',helvetica;font-size:14px"><br></div><div style="font-family:'helvetica Neue',helvetica;font-size:14px">Regards,</div><div style="font-family:'helvetica Neue',helvetica;font-size:14px"><br></div><div style="font-family:'helvetica Neue',helvetica;font-size:14px">Pr</div></div> <div id="bloop_sign_1495128032045867008" class="bloop_sign"><div style="font-family:helvetica,arial;font-size:13px"><br></div></div><p class="airmail_on">On 18 May 2017 at 18:14:28 , Thomas Markwalder (<a href="mailto:tmark@isc.org">tmark@isc.org</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div bgcolor="#FFFFFF" text="#000000"><div></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 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 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 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 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 class="moz-txt-link-abbreviated" href="mailto:Kea-users@lists.isc.org">Kea-users@lists.isc.org</a>
<a 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 class="moz-txt-link-abbreviated" href="mailto:Kea-users@lists.isc.org">Kea-users@lists.isc.org</a>
<a 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 href="mailto:Kea-users@lists.isc.org">Kea-users@lists.isc.org</a>
<br><a href="https://lists.isc.org/mailman/listinfo/kea-users">https://lists.isc.org/mailman/listinfo/kea-users</a>
<br></div></div></span></blockquote></body></html>