<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 6/2/16 11:11 AM, Thomas Markwalder
wrote:<br>
</div>
<blockquote cite="mid:fa4b2381-e76e-c76a-93d5-14954ab0ed12@isc.org"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
:<br>
<blockquote
cite="mid:HE1PR08MB101704C0C39686E7F8DF213A98580@HE1PR08MB1017.eurprd08.prod.outlook.com"
type="cite">
<pre wrap="">Hi Tomas,
I cleared the logs and renewed the address on my test machine to hopefully capture only the related events. Please find the logs attached. Apologies for the format of this message, this email web client is being very stupid :(
With thanks,
Lewis
</pre>
</blockquote>
<p>Hi Lewis:</p>
<p>Looking at the kea-dhcp4.log, you'll see this:</p>
<p>2016-06-02 15:05:35.953 DEBUG [kea-dhcp4.packets/35454]
DHCP4_QUERY_DATA [hwtype=1 00:50:56:9d:0f:1f],
cid=[01:00:50:56:9d:0f:1f], tid=0x3765bcd1, packet details:
local_address=255.255.255.255:67, remote_adress=0.0.0.0:68,
msg_type=DHCPREQUEST (3), transid=0x3765bcd1,<br>
options:<br>
type=012, len=007: "windhcp" (string)<br>
type=050, len=004: 10.12.30.150 (ipv4-address)<br>
type=053, len=001: 3 (uint8)<br>
type=054, len=004: 10.12.30.6 (ipv4-address)<br>
type=055, len=012: 1(uint8) 15(uint8) 3(uint8) 6(uint8)
44(uint8) 46(uint8) 47(uint8) 31(uint8) 33(uint8) 121(uint8)
249(uint8) 43(uint8)<br>
type=060, len=008: "MSFT 5.0" (string)<br>
type=061, len=007: 01:00:50:56:9d:0f:1f<br>
type=81 (CLIENT_FQDN), flags: (N=0, E=0, O=0, S=0),
domain-name='windhcp' (partial)</p>
<p><br>
</p>
<p>The FQDN flags being sent up by your Client, specify N and S as
0, which translates to
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
"Client wants to do forward updates, server should do reverse
updates". Look at Table 7.4 in the Kea Admin guide. You have
two options:<br>
</p>
<p>1. If you have control over your client you can change these
flags to be N=0, S=1 ... this requests the server to do both
Forward and Reverse updates.</p>
<p>2. If you cannot control the client, then you can use the
parameter <span class="command"><strong>override-client-update.</strong></span>
When this parameter is true, kea-dhcp4 will disregard requests
for client delegation and generate a DDNS request to update both
forward and reverse DNS data:</p>
<p>
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
</p>
<pre class="screen">"Dhcp4": {
"dhcp-ddns": {
<strong class="userinput"><code>"override-client-update": true</code></strong>,
...
},
...
}</pre>
<p>Looking kea-ddns.log, it receives the request from kea-dhcp4
but drops as it does not request forward updates (due to the
client flags) and reverse updates are not enabled (no reverse
domains), so it correctly drops the request.</p>
<p>Once you've addressed the flag issue, you should be on your
way.</p>
<p>Thomas</p>
<p>ISC Software Engineering<br>
</p>
<p><br>
</p>
<p><br>
</p>
</blockquote>
<p>Hi Lewis:</p>
<p>I'm just following up to see if you've gotten things working.
I've also cc'd this email to our user list:
<a class="moz-txt-link-abbreviated" href="mailto:kea-users@lists.isc.org">kea-users@lists.isc.org</a>. Using this email lets you look for
answers and share ideas with our growing Kea user community. Our
users are a creative, thoughtful group eager to help and learn
from each other.</p>
<p>Regards,</p>
<p>Thomas Markwalder</p>
<p>ISC Software Engineering<br>
</p>
<p><br>
</p>
<p><br>
</p>
</body>
</html>