Project

General

Profile

Actions

Bug #15343

closed

DHCP host names for Windows 10/11 hosts have "." at the end

Added by Daryl Morse about 2 months ago. Updated about 2 months ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
DHCP (IPv4)
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.7.x
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

Capture.PNG (32.8 KB) Capture.PNG Daryl Morse, 03/17/2024 04:20 PM
Actions #1

Updated by Kris Phillips about 2 months ago

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"?

Actions #2

Updated by Daryl Morse about 2 months ago

The hosts with yellow highlighting are windows 10/11. The others are IoT or mobile.

Actions #3

Updated by Jim Pingle about 2 months ago

  • 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.

Actions #4

Updated by Daryl Morse about 2 months ago

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?

Actions #5

Updated by Jim Pingle about 2 months ago

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.

Actions

Also available in: Atom PDF