[Kea-users] DDNS limitations - ddns-qualifying-suffix vs domain-name

[Darren Ankney]

Hi Vladimir,

The DHCPv4 domain-name option (15) isn't meant for use with ddns.  It
is a search domain that the client should use when performing name
resolution.  See: https://www.rfc-editor.org/rfc/rfc2132#section-3.17

You can set ddns-qualifying-suffix at the global, shared-network and
subnet level.  In a host reservation, you can use the "hostname"
parameter to specify a FQDN to send to the client and for use in DDNS.
See here: https://kea.readthedocs.io/en/kea-2.4.0/arm/dhcp4-srv.html#reserving-a-hostname

On Mon, Oct 16, 2023 at 3:23 PM Vladimir Nikolic via Kea-users
<kea-users at lists.isc.org> wrote:
>
> Hi,
>
> While trying to migrate DHCP service from ISC DHCP to ISC KEA, we are
> hitting following KEA limitations:
>
> - option domain-name has no part in DDNS names construction, it's only
> ddns-qualifying-suffix that's being honoured
> - ddns-qualifying-suffix can't be specified in the class definition (we
> have dedicated zone for our OOB devices)
> - there can be only one DDNS zone for all the clients in a subnet
> (ddns-qualifying-suffix), with ISC DHCP you can have one default
> domain-name for a subnet and every single host reservation with a
> different domain-name (DDNS zone)
>
> Regards,
> Vladimir
> --
> ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
>
> To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.
>
> Kea-users mailing list
> Kea-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/kea-users