IPv6 failure with DNS filtering enabled

[Chinaski1]

Steps to reproduce

1. Open AdGuard and configure DNS function
2. Choose one of the servers
3. Traffic will only go through IPv4 regardless of the server selected

Customer ID

AdGuard Forum

Your environment

• AdGuard version: 7.5 RC1

[Chinaski1]

The test results were sent to NCloud

[2civics]

Is there an ETA on when this will be fixed? I really want to use the DNS function of Adguard for Windows. But all testing I have done shows complete breakage of IPV6. I thought it was fixed because I enabled it and it worked fine. But then I rebooted and it's back to not working. So I had to disable it.

Adguard Version: 7.5 nightly 25

[techIndia-hacker]

I have this issue of unable to resolve ipv6 only domain names into addresses when dns is managed by adguard for windows. In adguard Android no such problem can be observed. Selecting any of the dns servers in the list does not resolve ipv6 addresses. According to adguard filtering logs, the application isn't even querying AAAA requests. ipv6 domains are queried as type A.

Adguard for windows version - 7.5.2
Windows 10 v2004

This bug was already reported in beta stage but it's still there in stable releases which is unfortuantely disturbing as ipv6 sites are all not working.

Switching off adguard dns solves the problem though but no domain filtering then.

[techIndia-hacker]

@ameshkov request you to look into this

[ameshkov]

@Chinaski1 have you assigned it to v7.6 already? It sounds as if this issue is quite easy to reproduce.

[Chinaski1]

Yes, the issue is reproduced on our side.