AdGuard VPN Leaks DNS Server Requests Like a Sieve

[CinnDebianBestDebian]

Please answer the following questions for yourself before submitting an issue.

• I checked the knowledge base and found no answer
• I checked to make sure that this issue has not already been filed

AdGuard VPN version

Current version: 2.6.2 (1782)

Environment

- OS: Windows 10 (x64) [LATEST]
- Other network-level software: AdGuard Ad Blocker, Bitdefender Total Security

Which DNS server do you use?

AdGuard DNS Non-filtering

Custom DNS

No response

Use Wintun

• yes, I do

Issue Details

Steps to reproduce:

1. Connect to VPN
2. Visit a Test website such as https://www.dnsleaktest.com/ or https://ipleak.net
3. See the leaks with your own eyes.

Expected Behavior

A good VPN protects the user from DNS leaks.

Actual Behavior

DNS queries leak like a sieve.

Screenshots

Screenshot 1

Screenshot 1

Additional Information

No response

[StanleyLynn]

@CinnDebianBestDebian Greeting!
Could you try installing our latest nightly build and tell us if the issue still persists?

[CinnDebianBestDebian]

@CinnDebianBestDebian Greeting! Could you try installing our latest nightly build and tell us if the issue still persists?

The issue still persists:

Screenshots

Screenshot 1

Screenshot 2

[StanleyLynn]

@CinnDebianBestDebian Please try installing the latest AdGuard VPN 2.7 (released yesterday). If the issue persists, collect and send us your application logs so we can investigate the cause.

Here's what we need you to do:

1. Go to Settings -> App settings -> Advanced settings -> Logging level -> Extended.
2. Reproduce the problem, then remember the exact time it happened.
3. Open Settings -> App settings -> Advanced settings -> Export logs and system info.
4. Send the archive to qa@adguard.com:
   • include [windows] keyword and 938 in the subject of your email
   • specify the exact time when the issue occurred

[kakadoo4]

Same thing... Multiple computers and they all leak dns while adguard vpn is active. I tried fresh windows install and still leaking. Clearly something is wrong with adguard vpn itself. I had to go back to a competing VPN solution — I hope you'll fix this issue.

[StanleyLynn]

@kakadoo4 Could you please send the logs following my instructions from the previous message? It will help us see what's going on and fix it

[CinnDebianBestDebian]

Same thing... Multiple computers and they all leak dns while adguard vpn is active. I tried fresh windows install and still leaking. Clearly something is wrong with adguard vpn itself. I had to go back to a competing VPN solution — I hope you'll fix this issue.

If you have a fancy enough WiFi router, a workaround I found for this issue is to simply set both your IPv4 and IPv6 DNS servers as AdGuard DNS servers inside the router software itself. The only downside is that you can't choose what type of DNS servers you want (e.g. Non-filter, Family Friendly, etc.). However, it does stop the leaks completely.

[CinnDebianBestDebian]

@CinnDebianBestDebian Please try installing the latest AdGuard VPN 2.7 (released yesterday). If the issue persists, collect and send us your application logs so we can investigate the cause.

Here's what we need you to do:

1. Go to Settings -> App settings -> Advanced settings -> Logging level -> Extended.

2. Reproduce the problem, then remember the exact time it happened.

3. Open Settings -> App settings -> Advanced settings -> Export logs and system info.

4. Send the archive to qa@adguard.com:

   • include [windows] keyword and 938 in the subject of your email
   • specify the exact time when the issue occurred

Please bear with me, the graphics card for my main desktop computer just died. I'm currently working on getting my backup laptop up and running, and will continue this bug report once that's complete.

[StanleyLynn]

@CinnDebianBestDebian Alright! Please send us the logs when you have a chance. We'll keep this issue open for 5 days awaiting your response. If we don't hear back by then, we'll temporarily close it — but don't worry, you can always reopen it later if the issue persists and you're able to send the logs.

[CinnDebianBestDebian]

@CinnDebianBestDebian Alright! Please send us the logs when you have a chance. We'll keep this issue open for 5 days awaiting your response. If we don't hear back by then, we'll temporarily close it — but don't worry, you can always reopen it later if the issue persists and you're able to send the logs.

Cool. I should have everything set up by Sunday anyways.

[CinnDebianBestDebian]

@CinnDebianBestDebian Alright! Please send us the logs when you have a chance. We'll keep this issue open for 5 days awaiting your response. If we don't hear back by then, we'll temporarily close it — but don't worry, you can always reopen it later if the issue persists and you're able to send the logs.

Got my lappy up and running. I successfully performed a test where a DNS leak occurred. I've send the logs to the qa email as requested. Hope this helps.