Feature Request: Consistent Client Identification in Dashboard/Logs Based on Server Endpoint (localEndPointGroupMap)

[0neTX]

Hello Technitium DNS Team,

First, thank you for this fantastic DNS server software!

I have a use case where I'm using the localEndPointGroupMap feature in the Advanced Blocking App to apply specific policies to a single logical device. This device connects to the DNS server using a dedicated FQDN endpoint (e.g., mydevice.dns.example.com via DoH/DoT/DoQ), and this works perfectly for policy enforcement.

The device might connect from my local LAN (with a consistent private IP) or from external WAN networks (with various dynamic public IPs). While the correct policies are always applied thanks to the localEndPointGroupMap matching mydevice.dns.example.com to my "mydevice_policy" group, the DNS dashboard and query logs always show the client's current source IP address.
I've reviewed existing discussions like:

• Identifying public clients (client ID?) for advanced blocking: Identifying public clients (client ID?) for advanced blocking #860
• [Feature request] Client identifier: [Feature request] Client identifier #1199

While these discuss client identification for policy application (which localEndPointGroupMap with FQDNs handles well), my request focuses on the visual representation of the client in the dashboard.

The Problem/Feature Request:

I would like to request a feature that allows for a more consistent visual identification of such a client in the Technitium DNS dashboard and logs. Ideally, I'd like to see a persistent, user-defined name (e.g., "MyDevice" or the name of the policy group it matched, like "mydevice_policy") displayed for all queries that come through that specific server endpoint FQDN (mydevice.dns.example.com), regardless of the client's changing source IP address. Quite similar with AGH behaviour.

Currently, if the device is on LAN, I might see 192.168.X.Y (or its PTR record if set). If it's on WAN, I see [Public IP 1], then [Public IP 2], etc. This makes it appear as multiple different clients over time, even though I know (and the server "knows" for policy purposes) that all these queries are from the same logical device because they are all directed to the mydevice.dns.example.com endpoint.

Desired Outcome:

It would be incredibly helpful if the dashboard could offer an option to display a "friendly name" or "alias" for clients based on the localEndPointGroupMap FQDN key they connected to, or the policy group name associated with that key. This would allow users to easily identify and track activity from specific configured devices/users that leverage unique server FQDNs for their DNS queries, especially when their source IPs are dynamic.

For example, instead of just seeing:

192.168.1.10
80.X.Y.Z
90.A.B.C

All of which used mydevice.dns.example.com (mapped to "mydevice_policy"), I would ideally see something like:

"MyDevice" (192.168.1.10)
"MyDevice" (80.X.Y.Z)
"MyDevice" (90.A.B.C) Or even just "MyDevice" consistently, with the IP perhaps available in a detailed view.

Current Workaround/Limitations:

PTR records help for static LAN IPs but are not feasible for dynamic WAN IPs.
The current localEndPointGroupMap correctly handles policy application but doesn't affect the client's displayed identity in the dashboard in this way.

This feature would significantly enhance the usability of the dashboard for tracking specific devices/users who are identified by the unique server endpoint they connect to, rather than by their IP address alone.

Thank you for considering this feature request!

[ShreyasZare]

Thanks for the feature request. Will evaluate how this can be implemented and let you know.