Reply clientid to upstream

[DunkanAidaho]

Prerequisites

• [X] I have checked the Wiki and Discussions and found no answer

• [X] I have searched other issues and found no duplicates

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

The problem

There are complex cases of using ADH, for example using nextdns and others as an upstream. In cases where the main DNS server on the local network is ADH, and the upstream server is, for example, nextdns, then from the point of view of nextdns all requests come from one host (the external IP behind which ADH is located). the protocols used are not important I would like it to be possible to enable the transfer of ClientID to upstream.

Proposed solution

Forward ClientID to upstream

Alternatives considered and additional information

No response

[ainar-g]

Doesn't NextDNS support identifying their clients through e.g. TLS hostnames? If so, why not just give custom upstreams to the clients that you want to be proxied?

[DunkanAidaho]

why not just give custom upstreams to the clients that you want to be proxied

To do this, each client will need to register the upstream using the -.dns.nextdns.io syntax. This is not convenient for a large number of devices on the network as it will take a lot of time. Instead, my suggestion is to optionally allow adh client-id to be forwarded to the upstream host's TLS