Adguard leaking DNS all time

[FadeMind]

Steps to reproduce

1. Install Adguard For Windows
2. Enable DNS and set any DNS Server from list in app.
3. Launch site browserleaks/dns or https://ipleak.net/
4. See results.

Expected behavior

DNS servers from adguard only.

Actual behavior

DNS leaking.

Screenshot:

Customer ID

Your environment

• Chrome 102.0.5005.63
• Windows 11 Pro 22H2 22621.1

[Aydinv13]

Hi there, sorry for a delay.

DNS servers from adguard only.

Judging from your screen you have AhaDNS server enabled.

[FadeMind]

I mean Adguard for Windows app like title say. You misunderstood.

[Aydinv13]

Please explain it more details

[FadeMind]

See carefully screenshot. Browsers DNS leaks site report system and Adguard for Windows DNS servers in one time.

[sav33]

Yep. Adguard is great except for this big problem which has existed for ages. Their support don't respond about it.

The problem exists on desktop and mobile, using paid Adguard app, using with or without Adguard VPN or other VPN's (which don't leak DNS without Adguard running). It usually leaks to Datacamp Limited servers.

It seems like they don't care or can't fix it (probably the former since they don't even respond).

[adbuker]

@FadeMind, @sav33 as for case with DoT and other secure DNS protocols we use system DNS for the bootstrap by default. Nevertheless, you can manually specify address for it with the special advanced setting. Moreover, you can specify fallback addresses manually too. I guess mentioned "leaks" covered with such cases.

If the issue still persist, please update to the latest nightly version, grab and send the "trace" logs (instruction here) to the [email protected] with the issue number in the letter's label. Please specify "timestamp" when the problem occurred

Also today (or in worse case - tomorrow) we've publish a new nightly version with thoroughly updated DNS-module

[FadeMind]

@adbuker latest nightly 7.11 nightly 9 (build 4017, CL 1.10.68) seems work finally OK. Closing.

[FadeMind]

For clear:

• other DNS resolvers need to set custom IPs in advanced settings - this stop leak.

Leak

INFO, AdguardSvc, 8, 01.09.2022 14:58:43.205, DNS forwarder init: Initializing upstreams...
INFO, AdguardSvc, 8, 01.09.2022 14:58:43.205, DNS forwarder init: Initializing upstream quic://<id>.dns.nextdns.io...
INFO, AdguardSvc, 8, 01.09.2022 14:58:43.205, DNS forwarder init: Upstream created successfully
INFO, AdguardSvc, 8, 01.09.2022 14:58:43.205, DNS forwarder init: Initializing fallback upstream 89.228.4.126...
INFO, AdguardSvc, 8, 01.09.2022 14:58:43.205, DNS forwarder init: Fallback upstream created successfully
INFO, AdguardSvc, 8, 01.09.2022 14:58:43.205, DNS forwarder init: Initializing fallback upstream 31.11.173.2...
INFO, AdguardSvc, 8, 01.09.2022 14:58:43.206, DNS forwarder init: Fallback upstream created successfully
INFO, AdguardSvc, 8, 01.09.2022 14:58:43.206, DNS forwarder init: Upstreams initialized
INFO, AdguardSvc, 8, 01.09.2022 14:58:43.206, DNS forwarder init: Initializing the filtering module...

VERBOSE, AdguardSvc, 21, 01.09.2022 14:58:45.126, AGProxyServer: [id=1000012] New filtered connection id=1250
VERBOSE, AdguardSvc, 21, 01.09.2022 14:58:45.127, Cannot find the filtered application for the process C:\Windows\System32\svchost.exe
VERBOSE, AdguardSvc, 21, 01.09.2022 14:58:45.128, AGUdpSocket: [id=1250] sockEventCb(): Error on socket: (what: 0x02) (10054) winsock error 0x00002746
VERBOSE, AdguardSvc, 21, 01.09.2022 14:58:45.128, AGProxySession: [id=1000012] onError(): Error on socket (127.0.0.1:60689): (10054) winsock error 0x00002746
VERBOSE, AdguardSvc, 21, 01.09.2022 14:58:45.128, AGProxySession: [id=1000012] shutDownSession(): Graceful: 0, reason: winsock error 0x00002746
VERBOSE, AdguardSvc, 21, 01.09.2022 14:58:45.128, AGProcessingChain: [id=1000012] shutdown(): ...
VERBOSE, AdguardSvc, 21, 01.09.2022 14:58:45.130, AGProcessingChain: [id=1000012] shutdown(): Done
VERBOSE, AdguardSvc, 21, 01.09.2022 14:58:45.130, AGProxySession: [id=1000012] ~AGProxySession(): ...
VERBOSE, AdguardSvc, 21, 01.09.2022 14:58:45.131, AGUdpMux: [id=1250] ~AGUdpMuxVSocket(): Connection closed: 192.168.0.15:61405 <-> 31.11.173.2:53
VERBOSE, AdguardSvc, 28, 01.09.2022 14:58:45.341, AGUdpMux: [id=1253] sendTo(): New connection: 192.168.0.15:59471 <-> 31.11.173.2:53
VERBOSE, AdguardSvc, 28, 01.09.2022 14:58:45.341, AGNFHandler: [id=1253] AGNFUdpFlow::onMuxNewConnection(): Redirecting UDP connection 192.168.0.15:59471 -> 31.11.173.2:53 to DNS proxy 127.0.0.1:60689, app: C:\Windows\System32\svchost.exe

No Leak anymore after set custom IPs in advanced

INFO, AdguardSvc, 51, 01.09.2022 15:01:48.994, Save advanced setting AdvancedSettingsEntry: {
  "m_AdvancedSettingBool": null,
  "m_AdvancedSettingString": null,
  "m_AdvancedSettingStringMultiLine": [
    "45.90.28.81",
    "45.90.30.81"
  ],
  "m_AdvancedSettingDropBox": null,
  "m_AdvancedSettingKey": "AdvancedSettingsDnsCustomFallbacks",
  "IsEnabled": true
}

VERBOSE, AdguardSvc, 40, 01.09.2022 15:01:51.218, DNS forwarder init: Using application_verifier
INFO, AdguardSvc, 40, 01.09.2022 15:01:51.218, DNS forwarder init: Initializing upstreams...
INFO, AdguardSvc, 40, 01.09.2022 15:01:51.218, DNS forwarder init: Initializing upstream quic://<id>.dns.nextdns.io...
INFO, AdguardSvc, 40, 01.09.2022 15:01:51.218, DNS forwarder init: Upstream created successfully
INFO, AdguardSvc, 40, 01.09.2022 15:01:51.218, DNS forwarder init: Initializing fallback upstream 45.90.28.81...
INFO, AdguardSvc, 40, 01.09.2022 15:01:51.218, DNS forwarder init: Fallback upstream created successfully
INFO, AdguardSvc, 40, 01.09.2022 15:01:51.218, DNS forwarder init: Initializing fallback upstream 45.90.30.81...
INFO, AdguardSvc, 40, 01.09.2022 15:01:51.219, DNS forwarder init: Fallback upstream created successfully
INFO, AdguardSvc, 40, 01.09.2022 15:01:51.219, DNS forwarder init: Upstreams initialized
INFO, AdguardSvc, 40, 01.09.2022 15:01:51.219, DNS forwarder init: Initializing the filtering module...

Now I closing this for good.

@adbuker