DNS unreachable when using AG #1918

atkrv · 2017-09-07T18:07:43Z

DNS becomes unresolvable within 15 seconds of starting Chrome, if AG and Google Home are on.

User runs about 140 tabs on Chrome (yes, yes, he knows) and have never had any troubles with Chrome or AG until he started using his new Google Home - literally 30 seconds after he started using it.

Steps to reproduce

Turn AdGuard and Google Home ON
Open a Chrome with a few tabs

Expected behavior

DNS shouldn't be broken using AdGuard + Google Home + Chrome.

Actual behavior

If he opens Chrome (even a few tabs) when AG and GHome are on, the DNS issue appears without fail. This 'breaks' the DNS for the entire PC (including other apps) until reboot. Logging out doesn't resolve it, nor does the 'ipconfig /flushdns,' etc.
Using Firefox (only 20 tabs) + AG + GHome causes no issues at all.
From a clean boot, if he turns off AG, leave GHome on, and open chrome (140 tabs) and load AG 1 min afterwards.... everything is fine.

Related report

https://forum.adguard.com/index.php?threads/dns-unreachable-when-using-ag-chrome-browser-google-home.24776/

Your environment

NETGEAR R7000 (running DD-WRT) router shows a peak of 1200 connections when Chrome is first loading up. This settles to about 200 after everything has loaded (~ 60 seconds later).

Hardware:

Win 10 Pro - 64 Bit (v 1703)
Chrome Version 60.0.3112.113 (Official Build) (64-bit)
Adguard (Beta) 6.2.390.2018 + 3 extensions

Extensions:

Adguard assistant Beta (v 4.0.11)
Adguard Popup Blocker Beta (v 1.0.21)
Mouseover Popup Image Viewer (v 2017.4.24.1)

Logs

I'll provide the logs on demand

atkrv · 2017-09-07T18:09:39Z

jasonzerozero:

To add, when closing AG, if I allow the background service to keep running (before loading Chrome), Chrome and GHome will work.

BooBerry · 2017-09-08T09:51:07Z

I don't think Google Home is a factor, as I encountered a similar issue 20 minutes ago (DNS probe errors in Chrome) and I don't even use Google Home. Of course, rebooting fixed it. First time in several weeks I encountered the DNS thing but I can't reproduce it again or make it happen.

Sadly, I didn't have debug mode enabled at the time. =\

ameshkov · 2017-09-12T13:51:08Z

What I know for sure about this is that it was not happening with the previous beta. We should analyze the changes between the last two beta versions in order to figure out what's wrong.

voarsh · 2017-09-13T12:06:46Z

I am having something similar!

I am occasionally having my internet not working and found it was related to Adguard.
If I kill the Adguard process my internet works. I also note that Adguard is also using a much higher percentage of CPU usage! From 20/30%!

ameshkov · 2017-09-13T12:07:58Z

@voarsh the latest beta, right?

We've narrowed it down to the specific module, working on resolving the issue.

voarsh · 2017-09-13T12:13:18Z

@ameshkov That's good to hear.

Yes, V6.2.390.2018.

Do you need to know any of my preferences/extensions/settings?

Thanks.

ameshkov · 2017-09-13T12:18:47Z

@voarsh I hope it's enough, we'll post a test build once it's ready

ameshkov · 2017-09-15T10:54:03Z

It seems that we need some help after all.

Could you please check the new build?

Here is a link to the new build installation file:
https://uploads.adguard.com/up04_m03ws.exe

What to do:

Install
Enable "debug" log via tray menu -> advanced -> logging level
Check if the issue is still present
If it does, please create a dump of "AdguardSvc.exe" process. It can be done from the Task manager:
https://uploads.adguard.com/up04_twc8k.png

We'll need the dump and the log files from %programdata%\Adguard\Logs

Please don't attach them to this issue, send it directly to devteam at adguard.com

ameshkov · 2017-09-17T14:57:10Z

One of the users reported that this test build helped.

ameshkov · 2017-09-17T23:55:35Z

One more test build with partly disabled UDP filtering:
https://uploads.adguard.com/up04_65uvi.exe

We've just tested it with @Steve1209 and the issue is gone with it.

It means that we narrowed it down to the changes in UDP filtering (there were some important changes in the latest beta).

ameshkov · 2017-09-18T16:48:49Z

And one more build:
https://uploads.adguard.com/up04_vcac9.exe

Changes:

UDP filtering is back on.
Made sure UDP filtering is single-threaded (was multi-threaded before, could be problematic in theory)

Steve1209 · 2017-09-18T16:53:01Z

*OK just put the new Dev up, seems ok so far*

…

On Mon, Sep 18, 2017 at 12:48 PM, Andrey Meshkov ***@***.***> wrote: And one more build: https://uploads.adguard.com/up04_vcac9.exe Changes: 1. UDP filtering is back on. 2. Made sure UDP filtering is single-threaded (was multi-threaded before, could be problematic in theory) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1918 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANCR-O5ipvzwwRF09V8yOtI-ObNcMOqVks5sjp74gaJpZM4PQMKk> .

-- *Steve*

ameshkov · 2017-09-18T19:32:03Z

And one more again:
https://uploads.adguard.com/up04_ngjok.exe

Completely reverted it to the single-threaded mode.

ameshkov · 2017-09-21T08:26:03Z

Resolved with this build: https://uploads.adguard.com/up04_65uvi.exe

anderdeath · 2017-09-21T09:27:03Z

Unfortunately, it didn't help. I used this latest build but in 5-10 minutes after installing it (on 6.1) I got AdGuard hanging without possibility to use any browser anymore.

JoshuaNCL · 2017-09-21T10:09:40Z

And one more again:
https://uploads.adguard.com/up04_ngjok.exe

Completely reverted it to the single-threaded mode.

I've tried this and unfortunately the issue is still present.

Steps taken to trigger the issue:

Restart computer
Log in and wait for Adguard to initialise
Open Google Chrome

Once Google Chrome has initialised, web connectivity will be unavailable until the Adguard processes are killed.

Additional Information:

The issue appears to manifest around the time Chrome makes HTTP HEAD requests to non-existent domains in order to check for DNS redirection.

Looking at the service logs, (service_21-09-2017-10_51_33-2017-09-21.log) there are stack traces relating to these domain names. (Example below:)

VERBOSE, AdguardSvc, 24, 21.09.2017 10:52:40.285, Cannot resolve host czuhrnsrriz: System.Net.Sockets.SocketException: No such host is known
Source: System
Stack trace:    at System.Net.Dns.GetAddrInfo(String name)
at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
at System.Net.Dns.GetHostAddresses(String hostNameOrAddress)
at Adguard.Commons.Network.DnsUtils.ResolveHost(String hostNameOrAddress)
at Adguard.Commons.Network.DnsUtils.ResolveHostQuietly(String hostNameOrAddress)

The non-existent domains Chrome called out to on this occasion are:

http://czuhrnsrriz/
http://akeujsnsnfkcfc/
http://undyhltf/

Thanks.

ameshkov · 2017-09-21T10:12:36Z

Ok, guys, let me please upload the proper build with a proper name (with version in it).

I am no more sure which one is what:)

ameshkov · 2017-09-21T10:14:59Z

Here you are, version 6.2.400:
https://uploads.adguard.com/up04_ji7em_setup_6.2.400_dev.exe

It's confirmed by 5 testers that this build resolves the issue.

ameshkov · 2017-09-25T19:49:15Z

Guys, we have a problem.

The build .400 has a serious issue -- one of AdGuard's libs is built with debug flag enabled. It writes debug log to the file in AdGuard's program directory -- look for AdguardNetApiLog.txt. It may take dozens of gigabytes easily.

Please use this newer build instead (until the next beta is out):
https://uploads.adguard.com/Setup_6.2.403_beta.exe

Also, I'd advise you to remove AdguardNetApiLog.txt after the update.

Bluscream · 2017-09-26T06:28:28Z

Thats a huge one o.O

FadeMind · 2017-09-26T06:35:26Z

@Bluscream I had 20 GB size of AdguardNetApiLog.txt during using build 400 ☣️ SSD drive like this 💃

voarsh · 2017-09-26T12:19:43Z

No problems with CPU/no internet with 6.2.403 so far...

JoshuaNCL · 2017-09-29T12:37:11Z

Hi, I'm still having issues using 6.2.403. I lose internet connectivity on startup, and I need to kill the Adguard processes, disconnect from the network and reconnect for it to work again.

Logs removed

Thanks!

ameshkov · 2017-09-29T12:55:55Z

@JoshuaNCL I see a couple of outgoing DNS requests, but nothing really serious.

Does it happen on startup only?

JoshuaNCL · 2017-09-29T13:10:53Z

Hi, I haven't not actually been regularly restarting Adguard when this happens, but I've just launched it again and I haven't lost connectivity again.

ameshkov · 2017-09-29T13:41:31Z

Maybe it's a compatibility issue? What AV do you have installed?

ameshkov · 2017-09-29T13:41:58Z

Also, it'd be better to use the latest build:
https://uploads.adguard.com/Setup_6.2.419_beta.exe

JoshuaNCL · 2017-09-29T14:16:17Z

I'm using Windows defender, I can't see anything it it regarding AdGuard but I did only take a quick look. Oh sorry I am actually using 6.2.419 currently.

Steve1209 · 2017-09-29T16:15:42Z

Andrey,

I installed 6.2.419 as well, I haven't been having any problems, don't really expect to have a problem now either.

ameshkov assigned adbuker Sep 12, 2017

ameshkov added bug P1: Critical labels Sep 12, 2017

ameshkov added this to the 6.2 milestone Sep 12, 2017

ameshkov changed the title ~~DNS unreachable when using AG + Chrome browser + Google Home~~ DNS unreachable when using AG Sep 12, 2017

ameshkov mentioned this issue Sep 12, 2017

Adguard 6.2.390 at Windows 10 stops browsing until user kill the process #1901

Closed

ameshkov assigned confessor-adguard and unassigned adbuker Sep 12, 2017

ameshkov closed this as completed Sep 21, 2017

anderdeath mentioned this issue Sep 21, 2017

DNS unreachable when using AG v2 #1932

Closed

vozersky added the beta label Sep 25, 2017

vozersky removed the beta label Sep 26, 2017

ameshkov reopened this Sep 29, 2017

adbuker modified the milestones: 6.2, 6.3 Nov 10, 2017

adbuker closed this as completed Nov 10, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

DNS unreachable when using AG #1918

DNS unreachable when using AG #1918

atkrv commented Sep 7, 2017 •

edited

atkrv commented Sep 7, 2017 •

edited

BooBerry commented Sep 8, 2017 •

edited

ameshkov commented Sep 12, 2017

voarsh commented Sep 13, 2017

ameshkov commented Sep 13, 2017

voarsh commented Sep 13, 2017

ameshkov commented Sep 13, 2017

ameshkov commented Sep 15, 2017

ameshkov commented Sep 17, 2017

ameshkov commented Sep 17, 2017

ameshkov commented Sep 18, 2017

Steve1209 commented Sep 18, 2017 via email

ameshkov commented Sep 18, 2017

ameshkov commented Sep 21, 2017

anderdeath commented Sep 21, 2017

JoshuaNCL commented Sep 21, 2017 •

edited

ameshkov commented Sep 21, 2017

ameshkov commented Sep 21, 2017 •

edited

ameshkov commented Sep 25, 2017 •

edited

Bluscream commented Sep 26, 2017

FadeMind commented Sep 26, 2017

voarsh commented Sep 26, 2017

JoshuaNCL commented Sep 29, 2017 •

edited

ameshkov commented Sep 29, 2017

JoshuaNCL commented Sep 29, 2017

ameshkov commented Sep 29, 2017

ameshkov commented Sep 29, 2017

JoshuaNCL commented Sep 29, 2017

Steve1209 commented Sep 29, 2017

DNS unreachable when using AG #1918

DNS unreachable when using AG #1918

Comments

atkrv commented Sep 7, 2017 • edited

Steps to reproduce

Expected behavior

Actual behavior

Related report

Your environment

Logs

atkrv commented Sep 7, 2017 • edited

BooBerry commented Sep 8, 2017 • edited

ameshkov commented Sep 12, 2017

voarsh commented Sep 13, 2017

ameshkov commented Sep 13, 2017

voarsh commented Sep 13, 2017

ameshkov commented Sep 13, 2017

ameshkov commented Sep 15, 2017

ameshkov commented Sep 17, 2017

ameshkov commented Sep 17, 2017

ameshkov commented Sep 18, 2017

Steve1209 commented Sep 18, 2017 via email

ameshkov commented Sep 18, 2017

ameshkov commented Sep 21, 2017

anderdeath commented Sep 21, 2017

JoshuaNCL commented Sep 21, 2017 • edited

ameshkov commented Sep 21, 2017

ameshkov commented Sep 21, 2017 • edited

ameshkov commented Sep 25, 2017 • edited

Bluscream commented Sep 26, 2017

FadeMind commented Sep 26, 2017

voarsh commented Sep 26, 2017

JoshuaNCL commented Sep 29, 2017 • edited

ameshkov commented Sep 29, 2017

JoshuaNCL commented Sep 29, 2017

ameshkov commented Sep 29, 2017

ameshkov commented Sep 29, 2017

JoshuaNCL commented Sep 29, 2017

Steve1209 commented Sep 29, 2017

atkrv commented Sep 7, 2017 •

edited

atkrv commented Sep 7, 2017 •

edited

BooBerry commented Sep 8, 2017 •

edited

JoshuaNCL commented Sep 21, 2017 •

edited

ameshkov commented Sep 21, 2017 •

edited

ameshkov commented Sep 25, 2017 •

edited

JoshuaNCL commented Sep 29, 2017 •

edited