DNS_PROBE_FINISHED_NXDOMAIN at every first access

[ameshkov]

@pdario commented on Fri Aug 19 2022

I always used AdGuard on Windows and set it to use AdGuard DNS; the problem is still present now that I linked the PC to AdGuarda DNS 2.0 (https://adguard-dns.io/en/dashboard/).

When I access some URL in Chrome, say the first time in a day, I get DNS_PROBE_FINISHED_NXDOMAIN error; if I refresh the page, it loads, but it may lack some content got from external URLs; a new refresh fixes. This is very annoying. Moreover, many sw that does not "refresh", does not start or run because their first connection attempt fails.

Please fix this ASAP!

Thank you

[ameshkov]

I am not sure what could be causing this, though. The only idea is that maybe after waking up from hibernation it tries to use the old connection and fails?

To troubleshoot this issue, we need to get additional logs.

Here's what we need you to do:

1. Click on the AdGuard's tray icon -> Advanced -> Logging level -> set it to "Debug".
2. Reproduce the issue (this is extremely important).
3. Set the logging level back to "Default".
4. Remember the exact time when the issue was reproduced, we will need it to find the corresponding records in the log file.
5. Click on the AdGuard's tray icon -> advanced -> "Export logs and system info"
6. Send the log file to us either in telegram or to [email protected]
7. Mention the time when the issue was reproduced and the website address.

[pdario]

Today the problem didn't occur; as soon as it starts again, I'll collect the log files.

[pdario]

Hello, I just sent the log files to the email address you told me.

[ameshkov]

According to the log the DNS request happened in the middle of protection re-init triggered by updated filters.

[pdario]

I don't understand how this helps; the problem occurred all day long and continues today.

For example, I got the error accessing github.com now; refreshing che page, it loaded, but it didn't load resources that I suppose are on differente domain names and appeared as in the screenshot.

After second refresh, the page was ok.

Even the image upload first failed and then went ok.

[ameshkov]

It's just an explanation of why is that happening, now we should find a way to fix that :)

[pdario]

Ah, ok! I thought you meant it was just a transient glitch. I hope you'll find a solution soon! :-)

[adbuker]

@pdario ,

1. please select "disable filter update" option in "General settings" pane, it can at least decrease amount of issues you face. And if this helps, please inform about it
2. have you faced the issue before 7.10.2 or problems start only with such version?

[pdario]

Ok, I disabled it: I hope to be able to use it soon again. I would say it "fixed" the problem.

I can't say about your second question... When has it been released? It is months I have the problem on one of my PC and it started when I enabled DNS filtering on a second PC a few weeks ago.

[adbuker]

Ok, I disabled it: I hope to be able to use it soon again. I would say it "fixed" the problem.

yes, it's not a fix (in general meaning), but a very temporarily solution, in particular needed to make your using more comfortable.

about 2nd question - ok, thanks

[pdario]

Unfortunately the problem still occurs, maybe less frequently

[ameshkov]

@pdario could you please record the logs again with this configuration?

[pdario]

I'm trying but it's not very frequent... I'll keep debug level enabled

[pdario]

I don't know, it seems to have stopped now; I'll cycled the update frequency settings to see what happens; I'll report here.

[adbuker]

Unfortunately the problem still occurs, maybe less frequently

And finally please test this build. It's totally test version (all the options you will switch not applied), but it's can lay light on the causes. After the test you made, please install regular build from the our site

[pdario]

Now it's working fine even with update frequency set to default; are you sure it is a client issue? Couldn't it depend on some server loads or something else server side?

[pdario]

I made it! I tried ftp.com @12.05 and got the error with filter update disabled. I'm preparing the logs to be sent

[adbuker]

Now it's working fine even with update frequency set to default; are you sure it is a client issue? Couldn't it depend on some server loads or something else server side?

Did you try with the build from the post above or regular one?

[pdario]

Regular: I do not have time, now, to uninstall, install, reinstall... I hope this helps

[adbuker]

Regular: I do not have time, now, to uninstall, install, reinstall... I hope this helps

So, according to your message above, that you've set update frequency to default, in the end your app's configuration is similar to one just before the issue occurred? Nevertheless the issue went away, right?

[pdario]

No, the last log files have been taken with filter update set to "disabled" and I got the errore accessing ftp.com @12.05

[adbuker]

@pdario , I guess, I fixed the problem - could you please try the build

[pdario]

Can I simply install that over the current version?

[adbuker]

@pdario , yes, of course

[pdario]

@adbuker I just installed your version and enabled filter update; I'll see how it works

[ameshkov]

Any update? Is this build better?

[pdario]

This is my first full day with the patched version: so far so good! :-)

[pdario]

@ameshkov @adbuker yesterday went without problems, but:

• today it started again at the first connection after boot; it seems stable, now
• (minor) the main interface window appears after login: this wasn't like that with the official version

[pdario]

It seems consistent: each first access today fails; after first access, all successive requests to the same name seem successful.

[adbuker]

each first access today fails; after first access

so, in other words, the issue still exists, right? could you please send the debug logs again

(minor) the main interface window appears after login

thanks, we got the issue and will fix it soon