Client upstream settings are ignored on DNS-over-TLS requests.

[moridew]

Hello.
Thank you for providing good software.

Internal DNS is being operated separately as needed.
In the client settings, the 10.9.8.0/24 range was set to "내부IP".
In the "내부IP" client, the "morid.......e domain" was set to 127.0.0.1:57053 upstream.

Now, in plaintext DNS, it works fine
When it is DNS-over-TLS, it responds by asking the global upstream to ignore this setting.

Am I doing something wrong?
Please help me
.

[ainar-g]

Hello. I cannot reproduce this. Are you using a TLS domain name with a ClientID?

[moridew]

thank you reply.

Yes, that's right. Using clientId.
When using clientid, is it possible to query internal dns only on specific ip?

[ainar-g]

You should either add that ClientID to the client (by pressing the ➕ button and pasting the ClientID there) or remove it from the hostname that devices use so that AGH could detect the client by the IP subnet.

[moridew]

Thank you, if you remove the clientID from the DoT, it will act as a successfully configured subnet. However, I would like to have a way to operate subnet classification even when the clientID is set. Because DoT-enabled devices are Android devices, but only internal DNS servers can be used when accessing the internal network

[moridew]

I achieved what I wanted.

The reason why I'm going to do this is,
When looking up a specific domain on the internal network, it was to respond to the internal IP.
(If you receive an external IP response from the internal network and connect to the internal server via NAT Loopback, the internal server logs the internal IP of the router.)

To do this, I set up the client and let the specific domain use a separate DNS inside. However, if clientID is set in DoT or DoH, the client setting is not applied.

I decided to use Custom filtering rules.

||morid..........................e^$dnsrewrite=10.9.8.141,client='10.9.8.0/24'

When I apply the above rule, it finally works as I want.

On Android devices with DoT settings,
When it is an external network, IP is answered through cloudflare or Google DNS
On the internal network, 10.9.8.141 is answered through the dnsrewite rule.

Thank you. Have a nice day!