AdGuard Home DHCP Server not assigning Connection-specific DNS Suffix for Windows clients

[ZolliusMeistrus]

Prerequisites

• I have checked the Wiki and Discussions and found no answer

• I have searched other issues and found no duplicates

• I want to request a feature or enhancement and not ask a question

The problem

When AdGuard Home DHCP Server is activated, and in the AdGuardHome.yaml file the entry "local_domain_name" has been assigned a custom value, then when Windows clients are assigned an IP address, their "Connection-specific DNS Suffix" is not updated to this custom value, and they are not able to resolve clients in this domain without specifying the FQDN when trying to resolve. For example - when resolving "hostname" in Windows CMD, then no results are returned. When resolving "hostname.custom.domain" then the IP is returned from the AdGuard Home DHCP cache.

Proposed solution

Add the option of using a custom domain name in the AdGuard Home web interface for DHCP Server, as well as set the "Connection-specific DNS Suffix" for Windows clients. If the Pi-Hole can do this, I'm sure AdGuard Home can also do this.

Alternatives considered and additional information

No response

[ainar-g]

Duplicate of #6749