No subject

[Darren Ankney]

Hi Christian,

This is why:

Nov 21 16:41:39 dnsdcp kea-dhcp-ddns[837]: FQDN: [node2.]

Add

"ddns-qualifying-suffix": "cluster01.darkwing.net",

to the global area of your Kea DHCP4 configuration.  The client only
sent 'node2.' it seems.

Thank you,

Darren Ankney

On Tue, Nov 21, 2023 at 10:53 AM Christian Floreck
<ch.floreck at outlook.de> wrote:
>
> Hi
>
>
>
> I  try to set up an DHCP request from an Client named  node2.cluster01.darkwing.net.
>
> The IP is generated fine, however  syslog reads:
>
>
>
> Nov 21 16:41:39 dnsdcp kea-dhcp4[840]: 2023-11-21 16:41:39.909 INFO  [kea-dhcp4.leases/840.140172516175488] DHCP4_LEASE_ADVERT [hwtype=1 08:00:27:b0:d3:33], cid=[no info], tid=0x1cef137                 9: lease 192.168.100.151 will be advertised
>
> Nov 21 16:41:39 dnsdcp kea-dhcp4[840]: 2023-11-21 16:41:39.910 INFO  [kea-dhcp4.leases/840.140172516175488] DHCP4_LEASE_ALLOC [hwtype=1 08:00:27:b0:d3:33], cid=[no info], tid=0x1cef1379                 : lease 192.168.100.151 has been allocated for 4000 seconds
>
> Nov 21 16:41:39 dnsdcp kea-dhcp-ddns[837]: WARN  DHCP_DDNS_NO_MATCH No DNS servers match FQDN node2.
>
> Nov 21 16:41:39 dnsdcp kea-dhcp-ddns[837]: ERROR DHCP_DDNS_NO_FWD_MATCH_ERROR Request ID 000001C04E5E0D7E9384272760E4FC21A3850EEBC3A679910D091F7288B0C2019CE272: the configured list of f                 orward DDNS domains does not contain a match for: Type: 1 (CHG_REMOVE)
>
> Nov 21 16:41:39 dnsdcp kea-dhcp-ddns[837]: Forward Change: yes
>
> Nov 21 16:41:39 dnsdcp kea-dhcp-ddns[837]: Reverse Change: yes
>
> Nov 21 16:41:39 dnsdcp kea-dhcp-ddns[837]: FQDN: [node2.]
>
> Nov 21 16:41:39 dnsdcp kea-dhcp-ddns[837]: IP Address: [192.168.100.151]
>
> Nov 21 16:41:39 dnsdcp kea-dhcp-ddns[837]: DHCID: [000001C04E5E0D7E9384272760E4FC21A3850EEBC3A679910D091F7288B0C2019CE272]
>
> Nov 21 16:41:39 dnsdcp kea-dhcp-ddns[837]: Lease Expires On: 20231121160234
>
> Nov 21 16:41:39 dnsdcp kea-dhcp-ddns[837]: Lease Length: 1333
>
> Nov 21 16:41:39 dnsdcp kea-dhcp-ddns[837]: Conflict Resolution: yes
>
> Nov 21 16:41:39 dnsdcp kea-dhcp-ddns[837]:   The request has been discarded.
>
> Nov 21 16:42:57 dnsdcp NetworkManager[657]: <info>  [1700581377.6288] dhcp4 (enp0s10): state changed new lease, address=192.168.200.101
>
> ^C
>
>
>
> As far as i got it I have to define the Forward ddns Domains in kea-dhcp-ddns.conf.
>
> Which I’ve done:
>
>
>
> "forward-ddns" : {
>
>       "ddns-domains" : [
>
>           {    "name": "darkwing.net.",
>
>                "key-name": "dhcp1-ns1",
>
>                "dns-servers":
>
>                         [
>
>                         { "ip-address": "192.168.100.41" }
>
>                         ]
>
>                 },
>
>         {        "name": "cluster01.darkwing.net.",
>
>                "key-name": "dhcp1-ns1",
>
>                "dns-servers":
>
>                         [
>
>                         { "ip-address": "192.168.100.41" }
>
>                         ]
>
>           }
>
>       ]
>
>   },
>
>
>
> It is defined lin named.conf.local, too
>
>
>
> zone "cluster01.darkwing.net" IN {
>
>         type master;
>
>         file "/var/lib/bind/db.cluster01.darkwing.net.zone";
>
>         update-policy { grant dhcp1-ns1 wildcard *.darkwing.net A DHCID;};
>
> };
>
>
>
> I guess, it is an „admin too stupid errror“…
>
> But which?
>
> Thx
>
> Christian
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Gesendet von Mail für Windows
>
>
>
> --
> ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
>
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users