Project

General

Profile

Actions

Bug #15849

closed

KEA is not appending the DNS Domain suffix as ISC did

Added by Dennis Adler 6 days ago. Updated 5 days ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
DHCP Server (IPv4)
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Release Notes:
Default
Affected Plus Version:
24.03
Affected Architecture:
All

Description

I've set a domain for my router (home.me). The URL for my router is "sg-router.home.me", and my self-signed keys used for SSL refer to it that way. Likewise, when my Windows computers and other devices are either assigned a static IP from a reserved range or get a DHCP-chosen address, their host names had the "home.me" suffix attached (yes, I know that ME is a TLD on the Internet -- I am willingly giving up any public sites whose domain is "home.me").

KEA does not replicate this behavior, and because of that all sorts of things are breaking on my network. Browser links that refer to "computer1.home.me" do not resolve; it instead resolves only as "computer1". Worse yet, dialing in from VPN no longer does name resolution (computer1 does not resolve). Even worse, my self-signed certificates for other services (e.g. Unifi controller) not only do not resolve, but using the hostname (sans suffix) causes browser security warnings.

Can you please update KEA so it behaves as ISC did (and as the pfSense documentation for DHCP lays out) -- append the DNS suffix?

Actions

Also available in: Atom PDF