Bug #15343
closed
DHCP host names for Windows 10/11 hosts have "." at the end
Added by Daryl Morse 2 months ago.
Updated about 2 months ago.
Affected Architecture:
amd64
Description
Since changing to Kea DHCP, DHCP host names for Windows 10 and Windows 11 hosts are being created with a "." at the end.
This does not happen for types of hosts.
This does not affect DHCPv6.
Files
Hello Daryl,
Can you please provide a screenshot or additional context for this? There isn't enough information in this bug report. Where are you seeing the "extra dot"?
The hosts with yellow highlighting are windows 10/11. The others are IoT or mobile.
- Status changed from New to Not a Bug
That is how the clients are sending their own hostname. It's that way in the lease database, and Kea is just recording what they sent.
This isn't negatively impacting anything.
DHCPv6 is not adding the "." to the hostnames for Windows 10 / 11 hosts. It's behaving differently than DHCPv4. If DHCPv6 isn't displaying the trailing ".", why is DHCPv4?
It's there in the Kea IPv6 lease database but the status page code trims it so it's not shown in the GUI. Just a minor cosmetic difference, doesn't indicate anything is wrong.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 