Re: [Kea-users] DDNS doesn't update local zone
Hi Darren,
I switched to filenames. Now the logs are clear enough to allow fixing the
forward- and reverse- ddns settings. (It seems it has been working for months
just because nobody happened to get a different IP than the time before.)
Thanks a lot
Ale
On Tue 11/Nov/2025 19:34:47 +0100 Darren Ankney wrote:
Hi Ale,
Your loggers section indicates that there should be a large amount of
information heading to syslog. I believe you are encountering this:
https://gitlab.isc.org/isc-projects/kea/-/issues/3921 whose fix was
backported to 2.6.4 here:
https://gitlab.isc.org/isc-projects/kea/-/issues/3992
Thank you,
Darren Ankney
On Tue, Nov 11, 2025 at 11:49 AM Alessandro Vesely wrote:
Hi Darren,
thanks for taking care.
One day after, all the other three clients have renewed (I can see the updated
expire time in dhcp4.csv[.2].) All I have in the logs is this:
Nov 10 12:08:17 190 north kea-dhcp-ddns: INFO
[kea-dhcp-ddns.dctl.140480598193344] DCTL_STARTING DhcpDdns starting, pid:
15727, version: 2.6.3 (stable)
Nov 10 12:23:45 190 north kea-dhcp4: INFO [kea-dhcp4.dhcp4.140607992743872]
DHCP4_STARTING Kea DHCPv4 server version 2.6.3 (stable) starting
Nov 10 12:23:45 190 north kea-dhcp4: INFO [kea-dhcp4.commands.140607992743872]
COMMAND_RECEIVED Received command 'config-set'
Nov 10 12:24:55 190 north kea-dhcp4: INFO [kea-dhcp4.dhcp4.140458599126976]
DHCP4_STARTING Kea DHCPv4 server version 2.6.3 (stable) starting
Nov 10 12:24:55 190 north kea-dhcp4: INFO [kea-dhcp4.commands.140458599126976]
COMMAND_RECEIVED Received command 'config-set'
Nov 10 12:25:45 190 north kea-dhcp4: INFO [kea-dhcp4.dhcp4.140267918301120]
DHCP4_STARTING Kea DHCPv4 server version 2.6.3 (stable) starting
Nov 10 12:25:45 190 north kea-dhcp4: INFO [kea-dhcp4.commands.140267918301120]
COMMAND_RECEIVED Received command 'config-set'
Nov 10 12:47:54 190 north kea-dhcp-ddns: INFO
[kea-dhcp-ddns.dctl.140298412311744] DCTL_STARTING DhcpDdns starting, pid:
17117, version: 2.6.3 (stable)
DHCP dialog, as shown by dhcpdum running on the server, looks fine.
Both commands are running with option -c . The logging
section for one:
"loggers":
[
{
// This section affects kea-dhcp4, which is the
base logger for DHCPv4
// component. It tells DHCPv4 server to write
all log messages (on
// severity INFO or more) to a file.
"name": "kea-dhcp4",
"output_options":
[
{
"output": "syslog:local7",
// Default is "%-5p [%c.%t]
%m\n";
// %-5p The severity of the
message
// %c The log source. This
includes two elements: kea-dhcp4 and library.
// %i The process ID.
// %t The thread ID.
// %m The log message itself.
"pattern": "%m\n",
// This governs whether the log
output is flushed to disk after
// every write. The default is
true (?)
"flush": false
// This specifies the maximum
size of the file before it is
// rotated.
// "maxsize": 1048576,
// This specifies the maximum
number of rotated files to keep.
// "maxver": 8
}
],
// This specifies the severity of log messages
to keep. Supported values
// are: FATAL, ERROR, WARN, INFO, DEBUG
"severity": "DEBUG",
// If DEBUG level is specified, this value is
used. 0 is least verbose,
// 99 is most verbose. If severity for the
logger is not DEBUG, this
// value is ignored.
"debuglevel": 99
}
]
For the other:
"loggers": [
{
// This specifies the logging for D2 (DHCP-DDNS) daemon.
"name": "kea-dhcp-ddns",
"output-options": [
{
// Specifies the output file. There are several special values
// supported:
// - stdou
Re: [Kea-users] DDNS doesn't update local zone
Hi Ale,
Your loggers section indicates that there should be a large amount of
information heading to syslog. I believe you are encountering this:
https://gitlab.isc.org/isc-projects/kea/-/issues/3921 whose fix was
backported to 2.6.4 here:
https://gitlab.isc.org/isc-projects/kea/-/issues/3992
Thank you,
Darren Ankney
On Tue, Nov 11, 2025 at 11:49 AM Alessandro Vesely wrote:
>
> Hi Darren,
>
> thanks for taking care.
>
> One day after, all the other three clients have renewed (I can see the
> updated expire time in dhcp4.csv[.2].) All I have in the logs is this:
>
> Nov 10 12:08:17 190 north kea-dhcp-ddns: INFO
> [kea-dhcp-ddns.dctl.140480598193344] DCTL_STARTING DhcpDdns starting, pid:
> 15727, version: 2.6.3 (stable)
> Nov 10 12:23:45 190 north kea-dhcp4: INFO [kea-dhcp4.dhcp4.140607992743872]
> DHCP4_STARTING Kea DHCPv4 server version 2.6.3 (stable) starting
> Nov 10 12:23:45 190 north kea-dhcp4: INFO
> [kea-dhcp4.commands.140607992743872] COMMAND_RECEIVED Received command
> 'config-set'
> Nov 10 12:24:55 190 north kea-dhcp4: INFO [kea-dhcp4.dhcp4.140458599126976]
> DHCP4_STARTING Kea DHCPv4 server version 2.6.3 (stable) starting
> Nov 10 12:24:55 190 north kea-dhcp4: INFO
> [kea-dhcp4.commands.140458599126976] COMMAND_RECEIVED Received command
> 'config-set'
> Nov 10 12:25:45 190 north kea-dhcp4: INFO [kea-dhcp4.dhcp4.140267918301120]
> DHCP4_STARTING Kea DHCPv4 server version 2.6.3 (stable) starting
> Nov 10 12:25:45 190 north kea-dhcp4: INFO
> [kea-dhcp4.commands.140267918301120] COMMAND_RECEIVED Received command
> 'config-set'
> Nov 10 12:47:54 190 north kea-dhcp-ddns: INFO
> [kea-dhcp-ddns.dctl.140298412311744] DCTL_STARTING DhcpDdns starting, pid:
> 17117, version: 2.6.3 (stable)
>
> DHCP dialog, as shown by dhcpdum running on the server, looks fine.
>
> Both commands are running with option -c . The logging
> section for one:
>
> "loggers":
> [
> {
> // This section affects kea-dhcp4, which is
> the base logger for DHCPv4
> // component. It tells DHCPv4 server to write
> all log messages (on
> // severity INFO or more) to a file.
> "name": "kea-dhcp4",
> "output_options":
> [
> {
> "output": "syslog:local7",
>
> // Default is "%-5p [%c.%t]
> %m\n";
> // %-5p The severity of the
> message
> // %c The log source. This
> includes two elements: kea-dhcp4 and library.
> // %i The process ID.
> // %t The thread ID.
> // %m The log message itself.
>
> "pattern": "%m\n",
>
> // This governs whether the
> log output is flushed to disk after
> // every write. The default
> is true (?)
> "flush": false
>
> // This specifies the maximum
> size of the file before it is
> // rotated.
> // "maxsize": 1048576,
>
> // This specifies the maximum
> number of rotated files to keep.
> // "maxver": 8
> }
> ],
> // This specifies the severity of log
> messages to keep. Supported values
> // are: FATAL, ERROR, WARN, INFO, DEBUG
> "severity": "DEBUG",
>
> // If DEBUG level is specified, this value is
> used. 0 is least verbose,
> // 99 is most verbose. If severity for the
> logger is not DEBUG, this
> // value is ignored.
> "debuglevel": 99
> }
> ]
>
> For the other:
>
>"loggers": [
> {
> // This specifies the logging for D2 (DHCP-DDNS) daemon.
> "name": "kea-dhcp-ddns",
> "output-options": [
> {
> // Specifies the output file. There are several special
> values
> // supported:
> // - stdout (prints on standard output)
> // - stderr (prints on standard error)
> // - syslog (logs to
Re: [Kea-users] DDNS doesn't update local zone
Hi Darren,
thanks for taking care.
One day after, all the other three clients have renewed (I can see the updated
expire time in dhcp4.csv[.2].) All I have in the logs is this:
Nov 10 12:08:17 190 north kea-dhcp-ddns: INFO
[kea-dhcp-ddns.dctl.140480598193344] DCTL_STARTING DhcpDdns starting, pid:
15727, version: 2.6.3 (stable)
Nov 10 12:23:45 190 north kea-dhcp4: INFO [kea-dhcp4.dhcp4.140607992743872]
DHCP4_STARTING Kea DHCPv4 server version 2.6.3 (stable) starting
Nov 10 12:23:45 190 north kea-dhcp4: INFO [kea-dhcp4.commands.140607992743872]
COMMAND_RECEIVED Received command 'config-set'
Nov 10 12:24:55 190 north kea-dhcp4: INFO [kea-dhcp4.dhcp4.140458599126976]
DHCP4_STARTING Kea DHCPv4 server version 2.6.3 (stable) starting
Nov 10 12:24:55 190 north kea-dhcp4: INFO [kea-dhcp4.commands.140458599126976]
COMMAND_RECEIVED Received command 'config-set'
Nov 10 12:25:45 190 north kea-dhcp4: INFO [kea-dhcp4.dhcp4.140267918301120]
DHCP4_STARTING Kea DHCPv4 server version 2.6.3 (stable) starting
Nov 10 12:25:45 190 north kea-dhcp4: INFO [kea-dhcp4.commands.140267918301120]
COMMAND_RECEIVED Received command 'config-set'
Nov 10 12:47:54 190 north kea-dhcp-ddns: INFO
[kea-dhcp-ddns.dctl.140298412311744] DCTL_STARTING DhcpDdns starting, pid:
17117, version: 2.6.3 (stable)
DHCP dialog, as shown by dhcpdum running on the server, looks fine.
Both commands are running with option -c . The logging
section for one:
"loggers":
[
{
// This section affects kea-dhcp4, which is the
base logger for DHCPv4
// component. It tells DHCPv4 server to write
all log messages (on
// severity INFO or more) to a file.
"name": "kea-dhcp4",
"output_options":
[
{
"output": "syslog:local7",
// Default is "%-5p [%c.%t]
%m\n";
// %-5p The severity of the
message
// %c The log source. This
includes two elements: kea-dhcp4 and library.
// %i The process ID.
// %t The thread ID.
// %m The log message itself.
"pattern": "%m\n",
// This governs whether the log
output is flushed to disk after
// every write. The default is
true (?)
"flush": false
// This specifies the maximum
size of the file before it is
// rotated.
// "maxsize": 1048576,
// This specifies the maximum
number of rotated files to keep.
// "maxver": 8
}
],
// This specifies the severity of log messages
to keep. Supported values
// are: FATAL, ERROR, WARN, INFO, DEBUG
"severity": "DEBUG",
// If DEBUG level is specified, this value is
used. 0 is least verbose,
// 99 is most verbose. If severity for the
logger is not DEBUG, this
// value is ignored.
"debuglevel": 99
}
]
For the other:
"loggers": [
{
// This specifies the logging for D2 (DHCP-DDNS) daemon.
"name": "kea-dhcp-ddns",
"output-options": [
{
// Specifies the output file. There are several special values
// supported:
// - stdout (prints on standard output)
// - stderr (prints on standard error)
// - syslog (logs to syslog)
// - syslog:name (logs to syslog using specified name)
// Any other value is considered a name of the file
"output": "syslog:local7",
// Shorter log pattern suitable for use with systemd,
// avoids redundant information
"pattern": "%m\n"
// This governs whether the log output is flushed to disk after
// every write.
// "flush": false,
// This specifies the maximum size of the file before it is
// rotat
Re: [Kea-users] DDNS doesn't update local zone
Hi Ale, As a sanity check, is Kea logging other clients messages as expected if you release and renew? Thank you, Darren Ankney On Mon, Nov 10, 2025 at 7:08 AM Alessandro Vesely wrote: > > Hi, > I recently upgraded to Devuan Excalibur, equivalent to Debian Trixie, and had > some difficulty starting the Kea daemons. Now they're running. However, a > client somehow got a different IP than it had before. > > The host name and PTR records still use the previous IP. > > I tried to fix it by issuing dhclient -r/ dhclient. As a result, I have > several records showing the new IP in /var/lib/dhcp4.csv, but the DNS records > are unchanged. > > In kea-dhcp4 both enable-updates and ddns-send-updates are set to true. > > In both kea-dhcp4.conf and kea-dhcp-ddns.conf I set debuglevel to 99, but, > upon > restarting, I only got the two lines > > kea-dhcp4: INFO [kea-dhcp4.commands.140267918301120] COMMAND_RECEIVED > Received > command 'config-set' > > and > > kea-dhcp-ddns: INFO [kea-dhcp-ddns.dctl.140298412311744] DCTL_STARTING > DhcpDdns starting, pid: 17117, version: 2.6.3 (stable) > > > > Dhcp releases and subsequent discover, offer, request and ack are not logged. > > > Is there a way to force the DNS to sync? > > > Best > Ale > -- > > > > > > -- > 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. > [email protected] -- 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. [email protected]
Re: [Kea-users] DDNS doesn't update local zone
Hi Alessandro, Out of curiosity, which platform is this misbehaving client running? While upgrading my own instances of ISC DHCP, I noticed (among a few other shamefully dated configurations), that one of my clients is / was also misbehaving. This is an Android phone running LineageOS 22.2 (official release). I have since then examined my log files, where the client requests an address it had previously but is not allowed to have. The server responds with DHCPNAK, and DHCPOFFER for the configured static lease. The client ignores this response and DHCPREQUEST again for the erroneous address. Upon continued DHCPNAK, the client ignores the server and applies the wrong address, then complains that it doesn’t have Internet access. In order to resolve that issue, as well as misbehaving connectivity check (though both have mysteriously gone away now on its own, always reassuring), I intend to build LineageOS from source myself. Additionally, I have made my internal web servers perform /generate_204 and DNS RPZ point connectivitycheck.gstatic.com to mine instead. In the build from source, I intend to just replace the Google address altogether. In addition, I want to pay close attention to the DHCP stack. It should not be ignoring what on the wire was multiple attempts to make the client behave, being promptly ignored by said client. Best regards, Michael De Roover > On 10 Nov 2025, at 13:08, Alessandro Vesely wrote: > > Hi, > I recently upgraded to Devuan Excalibur, equivalent to Debian Trixie, and had > some difficulty starting the Kea daemons. Now they're running. However, a > client somehow got a different IP than it had before. > > The host name and PTR records still use the previous IP. > > I tried to fix it by issuing dhclient -r/ dhclient. As a result, I have > several records showing the new IP in /var/lib/dhcp4.csv, but the DNS records > are unchanged. > > In kea-dhcp4 both enable-updates and ddns-send-updates are set to true. > > In both kea-dhcp4.conf and kea-dhcp-ddns.conf I set debuglevel to 99, but, > upon restarting, I only got the two lines > > kea-dhcp4: INFO [kea-dhcp4.commands.140267918301120] COMMAND_RECEIVED > Received command 'config-set' > > and > > kea-dhcp-ddns: INFO [kea-dhcp-ddns.dctl.140298412311744] DCTL_STARTING > DhcpDdns starting, pid: 17117, version: 2.6.3 (stable) > > > > Dhcp releases and subsequent discover, offer, request and ack are not logged. > > > Is there a way to force the DNS to sync? > > > Best > Ale > -- > > > > > > -- > 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. > [email protected] -- 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. [email protected]
