pfSense 2.8.1: Kea DHCPv6 IPv6 Static Lease Allocation Fails (ALLOC_ENGINE_V6_ALLOC_FAIL_SUBNET) for Known Client, Inconsistent DNS

Tomahawk

@hernanirvaz said in pfSense 2.8.1: Kea DHCPv6 IPv6 Static Lease Allocation Fails (ALLOC_ENGINE_V6_ALLOC_FAIL_SUBNET) for Known Client, Inconsistent DNS:

servers (with systemd-networkd) & register on the incorrect domain unknown.home.arpa
desktops (with NetworkManager) & register on the correct domain home.arpa

I have this issue as well
I tried to install commit 146391a mentioned in https://forum.netgate.com/topic/199239/kea-dhcpv6-dns-registration using System-Patches but the clients are still beeing registered with wrong domain.
hostname -d at the ubuntu server cli shows the correct domain name

Gertjan

@Tomahawk said in pfSense 2.8.1: Kea DHCPv6 IPv6 Static Lease Allocation Fails (ALLOC_ENGINE_V6_ALLOC_FAIL_SUBNET) for Known Client, Inconsistent DNS:

hostname -d at the ubuntu server cli shows the correct domain name

The pfSense DHCP daemon can't do that ;)

The issue isn't that your device doesn't have a name.
The issue is (imho) that the device doesn't specify it host name to the pfSense DHCP server. The other thread makes mention of this, so it could be corrected.

See for your :

Diagnostics > Packet Capture ,and tell pfSense what you want to see :
Interface - for example "LAN".
View Options : Full.
Protocole : UDP of course.
Ports : DHCP : type "67 68"
and hit the green start button.

Now run to the device that is marked 'unknown' and ask it to renew the lease.
For a Microsoft OS you have to type

ipconfig /renew

and back on pfSense you see now the DHCP request, with info, from the device,
and the DHCP lease proposal coming from the pfSense DHCP server.

Btw : you'll se probably also other DHCP traffic, if you have other devices on your network.

You can prepare a more specific filter by entering the MAC of your device.

IonutIT

@Tomahawk said in pfSense 2.8.1: Kea DHCPv6 IPv6 Static Lease Allocation Fails (ALLOC_ENGINE_V6_ALLOC_FAIL_SUBNET) for Known Client, Inconsistent DNS:

I have this issue as well
I tried to install commit 146391a mentioned in https://forum.netgate.com/topic/199239/kea-dhcpv6-dns-registration using System-Patches but the clients are still beeing registered with wrong domain.
hostname -d at the ubuntu server cli shows the correct domain name

I had this issue myself with only Ubuntu Server being affected.

Turns out by default in Ubuntu Server systemd-resolved is not configured to use the domains passed by DHCP (either v4 or v6).

So all I had to do was to edit /etc/systemd/networks/networkd.conf to have UseDomain=true and after reboot, by magic the hostname is properly registered in Unbound without the 'unknown' part.

hernanirvaz

@IonutIT thanks