Hi Darren,
please find my configuration below:
{
"Dhcp6":
{
"dhcp-ddns": {
"enable-updates": true
},
"ddns-replace-client-name": "always",
"ddns-generated-prefix": "v6",
"ddns-qualifying-suffix": "local.markert.live",
"ddns-override-client-update": true,
"ddns-override-no-update": true,
"hostname-char-set": "[^A-Za-z0-9.-]",
"hostname-char-replacement": "x",
"client-classes": [
{
"name": "Default",
"test": "not (option[1].hex == '0x00020000AB11D087EFD048F95BBD')",
"option-data":
[
{
"name": "dns-servers",
"data": "fd00:192:168:3::1"
},
{
"name": "domain-search",
"data": "local.markert.live"
}
]
}
],
"loggers": [
{
"name": "kea-dhcp6",
"severity": "DEBUG",
"debuglevel": 99,
"output_options": [
{
"output": "kea-dhcp6.log",
"maxver": 10
}
]
},
{
"name": "kea-dhcp6.dhcpsrv",
"severity": "DEBUG",
"debuglevel": 99,
"output_options": [
{
"output": "dhcp6-dhcpsrv.log",
"maxver": 10
}
]
},
{
"name": "kea-dhcp6.leases",
"severity": "DEBUG",
"debuglevel": 99,
"output_options": [
{
"output": "dhcp6-leases.log",
"maxver": 10
}
]
}
],
"interfaces-config":
{
"interfaces": ["enp2s0"], // This is the internal interface
"service-sockets-max-retries": 10,
"service-sockets-retry-wait-time": 3000
},
"lease-database":
{
"type": "memfile",
"persist": true,
"name": "kea-leases6.csv",
"lfc-interval": 3600
},
"renew-timer": 15840,
"rebind-timer": 27720,
"valid-lifetime": 31680,
"shared-networks":
[
{
# Name of the shared network. It may be an arbitrary string
# and it must be unique among all shared networks.
"name": "markert-live-local",
# The subnet selector can be specified at the shared-network level.
# Subnets from this shared network will be selected for directly
# connected clients sending requests to the server's "enp2s0" interface.
"interface": "enp2s0",
# This starts a list of subnets in this shared network.
# There are two subnets in this example.
"subnet6":
[
{
// Internal ID to identify subnet internally
"id": 19216810,
// Subnet for fd00:192:168:0::/48 - static IPs (usable host IP range:
fd00:192:168:0::1 - fd00:192:168:0::ffff)
"subnet": "fd00:192:168:0::/48",
// Add DHCP IPv6 Pool
"pools":
[ ],
// Add reservations here for subnet
"reservations":
[
{
"duid": "00:02:00:00:ab:11:d0:87:ef:d0:48:f9:5b:bd",
"ip-addresses": [ "fd00:192:168:0::1" ],
"hostname": "v6-vmhomeserver"
}
],
// Additional information for subnet
"option-data":
[
{
"name": "dns-servers",
"data": "fd00:192:168:3::1"
},
{
"name": "domain-search",
"data": "local.markert.live"
}
]
},
{
"id": 1921681,
// Subnet for fd00:192:168:1::/48 - static IPs (usable host IP range:
fd00:192:168:1::1 - fd00:192:168:1::ffff)
"subnet": "fd00:192:168:1::/48",
"client-class": "Default",
// Add DHCP IPv6 Pool
"pools":
[ ],
// Add reservations here for subnet
"reservations":
[
{
"hw-address": "52:54:00:74:f6:13",
"ip-addresses": [ "fd00:192:168:1::1" ],
"hostname": "v6-vmhomeserver"
}
]
},
{
"id": 1921682,
// Subnet for fd00:192:168:2::/48 - static IPs (usable host IP range:
fd00:192:168:2::1 - fd00:192:168:2::ffff)
"subnet": "fd00:192:168:2::/48",
"client-class": "Default",
// Add DHCP IPv6 Pool
"pools":
[ ],
// Add reservations here for subnet
"reservations":
[
{
"hw-address": "52:54:00:74:f6:13",
"ip-addresses": [ "fd00:192:168:2::1" ],
"hostname": "v6-vmhomeserver"
}
]
// Additional information for subnet
//"option-data":
},
{
"id": 1921683,
// Subnet for fd00:192:168:3::/48 - static IPs (usable host IP range:
fd00:192:168:3::1 - fd00:192:168:3::ffff)
"subnet": "fd00:192:168:3::/48",
"client-class": "Default",
// Add DHCP IPv6 Pool
"pools":
[ ],
// Add reservations here for subnet
"reservations":
[
{
"hw-address": "52:54:00:74:f6:13",
"ip-addresses": [ "fd00:192:168:3::1" ],
"hostname": "v6-vmhomeserver"
},
{
"duid": "00:04:71:7d:ec:24:45:86:f2:f8:07:fd:6a:c2:53:b6:be:da",
"ip-addresses": [ "fd00:192:168:3::2" ],
"hostname": "v6-homeserver"
},
// VMDatabaseServer
{
//"hw-address": "52:54:00:ef:57:d9",
"duid": "00:03:00:01:52:54:00:ef:57:d9",
"ip-addresses": [ "fd00:192:168:3::3" ],
"hostname": "v6-vmdatabaseserver"
//"option-data":
},
// VMHomeHub
{
//"hw-address": "52:54:00:ed:13:86",
"duid": "00:03:00:01:52:54:00:ed:13:86",
"ip-addresses": [ "fd00:192:168:3::4" ],
"hostname": "v6-vmhomehub"
//"option-data":
}
]
// Additional information for subnet
//"option-data":
},
{
"id": 19216816,
"subnet": "fd00:192:168:f::/48",
"client-class": "Default",
"pools":
[
{
"pool": "fd00:192:168:f::5-fd00:192:168:f::ffff"
}
],
// Add reservations here for subnet
"reservations":
[
// VMHomeServer - interface 'enp2s0'
{
"hw-address": "52:54:00:74:f6:13",
"ip-addresses": [ "fd00:192:0168:f::1" ],
"hostname": "v6-vmhomeserver"
//"option-data":
}
]
// Additional information for subnet
//"option-data":
}
]
}
]
# end of shared-networks
}
}
However, after a few hours the right host name is assigned again, so that
is strange. It seems to happen primarily after Debian updates on 'homehub'
and 'databaseserver' (and occasionally restarts of those)
Best,
C.
Am Mi., 26. Nov. 2025 um 02:58 Uhr schrieb <[email protected]
>:
> Send Kea-users mailing list submissions to
> [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.isc.org/mailman/listinfo/kea-users
> or, via email, send a message with subject or body 'help' to
> [email protected]
>
> You can reach the person managing the list at
> [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Kea-users digest..."
>
>
> Today's Topics:
>
> 1. Re: ddns for a zone in multiple views (Ben Sparks (bzsparks.com))
> 2. Re: The client class design in newer kea versions - 3.0.0
> (Darren Ankney)
> 3. Re: Kea-DHCPv6: No static reservations available (Darren Ankney)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 25 Nov 2025 13:34:15 +0000
> From: "Ben Sparks (bzsparks.com)" <[email protected]>
> To: Kea user's list <[email protected]>
> Subject: Re: [Kea-users] ddns for a zone in multiple views
> Message-ID:
>
> <c9C63CJg1JjeRD9gbEkwvB5Fv2C37RwttAxLNy48G_nNVH8ILuG2XEJ9-bxpZDdCYHtCDPHlNsSssddAdB8B2Tmi74s2AEJoS-PYYdXbz4k=@
> bzsparks.com>
>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Peter,
>
> Thank you, your suggestion pointed me in the correct direction. I'm now
> using the "in-view" zone option to share zones between views. Kea is now
> sending ddns updates to the primary view which are visible to all other
> views now. This also simplified the bind9 configuration.
>
> Thanks again,
>
> Ben
>
> On Tuesday, November 25th, 2025 at 11:26 AM, Peter Davies <[email protected]>
> wrote:
>
> > Hi Ben,
> > In a kea-dhcp-ddns configuration file, each ?dns-domain? definition can
> include
> > a single "key-name" statement, which refers to a previously defined TSig
> key.
> >
> > Since kea-dhcp-ddns does not permit duplicate dns-domain definitions,
> assigning
> > multiple keys to the same domain is not possible.
> >
> > One option to overcome this is to load the same zone in all views on
> your DNS
> > server. This could address the key limitation of the assignment.
> >
> > If multiple forward zones were updated at each lease renewal,
> implementing
> > conflict resolution would be rather complex.
> >
> > Kind Regards Peter
> >
> > On 24/11/2025 16.30, Ben Sparks (bzsparks.com) via Kea-users wrote:
> >
> >> Hello,
> >>
> >> I have a question about kea ddns sending to bind9 with multiple views
> for the same zone. We separate different networks by view for control of
> response policy zones but I would like all users to be able to perform
> forward and reserve resolutions for devices.
> >>
> >> Is something like this possible?
> >>
> >> #bind9 views
> >> view 1
> >> tsig1-key
> >> zone iot.example.com
> >>
> >> view 2
> >> tsig2-key
> >> zone iot.example.com
> >>
> >> view 3
> >> tsig3-key
> >> zone iot.example.com
> >>
> >> #kea ddns
> >> "ddns-domains": [
> >> {
> >> "name": "iot.example.com.",
> >> "key-names": [
> >> "tsig1-key",
> >> "tsig2-key",
> >> "tsig3-key"
> >> ],
> >> "dns-servers": [
> >> { "ip-address": "10.1.1.1" }
> >> ]
> >> }
> >> ]
> >>
> >> "ddns-domains": [
> >> {
> >> "name": "1.2.10.in-addr.arpa.",
> >> "key-names": [
> >> "tsig1-key",
> >> "tsig2-key",
> >> "tsig3-key"
> >> ],
> >> "dns-servers": [
> >> { "ip-address": "10.1.1.1" }
> >> ]
> >> } ]
> >>
> >> Thank you,
> >>
> >> Ben
> >
> > --
> > Peter Davies
> > Support Engineer
> > Internet Systems Corporation
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://lists.isc.org/pipermail/kea-users/attachments/20251125/83101705/attachment-0001.htm
> >
>
> ------------------------------
>
> Message: 2
> Date: Tue, 25 Nov 2025 10:36:26 -0500
> From: Darren Ankney <[email protected]>
> To: "Kea user's list" <[email protected]>
> Subject: Re: [Kea-users] The client class design in newer kea versions
> - 3.0.0
> Message-ID:
> <
> cakabwhjufhdm5e5bxo7dzrj_eev_axebgmlsqp1ve0qvvks...@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Hi,
>
> Kea will evaluate all classes. It won't stop when a match is
> encountered. Clients can be members of multiple classes. It will be
> difficult to help without seeing your configuration, logs and a packet
> capture of the client that is not matching the class.
>
> Thank you,
> Darren Ankney
>
> On Fri, Nov 21, 2025 at 3:50?PM [email protected]
> <[email protected]> wrote:
> >
> > Hello everyone,
> >
> > Last year, I tested on kea 2.6.2 with two different client classes
> Client_class1 and Client_class2 with similar configurations but slightly
> different, then I found my devices couldn?t match the Client_class2 even it
> should match all the criteria. Some other kea users told me that it was
> because I defined the Client_class1 configuration first then the
> Client_class2 configuration. So when the device came online, kea detects it
> match the criteria of Client_class1 first, so it won?t check the rest of
> similar client classes.
> >
> > I am wondering if you have made some improvement on this and allow kea
> to match the most satisfying client class instead of the 1st defined one?
> Thank you.
> >
> >
> >
> >
> >
> >
> >
> > Best Regards,
> >
> >
> >
> > --
> > 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]
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 25 Nov 2025 10:57:37 -0500
> From: Darren Ankney <[email protected]>
> To: "Kea user's list" <[email protected]>
> Subject: Re: [Kea-users] Kea-DHCPv6: No static reservations available
> Message-ID:
> <CAKabWHhfwxCNNiO8aENOc_152A1GNB=
> [email protected]>
> Content-Type: text/plain; charset="UTF-8"
>
> Hi Christoph,
>
> Please can you share your configuration? Whether Kea replaces
> hostnames, generates dynamic hostnames and / or honors the clients
> wishes from the flags in option 39 (all described here:
> https://kea.readthedocs.io/en/stable/arm/dhcp6-srv.html#ddns-for-dhcpv6)
> depend on several settings in the configuration. Option 39 flags and
> their meanings are described in the ARM
> (
> https://kea.readthedocs.io/en/stable/arm/dhcp6-srv.html#when-does-the-kea-dhcp6-server-generate-a-ddns-request
> )
> and in RFC4704 (https://datatracker.ietf.org/doc/html/rfc4704). There
> does seem to be some strange behavior here, but without additional
> information it is impossible to say what is happening and whether is
> *should* be.
>
> As for the log messages, this one "no static reservations available"
> is "ALLOC_ENGINE_V6_ALLOC_UNRESERVED" which is described here:
>
> https://kea.readthedocs.io/en/stable/kea-messages.html#alloc-engine-v6-alloc-unreserved
> and this one "no leases found but reservations" is
> "ALLOC_ENGINE_V6_ALLOC_NO_LEASES_HR" and is described here:
>
> https://kea.readthedocs.io/en/stable/kea-messages.html#alloc-engine-v6-alloc-no-leases-hr
>
> As for the reason for these messages, I could only guess without
> seeing the full configuration.
>
> Thank you,
> Darren Ankney
>
> On Sun, Nov 23, 2025 at 11:43?PM Christoph Markert <[email protected]>
> wrote:
> >
> > Hi there,
> >
> > I do observe a strange behaviour since a while now on KEA DHCPv6 (dual
> stack with KEA DHCP v4 as well, but the problem does not occur on v4!). Kea
> version is 2.6.3
> > Within my v6 configuration file, I do have the following entry:
> > ....
> > // VMDatabaseServer
> > {
> > //"hw-address": "52:54:00:ef:57:d9",
> > "duid": "00:03:00:01:52:54:00:ef:57:d9",
> > "ip-addresses": [ "fd00:192:168:3::3" ],
> > "hostname": "v6-vmdatabaseserver"
> > //"option-data":
> >
> > },
> >
> > ....
> >
> > When restarting VMDatabaseServer, it doesn't get the hostname
> 'v6-vmdatabaseserver' assigned, but
> 'v6-fd00-192-168-3--3.local.markert.live.' Kea assigns the correct IPv6
> address ,but it doesn't recognize the hostname. I don't understand why Kea
> states the following messages in the log: 'no leases found but
> reservations' / 'no static reservations available'.
> >
> > Here is the kea-dhcp6.log file excerpt:
> > 2025-11-24 03:53:47.522 DEBUG [kea-dhcp6.packets/2314.140128965162944]
> DHCP6_BUFFER_RECEIVED received buffer from fe80::5054:ff:feef:57d9:546 to
> ff02::1:2:0 over interface enp2s0
> > 2025-11-24 03:53:47.523 DEBUG [kea-dhcp6.options/2314.140128923162304]
> DHCP6_BUFFER_UNPACK parsing buffer received from fe80::5054:ff:feef:57d9 to
> ff02::1:2 over interface enp2s0
> > 2025-11-24 03:53:47.523 INFO [kea-dhcp6.dhcp6/2314.140128923162304]
> DHCP6_QUERY_LABEL received query: duid=[00:03:00:01:52:54:00:ef:57:d9], [no
> hwaddr info], tid=0xa4e486
> > 2025-11-24 03:53:47.524 DEBUG [kea-dhcp6.eval/2314.140128923162304]
> EVAL_DEBUG_OPTION duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xa4e486: Pushing option 1 with value 0x00030001525400EF57D9
> > 2025-11-24 03:53:47.524 DEBUG [kea-dhcp6.eval/2314.140128923162304]
> EVAL_DEBUG_STRING duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xa4e486: Pushing text string '0x00020000AB11D087EFD048F95BBD'
> > 2025-11-24 03:53:47.524 DEBUG [kea-dhcp6.eval/2314.140128923162304]
> EVAL_DEBUG_EQUAL duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xa4e486: Popping
> 0x307830303032303030304142313144303837454644303438463935424244 and
> 0x00030001525400EF57D9 pushing result 'false'
> > 2025-11-24 03:53:47.524 DEBUG [kea-dhcp6.eval/2314.140128923162304]
> EVAL_DEBUG_NOT duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xa4e486: Popping 'false' pushing 'true'
> > 2025-11-24 03:53:47.525 INFO [kea-dhcp6.packets/2314.140128923162304]
> DHCP6_PACKET_RECEIVED duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr
> info], tid=0xa4e486: RELEASE (type 8) received from fe80::5054:ff:feef:57d9
> to ff02::1:2 on interface enp2s0
> > 2025-11-24 03:53:47.525 DEBUG [kea-dhcp6.packets/2314.140128923162304]
> DHCP6_QUERY_DATA duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xa4e486, packet details: local_address=[ff02::1:2]:0,
> remote_address=[fe80::5054:ff:feef:57d9]:546,
> > msg_type=RELEASE (8), trans_id=0xa4e486,
> > options:
> > type=00001, len=00010: 00:03:00:01:52:54:00:ef:57:d9
> > type=00002, len=00014: 00:01:00:01:2f:25:a8:ed:52:54:00:16:67:1d
> > type=00003(IA_NA), len=00040: iaid=1448103320, t1=0, t2=0,
> > options:
> > type=00005(IAADDR), len=00024: address=fd00:192:168:3::3,
> preferred-lft=0, valid-lft=0
> > type=00008, len=00002: 27332 (uint16)
> > No relays traversed.
> >
> > 2025-11-24 03:53:47.526 DEBUG [kea-dhcp6.packets/2314.140128923162304]
> DHCP6_SUBNET_SELECTED duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr
> info], tid=0xa4e486: the subnet with ID 1921681 was selected for client
> assignments
> > 2025-11-24 03:53:47.526 DEBUG [kea-dhcp6.packets/2314.140128923162304]
> DHCP6_SUBNET_DATA duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xa4e486: the selected subnet details: fd00:192:168:1::/48
> > 2025-11-24 03:53:47.526 DEBUG [kea-dhcp6.hosts/2314.140128923162304]
> HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
> identifier: hwaddr=525400EF57D9
> > 2025-11-24 03:53:47.527 DEBUG [kea-dhcp6.hosts/2314.140128923162304]
> HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=525400EF57D9,
> found 0 host(s)
> > 2025-11-24 03:53:47.527 DEBUG [kea-dhcp6.hosts/2314.140128923162304]
> HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
> identifier: duid=00030001525400EF57D9
> > 2025-11-24 03:53:47.527 DEBUG [kea-dhcp6.hosts/2314.140128923162304]
> HOSTS_CFG_GET_ALL_IDENTIFIER_HOST using identifier:
> duid=00030001525400EF57D9, found host: duid=00030001525400EF57D9
> ipv6_subnet_id=1921683 hostname=v6-vmdatabaseserver ipv4_reservation=(no)
> siaddr=(no) sname=(empty) file=(empty) key=(empty)
> ipv6_reservation0=fd00:192:168:3::3
> > 2025-11-24 03:53:47.527 DEBUG [kea-dhcp6.hosts/2314.140128923162304]
> HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier
> duid=00030001525400EF57D9, found 1 host(s)
> > 2025-11-24 03:53:47.527 DEBUG [kea-dhcp6.dhcp6/2314.140128923162304]
> DHCP6_CLASS_ASSIGNED duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr
> info], tid=0xa4e486: client packet has been assigned to the following
> class: KNOWN
> > 2025-11-24 03:53:47.527 DEBUG [kea-dhcp6.dhcp6/2314.140128923162304]
> DHCP6_CLASSES_ASSIGNED_AFTER_SUBNET_SELECTION
> duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info], tid=0xa4e486:
> client packet has been assigned to the following classes: ALL, Default,
> KNOWN
> > 2025-11-24 03:53:47.527 DEBUG [kea-dhcp6.dhcp6/2314.140128923162304]
> DHCP6_CLASSES_ASSIGNED duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr
> info], tid=0xa4e486: client packet has been assigned on RELEASE message to
> the following classes: ALL, Default, KNOWN
> > 2025-11-24 03:53:47.528 DEBUG [kea-dhcp6.options/2314.140128923162304]
> DHCP6_ADD_STATUS_CODE_FOR_IA duid=[00:03:00:01:52:54:00:ef:57:d9], [no
> hwaddr info], tid=0xa4e486: adding Status Code to IA with iaid=1448103320:
> Success(0) "Lease released. Thank you, please come again."
> > 2025-11-24 03:53:47.528 DEBUG [kea-dhcp6.options/2314.140128923162304]
> DHCP6_ADD_GLOBAL_STATUS_CODE duid=[00:03:00:01:52:54:00:ef:57:d9], [no
> hwaddr info], tid=0xa4e486: adding Status Code to DHCPv6 packet: Success(0)
> "Summary status for all processed IA_NAs"
> > 2025-11-24 03:53:47.528 INFO [kea-dhcp6.packets/2314.140128923162304]
> DHCP6_PACKET_SEND duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xa4e486: trying to send packet REPLY (type 7) from [ff02::1:2]:547 to
> [fe80::5054:ff:feef:57d9]:546 on interface enp2s0
> > 2025-11-24 03:53:47.528 DEBUG [kea-dhcp6.packets/2314.140128923162304]
> DHCP6_RESPONSE_DATA duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xa4e486: responding with packet REPLY (type 7), packet details:
> local_address=[ff02::1:2]:547, remote_address=[fe80::5054:ff:feef:57d9]:546,
> > msg_type=REPLY (7), trans_id=0xa4e486,
> > options:
> > type=00001, len=00010: 00:03:00:01:52:54:00:ef:57:d9
> > type=00002, len=00014: 00:01:00:01:2f:25:a8:ed:52:54:00:16:67:1d
> > type=00003(IA_NA), len=00063: iaid=1448103320, t1=0, t2=0,
> > options:
> > type=00013, len=00047: Success(0) "Lease released. Thank you, please
> come again."
> > type=00013, len=00041: Success(0) "Summary status for all processed
> IA_NAs"
> > No relays traversed.
> >
> > 2025-11-24 03:53:51.527 DEBUG
> [kea-dhcp6.alloc-engine/2314.140128965162944]
> ALLOC_ENGINE_V6_LEASES_RECLAMATION_START starting reclamation of expired
> leases (limit = 100 leases or 250 milliseconds)
> > 2025-11-24 03:53:51.528 DEBUG
> [kea-dhcp6.alloc-engine/2314.140128965162944] ALLOC_ENGINE_V6_LEASE_RECLAIM
> duid=[00:03:00:01:52:54:00:ef:57:d9], [hwtype=1 52:54:00:ef:57:d9]:
> reclaiming expired lease for prefix fd00:192:168:3::3/128
> > 2025-11-24 03:53:51.529 DEBUG
> [kea-dhcp6.alloc-engine/2314.140128965162944] ALLOC_ENGINE_LEASE_RECLAIMED
> successfully reclaimed lease fd00:192:168:3::3
> > 2025-11-24 03:53:51.529 DEBUG
> [kea-dhcp6.alloc-engine/2314.140128965162944]
> ALLOC_ENGINE_V6_LEASES_RECLAMATION_COMPLETE reclaimed 1 leases in 1.437 ms
> > 2025-11-24 03:53:51.529 DEBUG
> [kea-dhcp6.alloc-engine/2314.140128965162944]
> ALLOC_ENGINE_V6_NO_MORE_EXPIRED_LEASES all expired leases have been
> reclaimed
> > 2025-11-24 03:54:01.542 DEBUG
> [kea-dhcp6.alloc-engine/2314.140128965162944]
> ALLOC_ENGINE_V6_RECLAIMED_LEASES_DELETE begin deletion of reclaimed leases
> expired more than 3600 seconds ago
> > 2025-11-24 03:54:01.542 DEBUG
> [kea-dhcp6.alloc-engine/2314.140128965162944]
> ALLOC_ENGINE_V6_RECLAIMED_LEASES_DELETE_COMPLETE successfully deleted 0
> expired-reclaimed leases
> > 2025-11-24 03:54:01.543 DEBUG
> [kea-dhcp6.alloc-engine/2314.140128965162944]
> ALLOC_ENGINE_V6_LEASES_RECLAMATION_START starting reclamation of expired
> leases (limit = 100 leases or 250 milliseconds)
> > 2025-11-24 03:54:01.543 DEBUG
> [kea-dhcp6.alloc-engine/2314.140128965162944]
> ALLOC_ENGINE_V6_LEASES_RECLAMATION_COMPLETE reclaimed 0 leases in 0.053 ms
> > 2025-11-24 03:54:01.543 DEBUG
> [kea-dhcp6.alloc-engine/2314.140128965162944]
> ALLOC_ENGINE_V6_NO_MORE_EXPIRED_LEASES all expired leases have been
> reclaimed
> > 2025-11-24 03:54:11.556 DEBUG
> [kea-dhcp6.alloc-engine/2314.140128965162944]
> ALLOC_ENGINE_V6_LEASES_RECLAMATION_START starting reclamation of expired
> leases (limit = 100 leases or 250 milliseconds)
> > 2025-11-24 03:54:11.556 DEBUG
> [kea-dhcp6.alloc-engine/2314.140128965162944]
> ALLOC_ENGINE_V6_LEASES_RECLAMATION_COMPLETE reclaimed 0 leases in 0.067 ms
> > 2025-11-24 03:54:11.556 DEBUG
> [kea-dhcp6.alloc-engine/2314.140128965162944]
> ALLOC_ENGINE_V6_NO_MORE_EXPIRED_LEASES all expired leases have been
> reclaimed
> > 2025-11-24 03:54:17.038 DEBUG [kea-dhcp6.packets/2314.140128965162944]
> DHCP6_BUFFER_RECEIVED received buffer from fe80::5054:ff:feef:57d9:546 to
> ff02::1:2:0 over interface enp2s0
> > 2025-11-24 03:54:17.039 DEBUG [kea-dhcp6.options/2314.140128914769600]
> DHCP6_BUFFER_UNPACK parsing buffer received from fe80::5054:ff:feef:57d9 to
> ff02::1:2 over interface enp2s0
> > 2025-11-24 03:54:17.039 INFO [kea-dhcp6.dhcp6/2314.140128914769600]
> DHCP6_QUERY_LABEL received query: duid=[00:03:00:01:52:54:00:ef:57:d9], [no
> hwaddr info], tid=0xaeccc3
> > 2025-11-24 03:54:17.039 DEBUG [kea-dhcp6.eval/2314.140128914769600]
> EVAL_DEBUG_OPTION duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xaeccc3: Pushing option 1 with value 0x00030001525400EF57D9
> > 2025-11-24 03:54:17.039 DEBUG [kea-dhcp6.eval/2314.140128914769600]
> EVAL_DEBUG_STRING duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xaeccc3: Pushing text string '0x00020000AB11D087EFD048F95BBD'
> > 2025-11-24 03:54:17.039 DEBUG [kea-dhcp6.eval/2314.140128914769600]
> EVAL_DEBUG_EQUAL duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xaeccc3: Popping
> 0x307830303032303030304142313144303837454644303438463935424244 and
> 0x00030001525400EF57D9 pushing result 'false'
> > 2025-11-24 03:54:17.039 DEBUG [kea-dhcp6.eval/2314.140128914769600]
> EVAL_DEBUG_NOT duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xaeccc3: Popping 'false' pushing 'true'
> > 2025-11-24 03:54:17.039 INFO [kea-dhcp6.packets/2314.140128914769600]
> DHCP6_PACKET_RECEIVED duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr
> info], tid=0xaeccc3: SOLICIT (type 1) received from fe80::5054:ff:feef:57d9
> to ff02::1:2 on interface enp2s0
> > 2025-11-24 03:54:17.039 DEBUG [kea-dhcp6.packets/2314.140128914769600]
> DHCP6_QUERY_DATA duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xaeccc3, packet details: local_address=[ff02::1:2]:0,
> remote_address=[fe80::5054:ff:feef:57d9]:546,
> > msg_type=SOLICIT (1), trans_id=0xaeccc3,
> > options:
> > type=00001, len=00010: 00:03:00:01:52:54:00:ef:57:d9
> > type=00003(IA_NA), len=00012: iaid=1448103320, t1=0, t2=0
> > type=00006, len=00014: 23(uint16) 24(uint16) 31(uint16) 56(uint16)
> 82(uint16) 103(uint16) 144(uint16)
> > type=00008, len=00002: 0 (uint16)
> > type=00014, len=00000:
> > type=00025(IA_PD), len=00012: iaid=1448103320, t1=0, t2=0
> > type=39(CLIENT_FQDN), flags: (N=0, O=0, S=1),
> domain-name='vmdatabaseserver' (partial)
> > No relays traversed.
> >
> > 2025-11-24 03:54:17.040 DEBUG [kea-dhcp6.packets/2314.140128914769600]
> DHCP6_SUBNET_SELECTED duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr
> info], tid=0xaeccc3: the subnet with ID 1921681 was selected for client
> assignments
> > 2025-11-24 03:54:17.040 DEBUG [kea-dhcp6.packets/2314.140128914769600]
> DHCP6_SUBNET_DATA duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xaeccc3: the selected subnet details: fd00:192:168:1::/48
> > 2025-11-24 03:54:17.040 DEBUG [kea-dhcp6.hosts/2314.140128914769600]
> HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
> identifier: hwaddr=525400EF57D9
> > 2025-11-24 03:54:17.040 DEBUG [kea-dhcp6.hosts/2314.140128914769600]
> HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=525400EF57D9,
> found 0 host(s)
> > 2025-11-24 03:54:17.040 DEBUG [kea-dhcp6.hosts/2314.140128914769600]
> HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
> identifier: duid=00030001525400EF57D9
> > 2025-11-24 03:54:17.040 DEBUG [kea-dhcp6.hosts/2314.140128914769600]
> HOSTS_CFG_GET_ALL_IDENTIFIER_HOST using identifier:
> duid=00030001525400EF57D9, found host: duid=00030001525400EF57D9
> ipv6_subnet_id=1921683 hostname=v6-vmdatabaseserver ipv4_reservation=(no)
> siaddr=(no) sname=(empty) file=(empty) key=(empty)
> ipv6_reservation0=fd00:192:168:3::3
> > 2025-11-24 03:54:17.040 DEBUG [kea-dhcp6.hosts/2314.140128914769600]
> HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier
> duid=00030001525400EF57D9, found 1 host(s)
> > 2025-11-24 03:54:17.040 DEBUG [kea-dhcp6.dhcp6/2314.140128914769600]
> DHCP6_CLASS_ASSIGNED duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr
> info], tid=0xaeccc3: client packet has been assigned to the following
> class: KNOWN
> > 2025-11-24 03:54:17.040 DEBUG [kea-dhcp6.dhcp6/2314.140128914769600]
> DHCP6_CLASSES_ASSIGNED_AFTER_SUBNET_SELECTION
> duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info], tid=0xaeccc3:
> client packet has been assigned to the following classes: ALL, Default,
> KNOWN
> > 2025-11-24 03:54:17.040 DEBUG [kea-dhcp6.ddns/2314.140128914769600]
> DHCP6_DDNS_RECEIVE_FQDN duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr
> info], tid=0xaeccc3: received DHCPv6 Client FQDN option:
> type=39(CLIENT_FQDN), flags: (N=0, O=0, S=1),
> domain-name='vmdatabaseserver' (partial)
> > 2025-11-24 03:54:17.041 DEBUG [kea-dhcp6.ddns/2314.140128914769600]
> DHCP6_DDNS_RESPONSE_FQDN_DATA duid=[00:03:00:01:52:54:00:ef:57:d9], [no
> hwaddr info], tid=0xaeccc3: including FQDN option in the server's response:
> type=39(CLIENT_FQDN), flags: (N=0, O=0, S=1), domain-name='' (partial)
> > 2025-11-24 03:54:17.041 DEBUG
> [kea-dhcp6.alloc-engine/2314.140128914769600]
> ALLOC_ENGINE_V6_ALLOC_LEASES_HR leases and static reservations found for
> client duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info], tid=0xaeccc3
> > 2025-11-24 03:54:17.041 DEBUG
> [kea-dhcp6.alloc-engine/2314.140128914769600]
> ALLOC_ENGINE_V6_CALCULATED_PREFERRED_LIFETIME
> duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info], tid=0xaeccc3: using
> a calculated preferred-lifetime of 19800
> > 2025-11-24 03:54:17.042 DEBUG
> [kea-dhcp6.alloc-engine/2314.140128914769600]
> ALLOC_ENGINE_V6_ALLOC_NO_LEASES_HR no leases found but reservations exist
> for client duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xaeccc3
> > 2025-11-24 03:54:17.042 DEBUG
> [kea-dhcp6.alloc-engine/2314.140128914769600]
> ALLOC_ENGINE_V6_ALLOC_UNRESERVED no static reservations available - trying
> to dynamically allocate leases for client
> duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info], tid=0xaeccc3
> > 2025-11-24 03:54:17.042 WARN
> [kea-dhcp6.alloc-engine/2314.140128914769600]
> ALLOC_ENGINE_V6_ALLOC_FAIL_SHARED_NETWORK
> duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info], tid=0xaeccc3:
> failed to allocate a lease in the shared network markert-live-local: 0
> subnets have no available leases, 5 subnets have no matching pools
> > 2025-11-24 03:54:17.042 WARN
> [kea-dhcp6.alloc-engine/2314.140128914769600]
> ALLOC_ENGINE_V6_ALLOC_FAIL_NO_POOLS duid=[00:03:00:01:52:54:00:ef:57:d9],
> [no hwaddr info], tid=0xaeccc3: no pools were available for the lease
> allocation
> > 2025-11-24 03:54:17.042 WARN
> [kea-dhcp6.alloc-engine/2314.140128914769600]
> ALLOC_ENGINE_V6_ALLOC_FAIL_CLASSES duid=[00:03:00:01:52:54:00:ef:57:d9],
> [no hwaddr info], tid=0xaeccc3: Failed to allocate an IPv6 address for
> client with classes: ALL, Default, KNOWN
> > 2025-11-24 03:54:17.042 DEBUG [kea-dhcp6.options/2314.140128914769600]
> DHCP6_ADD_STATUS_CODE_FOR_IA duid=[00:03:00:01:52:54:00:ef:57:d9], [no
> hwaddr info], tid=0xaeccc3: adding Status Code to IA with iaid=1448103320:
> NoPrefixAvail(6) "Sorry, no prefixes could be allocated."
> > 2025-11-24 03:54:17.042 DEBUG [kea-dhcp6.dhcp6/2314.140128914769600]
> DHCP6_CLASSES_ASSIGNED duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr
> info], tid=0xaeccc3: client packet has been assigned on SOLICIT message to
> the following classes: ALL, Default, KNOWN
> > 2025-11-24 03:54:17.042 INFO [kea-dhcp6.packets/2314.140128914769600]
> DHCP6_PACKET_SEND duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xaeccc3: trying to send packet ADVERTISE (type 2) from [ff02::1:2]:547
> to [fe80::5054:ff:feef:57d9]:546 on interface enp2s0
> > 2025-11-24 03:54:17.043 DEBUG [kea-dhcp6.packets/2314.140128914769600]
> DHCP6_RESPONSE_DATA duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xaeccc3: responding with packet ADVERTISE (type 2), packet details:
> local_address=[ff02::1:2]:547, remote_address=[fe80::5054:ff:feef:57d9]:546,
> > msg_type=ADVERTISE (2), trans_id=0xaeccc3,
> > options:
> > type=00001, len=00010: 00:03:00:01:52:54:00:ef:57:d9
> > type=00002, len=00014: 00:01:00:01:2f:25:a8:ed:52:54:00:16:67:1d
> > type=00003(IA_NA), len=00040: iaid=1448103320, t1=15840, t2=27720,
> > options:
> > type=00005(IAADDR), len=00024: address=fd00:192:168:3::3,
> preferred-lft=19800, valid-lft=31680
> > type=00023, len=00016: fd00:192:168:3::1
> > type=00024, len=00020: "local.markert.live." (fqdn)
> > type=00025(IA_PD), len=00056: iaid=1448103320, t1=0, t2=0,
> > options:
> > type=00013, len=00040: NoPrefixAvail(6) "Sorry, no prefixes could be
> allocated."
> > type=39(CLIENT_FQDN), flags: (N=0, O=0, S=1), domain-name='' (partial)
> > No relays traversed.
> >
> > 2025-11-24 03:54:18.139 DEBUG [kea-dhcp6.packets/2314.140128965162944]
> DHCP6_BUFFER_RECEIVED received buffer from fe80::5054:ff:feef:57d9:546 to
> ff02::1:2:0 over interface enp2s0
> > 2025-11-24 03:54:18.140 DEBUG [kea-dhcp6.options/2314.140128906376896]
> DHCP6_BUFFER_UNPACK parsing buffer received from fe80::5054:ff:feef:57d9 to
> ff02::1:2 over interface enp2s0
> > 2025-11-24 03:54:18.140 INFO [kea-dhcp6.dhcp6/2314.140128906376896]
> DHCP6_QUERY_LABEL received query: duid=[00:03:00:01:52:54:00:ef:57:d9], [no
> hwaddr info], tid=0xfa827
> > 2025-11-24 03:54:18.140 DEBUG [kea-dhcp6.eval/2314.140128906376896]
> EVAL_DEBUG_OPTION duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xfa827: Pushing option 1 with value 0x00030001525400EF57D9
> > 2025-11-24 03:54:18.141 DEBUG [kea-dhcp6.eval/2314.140128906376896]
> EVAL_DEBUG_STRING duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xfa827: Pushing text string '0x00020000AB11D087EFD048F95BBD'
> > 2025-11-24 03:54:18.141 DEBUG [kea-dhcp6.eval/2314.140128906376896]
> EVAL_DEBUG_EQUAL duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xfa827: Popping
> 0x307830303032303030304142313144303837454644303438463935424244 and
> 0x00030001525400EF57D9 pushing result 'false'
> > 2025-11-24 03:54:18.141 DEBUG [kea-dhcp6.eval/2314.140128906376896]
> EVAL_DEBUG_NOT duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xfa827: Popping 'false' pushing 'true'
> > 2025-11-24 03:54:18.141 INFO [kea-dhcp6.packets/2314.140128906376896]
> DHCP6_PACKET_RECEIVED duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr
> info], tid=0xfa827: REQUEST (type 3) received from fe80::5054:ff:feef:57d9
> to ff02::1:2 on interface enp2s0
> > 2025-11-24 03:54:18.141 DEBUG [kea-dhcp6.packets/2314.140128906376896]
> DHCP6_QUERY_DATA duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xfa827, packet details: local_address=[ff02::1:2]:0,
> remote_address=[fe80::5054:ff:feef:57d9]:546,
> > msg_type=REQUEST (3), trans_id=0xfa827,
> > options:
> > type=00001, len=00010: 00:03:00:01:52:54:00:ef:57:d9
> > type=00002, len=00014: 00:01:00:01:2f:25:a8:ed:52:54:00:16:67:1d
> > type=00003(IA_NA), len=00040: iaid=1448103320, t1=0, t2=0,
> > options:
> > type=00005(IAADDR), len=00024: address=fd00:192:168:3::3,
> preferred-lft=0, valid-lft=0
> > type=00006, len=00012: 23(uint16) 24(uint16) 31(uint16) 56(uint16)
> 103(uint16) 144(uint16)
> > type=00008, len=00002: 0 (uint16)
> > type=39(CLIENT_FQDN), flags: (N=0, O=0, S=1),
> domain-name='vmdatabaseserver' (partial)
> > No relays traversed.
> >
> > 2025-11-24 03:54:18.141 DEBUG [kea-dhcp6.packets/2314.140128906376896]
> DHCP6_SUBNET_SELECTED duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr
> info], tid=0xfa827: the subnet with ID 1921681 was selected for client
> assignments
> > 2025-11-24 03:54:18.141 DEBUG [kea-dhcp6.packets/2314.140128906376896]
> DHCP6_SUBNET_DATA duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xfa827: the selected subnet details: fd00:192:168:1::/48
> > 2025-11-24 03:54:18.142 DEBUG [kea-dhcp6.hosts/2314.140128906376896]
> HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
> identifier: hwaddr=525400EF57D9
> > 2025-11-24 03:54:18.142 DEBUG [kea-dhcp6.hosts/2314.140128906376896]
> HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=525400EF57D9,
> found 0 host(s)
> > 2025-11-24 03:54:18.142 DEBUG [kea-dhcp6.hosts/2314.140128906376896]
> HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using
> identifier: duid=00030001525400EF57D9
> > 2025-11-24 03:54:18.142 DEBUG [kea-dhcp6.hosts/2314.140128906376896]
> HOSTS_CFG_GET_ALL_IDENTIFIER_HOST using identifier:
> duid=00030001525400EF57D9, found host: duid=00030001525400EF57D9
> ipv6_subnet_id=1921683 hostname=v6-vmdatabaseserver ipv4_reservation=(no)
> siaddr=(no) sname=(empty) file=(empty) key=(empty)
> ipv6_reservation0=fd00:192:168:3::3
> > 2025-11-24 03:54:18.142 DEBUG [kea-dhcp6.hosts/2314.140128906376896]
> HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier
> duid=00030001525400EF57D9, found 1 host(s)
> > 2025-11-24 03:54:18.142 DEBUG [kea-dhcp6.dhcp6/2314.140128906376896]
> DHCP6_CLASS_ASSIGNED duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr
> info], tid=0xfa827: client packet has been assigned to the following class:
> KNOWN
> > 2025-11-24 03:54:18.142 DEBUG [kea-dhcp6.dhcp6/2314.140128906376896]
> DHCP6_CLASSES_ASSIGNED_AFTER_SUBNET_SELECTION
> duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info], tid=0xfa827: client
> packet has been assigned to the following classes: ALL, Default, KNOWN
> > 2025-11-24 03:54:18.142 DEBUG [kea-dhcp6.ddns/2314.140128906376896]
> DHCP6_DDNS_RECEIVE_FQDN duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr
> info], tid=0xfa827: received DHCPv6 Client FQDN option:
> type=39(CLIENT_FQDN), flags: (N=0, O=0, S=1),
> domain-name='vmdatabaseserver' (partial)
> > 2025-11-24 03:54:18.143 DEBUG [kea-dhcp6.ddns/2314.140128906376896]
> DHCP6_DDNS_RESPONSE_FQDN_DATA duid=[00:03:00:01:52:54:00:ef:57:d9], [no
> hwaddr info], tid=0xfa827: including FQDN option in the server's response:
> type=39(CLIENT_FQDN), flags: (N=0, O=0, S=1), domain-name='' (partial)
> > 2025-11-24 03:54:18.143 DEBUG
> [kea-dhcp6.alloc-engine/2314.140128906376896]
> ALLOC_ENGINE_V6_ALLOC_LEASES_HR leases and static reservations found for
> client duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info], tid=0xfa827
> > 2025-11-24 03:54:18.143 DEBUG
> [kea-dhcp6.alloc-engine/2314.140128906376896]
> ALLOC_ENGINE_V6_CALCULATED_PREFERRED_LIFETIME
> duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info], tid=0xfa827: using
> a calculated preferred-lifetime of 19800
> > 2025-11-24 03:54:18.143 DEBUG [kea-dhcp6.dhcp6/2314.140128906376896]
> DHCP6_CLASSES_ASSIGNED duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr
> info], tid=0xfa827: client packet has been assigned on REQUEST message to
> the following classes: ALL, Default, KNOWN
> > 2025-11-24 03:54:18.144 DEBUG [kea-dhcp6.ddns/2314.140128906376896]
> DHCP6_DDNS_FQDN_GENERATED duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr
> info], tid=0xfa827: generated FQDN for the client:
> v6-fd00-192-168-3--3.local.markert.live.
> > 2025-11-24 03:54:18.144 DEBUG [kea-dhcp6.ddns/2314.140128906376896]
> DHCP6_DDNS_CREATE_ADD_NAME_CHANGE_REQUEST
> duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info], tid=0xfa827:
> created name change request: Type: 0 (CHG_ADD)
> > Forward Change: yes
> > Reverse Change: yes
> > FQDN: [v6-fd00-192-168-3--3.local.markert.live.]
> > IP Address: [fd00:192:168:3::3]
> > DHCID:
> [000201A2DBEB419810CCF195778B161D49A9142E8BF2C86B4AF212031D611D82FFFFC3]
> > Lease Expires On: 19700101000000
> > Lease Length: 10560
> > Conflict Resolution Mode: check-with-dhcid
> >
> > 2025-11-24 03:54:18.145 INFO [kea-dhcp6.packets/2314.140128906376896]
> DHCP6_PACKET_SEND duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xfa827: trying to send packet REPLY (type 7) from [ff02::1:2]:547 to
> [fe80::5054:ff:feef:57d9]:546 on interface enp2s0
> > 2025-11-24 03:54:18.145 DEBUG [kea-dhcp6.packets/2314.140128906376896]
> DHCP6_RESPONSE_DATA duid=[00:03:00:01:52:54:00:ef:57:d9], [no hwaddr info],
> tid=0xfa827: responding with packet REPLY (type 7), packet details:
> local_address=[ff02::1:2]:547, remote_address=[fe80::5054:ff:feef:57d9]:546,
> > msg_type=REPLY (7), trans_id=0xfa827,
> > options:
> > type=00001, len=00010: 00:03:00:01:52:54:00:ef:57:d9
> > type=00002, len=00014: 00:01:00:01:2f:25:a8:ed:52:54:00:16:67:1d
> > type=00003(IA_NA), len=00040: iaid=1448103320, t1=15840, t2=27720,
> > options:
> > type=00005(IAADDR), len=00024: address=fd00:192:168:3::3,
> preferred-lft=19800, valid-lft=31680
> > type=00023, len=00016: fd00:192:168:3::1
> > type=00024, len=00020: "local.markert.live." (fqdn)
> > type=39(CLIENT_FQDN), flags: (N=0, O=0, S=1),
> domain-name='v6-fd00-192-168-3--3.local.markert.live.' (full)
> > No relays traversed.
> > --
> > 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]
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
>
> ISC funds the development of this software with paid support
> subscriptions. Contact us at https://www.isc.org/contact/ for more
> information.
>
> Kea-users mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/kea-users
>
>
> ------------------------------
>
> End of Kea-users Digest, Vol 137, Issue 23
> ******************************************
>
--
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]
