<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof ContentPasted0">
Hello,</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof ContentPasted0">
<div><br class="ContentPasted0">
</div>
<div class="ContentPasted0">I'm setting up Kea in a Test environment and ran across an issue with DDNS domain names. I have a couple of Windows servers that are domain joined. The domain is different than the domain used by the Kea DDNS service. So when a Windows
servers requests a lease an odd record is generated for the client. The windows domain name is "win-domain.com" and the domain used by DDNS is "win-test.com". Here are the hostname specific options received by a tcpdump when the Windows servers requests a
lease.</div>
<div><br class="ContentPasted0">
</div>
<div class="ContentPasted0"> Hostname (12), length 21: "win11"</div>
<div class="ContentPasted0"> FQDN (81), length 33: "win11.win-domain.com"</div>
<div><br class="ContentPasted0">
</div>
<div class="ContentPasted0">This combination results in the DDNS service creating a recording containing "win-domain.com" that I assume is because it's not the Kea DDNS domain and doesn't know how to handle it. The record that gets generated looks like this:
"win11.win-domain.com.win-test.com". In the Kea DHCP4 config, I have the following for the DDNS suffix.</div>
<div><br class="ContentPasted0">
</div>
<div class="ContentPasted0"> "ddns-qualifying-suffix": "win-test.com",</div>
<div><br class="ContentPasted0">
</div>
<div class="ContentPasted0">Looking at the documentation for DDNS there is the "ddns-replace-client-name" option but in my testing it seems that it can't use the value from the incoming packet's option 12 (hostname) and requires statically setting something.
Is there a way to work around this issue, removing "win-domain.com" from the DDNS record, or having DDNS ignore the FQDN (81) option all together? Would the "ddns-tuning" hook work for this?</div>
<div><br class="ContentPasted0">
</div>
<div class="ContentPasted0">Thanks,</div>
Isaac<br>
</div>
</body>
</html>