Hi Vladimir,
I don't know for sure. It might make an assumption that "myhost" is
not an FQDN while assuming that "myhost.SomeOtherLabel" is an FQDN.
Or it might look to see if the value from ddns-qualifying-suffix is
part of the host already and not append if it is... Perhaps someone
else who
Hi Darren,
Could DDNS Tuning hook help here?
It says here
https://kea.readthedocs.io/en/latest/arm/hooks.html#dhcpv4-host-name-generation:
4. If there is a ddns-tuning in-scope host-name expression (either
global or subnet), calculate the host name using the expression. If the
calculated
Hi Vladimir,
I thought about that, but that wouldn't necessarily work. Without
looking up the provided hostname, Kea wouldn't understand if it should
add the suffix or not (i.e., is it a complete name?) For example:
- suffix could be 'example.org'
- 'example.org' might have sub domains such as
Hi Darren,
There would have to be some way to flag hostnames that you wanted to
ignore a ddns-qualifying-suffix setting somehow to have it
simultaneously set to some value and not apply to all hostnames in
that block.
Yeah, like if you end "hostname" parameter (within a host reservation)
Hi Vladimir,
You can set it "ddns-qualifying-suffix": "", which resets it to empty
in the block in which you do that. You could also only specify inside
subnets where you need it specified and not specify at global level.
There would have to be some way to flag hostnames that you wanted to
Thanks Darren.
If ‘ddns-qualifying-subnet’ is being set on any level, it’s then appended to
the ‘hostname’ value from the host reservation. ‘hostname’ is the FQDN, only if
‘ddns-qualifying-subnet’ is empty.
So it’s either one or another.
Which is really inflexible.
Regards
> On 17 Oct 2023,
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
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
