Celexi
commented
3 weeks ago looks like this got fixed with v0.107.52, although there is no UI setting for this yet.
Closed Celexi closed 3 weeks ago
Celexi
commented
3 weeks ago looks like this got fixed with v0.107.52, although there is no UI setting for this yet.
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 report a bug and not ask a question or ask for help
[X] I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)
Platform (OS and CPU architecture)
Custom (please mention in the description)
Installation
Other (please mention in the description)
Setup
On one machine
AdGuard Home version
0.107.48
Action
Replace the following command with the one you're calling or a description of the failing action:
Expected result
The lookup should go first via ipv6 if that is available before falling back to ipv4. They correctly go via ipv6 first in windows or android.
Actual result
all tls requests are going via ipv4, I have tried both in adguard dns and nextdns so I could see the logs.
Additional information and/or screenshots
My adguard dns is running in hassos as an addon, however I tried installing it on a server just to rule out that was not the root cause, and it still looks up tls requests via ipv4.