Kea registrations
-
Thanks for the report. We replicated the issue and are working on a fix for the release.
-
@marcosm Thanks Marcos. Quick question... Is the issue with missing option-data data also expected to be addressed in the release?
-
I'm not aware of it - do you have a link with more info?
-
@dennypage
I always wanted to find out from the users why do they need KEA to register non-static IP clients with Unbound. Nobody has been able to explain that. I wonder if you could help me understand. -
@marcosm said in Kea registrations:
I'm not aware of it - do you have a link with more info?
Apologies, I thought the issue was a known issue, but now that I look I can't find anything in Redmine.
The issue in 25.07.1 is that kea2unbound produces "unknown.home.arpa" domains for some hosts. Some discussion of it in this thread, but it's unfortunately mixed in with intentional "home.arpa" use so it doesn't stand out clearly. I have a bit of dependence on IPv6 (and don't use home.arpa), so it really stands out for me.
In my case, the issue arrises from Kea reporting an empty option-data section, seen with
echo '{"command":"lease6-get-all"}' | nc -U /var/run/kea6-ctrl-socket | jqand this empty option-data section causes kea2unbound to use the fallback domain of "unknown.home.arpa" registered in kea2unbound line 865.
I never fully tracked down why Kea was reporting empty option-data, but looking in /var/lib/kea/dhcp6.leases*, the affected hosts actually have option-data in them, but there is no domain-search present in the option-data.
In my network, it affects a handful of devices. Two devices, my switch (Cisco) and main server (Gentoo Linux), are multi-homed, and most interestingly it only affects the registrations in two of three network segments those hosts are present in. I'm happy to PM you examples from the lease6-get-all output if that would help.
I ended up patching kea2unbound to use my domain as the fallback domain, meaning to get back to it. I've since looked at it a couple of times, but I always ran out of time before I could really track down why it's happening.
-
@markster said in Kea registrations:
I always wanted to find out from the users why do they need KEA to register non-static IP clients with Unbound. Nobody has been able to explain that. I wonder if you could help me understand.
The term "non-static" is subject to interpretation, so I'm guessing what your question actually is...
I generally run my networks as fully managed. All hosts have names registered with DHCP. In the case of IPv4, these are handled via Early DNS registrations. However with Kea, IPv6 Early DNS registration does not currently work when a track interface is in use. With a track interface if you have a host with an assigned address of
::22and you have pre-registration enabled, what you will receive in hostname resolution is literally just
::22instead of the expected
<delegated-prefix>::22Currently, the only way around this with Kea is to perform the registration when the host is given the lease. This is a known issue (Redmine #16191).
Does this answer your question?
-
@dennypage
Let me clarify.It makes perfect sense that static IP network resources like NAS, email server, print server etc need to be registered but I somewhat fail to get an idea that my iphones, ipads and tables need to be.
But why would I want every dynamic IP clients (iphone, tv, ipda, android phone etc) have registered with Unbound?
My question is about the need to register dhcp leases (changes all the time) with Unbound DNS? These clients do not need to have these dynamic/changes IP addresses registered with DNS. -
@dennypage There are significant changes with Kea in 25.11. I would first ask to try reproducing the issue there. Until a new RC build is released, you can update to the current public build and apply the patch for (then restart Kea services):
35b7ace2e50e8e9387ae23964a0d18978601e0ddNote that the socket path has changed; the command would now be:
echo '{"command":"lease6-get-all"}' | nc -U /var/run/kea/kea6-ctrl-socket | jq . -
@markster said in Kea registrations:
@dennypage
But why would I want every dynamic IP clients (iphone, tv, ipda, android phone etc) have registered with Unbound?
My question is about the need to register dhcp leases (changes all the time) with Unbound DNS? These clients do not need to have these dynamic/changes IP addresses registered with DNS.I'm not sure my usage relates to your question then. My leases, including phones, tablets, tvs, etc., don't change all the time. They are all fixed hostname->ip addr mappings.
-
@marcosm said in Kea registrations:
Until a new RC build is released, you can update to the current public build and apply the patch for (then restart Kea services):
35b7ace2e50e8e9387ae23964a0d18978601e0ddI gave the patch a quick try, but it breaks unbound. [It reports syntax errors /in /var/unbound/leases*.conf]
-
Can you provide more detail? What exactly is the error being logged and what are the contents of those files? What's the step-by-step for the test? Feel free to DM me.
-
@marcosm DM sent.
