Linked IPs feature does not work when using encrypted queries

[trmdi]

Issue Details

My public ipv4 is linked to my Adguard DNS device as instructed here [1]
I do a test by adding a User rule to rewrite example.com -> 1.2.3.4 in my Server setting and see that:

• it works as expected for plain queries to 94.140.14.49
• but not work for DoT/DoH queries. This means when the user chooses the 'Auto' option in Private DNS settings on Android or browsers, the Linked IPs feature will not work.

You can see that in this screenshot:

(dig +short example.com @94.140.14.49 +https behaves the same)

Is it a bug?

[1] https://adguard-dns.io/kb/private-dns/connect-devices/other-options/linked-ip/

[ameshkov]

For DoT you're supposed to use the domain name with your device ID

[trmdi]

For DoT you're supposed to use the domain name with your device ID

Yes, I know that.
But the ip address is still useful in some cases, for example, you set it up in the DHCP server and any client joining your wifi network will benefit from it without doing anything else...
I think the servers for linked IPs (94.140.14.49 and 94.140.14.59) should do their job consistently, regardless of whether the queries are encrypted or not.

[trmdi]

openDNS does the same for both with and without tls:

Both DoT and Linked IP are great features. It would be really great if AG could combine these two things.