[Kea-users] On setting up DDNS with entries in /etc/kea/isc-kea-dhcp4.conf

[Darren Ankney]

Hi,

I was able to start the kea-dhcp4 server (2.4.1) using this simple
configuration derived from yours above.  Of course, it wouldn't do
anything, but it did start and run.

The configuration (in test.json):
{
  "Dhcp4": {
     "dhcp-ddns": {
        "enable-updates": false,
         "server-ip": "127.0.0.1",
         "server-port":53001,
         "sender-ip":"",
         "sender-port":0,
         "max-queue-size":1024,
         "ncr-protocol":"UDP",
         "ncr-format":"JSON"
     },
     "ddns-send-updates": true,
     "ddns-override-no-update": false,
     "ddns-override-client-update": false,
     "ddns-replace-client-name": "never",
     "ddns-generated-prefix": "myhost",
     "ddns-qualifying-suffix": "",
     "ddns-update-on-renew": false,
     "ddns-use-conflict-resolution": true,
     "hostname-char-set": "",
     "hostname-char-replacement": ""
  }
}

The command and output:
$ sudo /usr/sbin/kea-dhcp4 -c test.json
[sudo] password for dankney:
2024-01-19 20:47:07.643 INFO  [kea-dhcp4.dhcp4/4941.140426273409472]
DHCP4_STARTING Kea DHCPv4 server version 2.4.1 (stable) starting
2024-01-19 20:47:07.644 INFO  [kea-dhcp4.hosts/4941.140426273409472]
HOSTS_BACKENDS_REGISTERED the following host backend types are
available: mysql postgresql
2024-01-19 20:47:07.644 WARN  [kea-dhcp4.dhcpsrv/4941.140426273409472]
DHCPSRV_MT_DISABLED_QUEUE_CONTROL disabling dhcp queue control when
multi-threading is enabled.
2024-01-19 20:47:07.644 WARN  [kea-dhcp4.dhcp4/4941.140426273409472]
DHCP4_RESERVATIONS_LOOKUP_FIRST_ENABLED Multi-threading is enabled and
host reservations lookup is always performed first.
2024-01-19 20:47:07.645 INFO  [kea-dhcp4.dhcp4/4941.140426273409472]
DHCP4_CONFIG_COMPLETE DHCPv4 server has completed configuration: no
IPv4 subnets!; DDNS: disabled
2024-01-19 20:47:07.647 INFO  [kea-dhcp4.dhcpsrv/4941.140426273409472]
DHCPSRV_MEMFILE_DB opening memory file lease database: type=memfile
universe=4
2024-01-19 20:47:07.647 INFO  [kea-dhcp4.dhcpsrv/4941.140426273409472]
DHCPSRV_MEMFILE_LEASE_FILE_LOAD loading leases from file
/var/lib/kea/kea-leases4.csv.2
2024-01-19 20:47:07.648 INFO  [kea-dhcp4.dhcpsrv/4941.140426273409472]
DHCPSRV_MEMFILE_LEASE_FILE_LOAD loading leases from file
/var/lib/kea/kea-leases4.csv
2024-01-19 20:47:07.648 INFO  [kea-dhcp4.dhcpsrv/4941.140426273409472]
DHCPSRV_MEMFILE_EXTRACT_EXTENDED_INFO4 extracting extended info saw 0
leases, extended info sanity checks modified 0 / updated 0 leases and
0 leases have relay or remote id
2024-01-19 20:47:07.650 INFO  [kea-dhcp4.dhcpsrv/4941.140426273409472]
DHCPSRV_MEMFILE_LFC_SETUP setting up the Lease File Cleanup interval
to 3600 sec
2024-01-19 20:47:07.651 WARN  [kea-dhcp4.dhcpsrv/4941.140426273409472]
DHCPSRV_NO_SOCKETS_OPEN no interface configured to listen to DHCP
traffic
2024-01-19 20:47:07.653 WARN  [kea-dhcp4.dhcp4/4941.140426273409472]
DHCP4_MULTI_THREADING_INFO enabled: yes, number of threads: 2, queue
size: 64
2024-01-19 20:47:07.655 INFO  [kea-dhcp4.dhcp4/4941.140426273409472]
DHCP4_STARTED Kea DHCPv4 server version 2.4.1 started
^C2024-01-19 20:47:09.182 INFO  [kea-dhcp4.dhcp4/4941.140426273409472]
DHCP4_SHUTDOWN server shutdown

Please can you attempt to run your server from the command line as
shown and supply the output?  It will have the error message when the
server fails.

Also, 2.0.x is EOL.  There are two current versions: 2.2.1 and 2.4.1.
It is best to run the latest current version (2.4.1) if possible.

Thank you,
Darren Ankney

On Fri, Jan 19, 2024 at 3:19 PM Roger Hall <rhall at colorado.edu> wrote:
>
> I’m in the process of building out Kea for the first time and am in the midst of adding parameters in isc-kea-dhcp4.conf.  I’m finding discrepancies in the following syntax listed in section 8.2.18 DDNS for DHCPv4 of the kea readthedocs manual:
>
>
>
> "Dhcp4": {
>
>      "dhcp-ddns": {
>
>         // Connectivity parameters
>
>         "enable-updates": false,
>
>          "server-ip": "127.0.0.1",
>
>          "server-port":53001,
>
>          "sender-ip":"",
>
>          "sender-port":0,
>
>          "max-queue-size":1024,
>
>          "ncr-protocol":"UDP",
>
>          "ncr-format":"JSON"
>
>      },
>
>
>
>      // Behavioral parameters (global)
>
>      "ddns-send-updates": true,
>
>      "ddns-override-no-update": false,
>
>      "ddns-override-client-update": false,
>
>      "ddns-replace-client-name": "never",
>
>      "ddns-generated-prefix": "myhost",
>
>      "ddns-qualifying-suffix": "",
>
>      "ddns-update-on-renew": false,
>
>      "ddns-use-conflict-resolution": true,
>
>      "hostname-char-set": "",
>
>      "hostname-char-replacement": ""
>
>      ...
>
> }
>
>
>
> None of the ddns entry parameters are recognized upon isc-kea-dhcp4-server restart after first install.  In order for me to get kea status to behave, I have to comment out all of the ddns-* entries.  Has anyone else seen this?  I’ve installed kea 2.0.
>
> --
> 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