<div dir="ltr"><div><div>Thanks Thomas,<br></div><br>That's unfortunate as this is pretty straight forward function with the older ISC dhcp server with ddns-domainname that can be set in the subnet. Whilst writing a bit of C has some attraction, then maintaining it and the associated documentation for our environment.. does not.. It probably makes more business sense to punt back to the ISC server until this becomes a supported feature in Kea.<br><br></div><div>/rh<br></div><div><br></div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 11, 2016 at 4:04 AM, Thomas Markwalder <span dir="ltr"><<a href="mailto:tmark@isc.org" target="_blank">tmark@isc.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div><div class="h5">
<div>On 10/10/16 1:23 PM, Richard Holbo
wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>Am doing my first deployment of KEA after using
ISC-DHCP for..ever.<br>
<br>
</div>
Am trying to replicate an existing configuration with
multiple subnets updating different forward DNS
domains and am unclear on how to accomplish this as
all examples/docs I've found only seem to use a single
forward domain.<br>
<br>
</div>
I've got both forward and reverse working, forward for a
single domain, and reverse for whatever the subnet is.
My issue seems to be the following commands:<br>
<br>
<span></span>{<br>
<br>
"dhcp-ddns": { "enable-updates": true,<br>
"qualifying-suffix": "<a href="http://bogus.net" target="_blank">bogus.net</a>",<br>
"override-client-update": true<br>
},<br>
<br>
</div>
These seem to be required in the DHCP4 config but then
seem to override any settings in the ddns config<br>
<br>
"forward-ddns" : {<br>
"ddns-domains": [<br>
{<br>
"name": "<a href="http://bogus.net" target="_blank">bogus.net</a>.",<br>
"dns-servers": [ { "ip-address": "re.dac.ted",
"port": 53 } ]<br>
},<br>
{<br>
"name": "wireless.bogus.",<br>
"dns-servers": [ { "ip-address": "re.dac.ted",
"port": 53 } ]<br>
},<br>
{<br>
"name": "bogus.",<br>
"dns-servers": [ { "ip-address": "re.dac.ted",
"port": 53 } ]<br>
},<br>
]<br>
},<br>
<br>
</div>
<div>The following is info is set under the "subnet" section
for each:<br>
-----<br>
{<br>
"name": "domain-name",<br>
"data": "<a href="http://bogus.net" target="_blank">bogus.net</a>"<br>
},<br>
</div>
<div>-----<br>
{<br>
"name": "domain-name",<br>
"data": "bogus.wireless"<br>
},<br>
-----<br>
{<br>
"name": "domain-name",<br>
"data": "bogus"<br>
},<br>
<br>
</div>
I'm sure it's something simple I'm missing but been banging
my head against it for a couple of days. All forward DNS
goes to <a href="http://bogus.net" target="_blank">bogus.net</a>
irrespective of the domain-name settings of the subnet.<br>
<br>
</div>
/thanks<br>
</div>
/rh<br>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>______________________________<wbr>_________________
Kea-users mailing list
<a href="mailto:Kea-users@lists.isc.org" target="_blank">Kea-users@lists.isc.org</a>
<a href="https://lists.isc.org/mailman/listinfo/kea-users" target="_blank">https://lists.isc.org/mailman/<wbr>listinfo/kea-users</a>
</pre>
</blockquote>
<p><tt>Hello Richard:</tt></p>
<p><tt><br>
If I understand correctly, you're thinking that kea-dhcp4 will
use the "domain-name" option to qualify the hostname sent by
your clients as the FQDN for the DNS entries. While this is a
very useful feature, Kea does not yet support it. Currently,
the dhcp server can only be configured with a single, global
qualifying-suffix. It should be possible to override this
behavior by writing a custom hook for the lease4_select hook
point. This hook point is called after the subnet has been
selected and a lease has been determined but before the DDNS
request(s) are created. The hook would need to create an FQDN
option using the domain-name value from the selected subnet and
add the option to the inbound packet, the "query" argument in
the lease4_select. The server will see this FQDN option and use
it when forming the DDNS requests sent to kea-dhcp-ddns (aka
D2).<br>
</tt></p>
<p><tt>Writing hooks is discussed in detail with examples in our
developer's guide:</tt></p>
<p><tt><a href="https://jenkins.isc.org/job/Fedora20_32_doxygen_doc/doxygen/de/df3/dhcpv4Hooks.html" target="_blank">https://jenkins.isc.org/job/<wbr>Fedora20_32_doxygen_doc/<wbr>doxygen/de/df3/dhcpv4Hooks.<wbr>html</a></tt></p>
<p><tt>In the meantime, I have opened a ticket in our Trac, to
request the behavior:</tt></p>
<p><tt><a href="http://kea.isc.org/ticket/5048#ticket" target="_blank">http://kea.isc.org/ticket/<wbr>5048#ticket</a></tt></p>
<p><tt><br>
</tt></p>
<p><tt>Sincerely,</tt></p>
<p><tt>Thomas Markwalder</tt></p>
<p><tt>ISC Software Engineering<br>
</tt></p>
<p><tt><br>
</tt></p>
<p><tt><br>
</tt></p>
<p><tt><br>
</tt></p>
<p><tt><br>
</tt></p>
<p><tt><br>
</tt></p>
<p><tt><br>
</tt></p>
<p><tt> <br>
</tt></p>
<p><tt><br>
</tt></p>
<p><tt><br>
</tt></p>
</div>
<br>______________________________<wbr>_________________<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" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/<wbr>listinfo/kea-users</a><br>
<br></blockquote></div><br></div>