mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2026-03-04 00:01:12 -05:00
When internet drops, Adguard stops serving all DNS requests, including rewrites. #2456
Labels
No labels
P1: Critical
P2: High
P3: Medium
P4: Low
UI
bug
cannot reproduce
compatibility
dependencies
docker
documentation
duplicate
enhancement
enhancement
external libs
feature request
good first issue
help wanted
infrastructure
invalid
localization
needs investigation
performance
potential-duplicate
question
recurrent
research
snap
waiting for data
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AdGuardHome#2456
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @norgan on GitHub (Feb 9, 2021).
Originally assigned to: @ainar-g, @EugeneOne1 on GitHub.
Docker
dns over tls and https for upstream, half a dozen local rewrites
Raspi 4
Raspbian 64bit
Expected Behavior
Like a real DNs server, queries should be delivered from local zones and cached lookups, even when upstream servers are down.
Actual Behavior
All DNS queries fail and clients panic
Screenshots
Screenshot:
Additional Information
@norgan commented on GitHub (Feb 9, 2021):
AdGuard Home v0.104.3
@ainar-g commented on GitHub (Feb 10, 2021):
Hi, and thank you for your report.
@ameshkov, do we have an issue about an “offline mode”? I think we've discussed that before somewhere, but I can't find the related issue.
@ameshkov commented on GitHub (Feb 10, 2021):
@ainar-g we don't, and the problem is caused by the
max_goroutineslimit, and yes, there was a ticket about that already.We could lift the limit or set it to a higher value, this would help.
@tezgno commented on GitHub (Mar 26, 2021):
This is definitely causing issues when there are ISP outages or on power related restarts. Is there any update on this one?
@KF5JWC commented on GitHub (Apr 14, 2021):
Migrated away from Adguard due to this issue :(
@timcappalli commented on GitHub (Apr 14, 2021):
Why is this flagged as feature request? This is a core deficiency.
@ameshkov commented on GitHub (Apr 15, 2021):
The easy solution to this issue is to set
max_goroutinesto 0 inAdGuardHome.yaml.@Aikatsui commented on GitHub (Apr 17, 2021):
https://github.com/AdguardTeam/AdGuardHome/issues/1558
@SanderGit commented on GitHub (Apr 19, 2021):
I think the issue reported in #1777 is also related.
@SubtleShuttle commented on GitHub (Apr 20, 2021):
I'm not sure if this ticket means no local dns look ups work just while upstream dns servers are unavailable or if it means it doesn't work even when they become available again (my issues is the latter). If my internet goes down, I have to reboot my pi or restart the adguard service for it to process DNS requests again. I thought it just happened when I was using DoH upstream servers but now it happens for unencrypted upstream servers as well. max_goroutines set to 0 didn't fix it for me.
@ameshkov commented on GitHub (Apr 20, 2021):
This one is definitely something new, not related to this ticket.
@SubtleShuttle commented on GitHub (Apr 20, 2021):
Thanks. FWIW, I'm using a Raspberry Pi 3b. The only odd thing about my setup is that my ISP uses CGNAT. I don't think it's related as I haven't seen the issue with pihole.
@SanderGit commented on GitHub (Apr 20, 2021):
Sorry for that, because it was my impression as well that this is the case and @KF5JWC seems to refer to the same. I have this both on a RPi and in docker, with my own unbound as root server (which keeps working). After the connection drops and returns, AGH still does not work.
@ameshkov commented on GitHub (Apr 20, 2021):
@rhraziel @SanderGit it would help a lot if you could record verbose-level log of this issue for us.
@KF5JWC commented on GitHub (Apr 20, 2021):
This is an accurate understanding of the issues I ran into.
@tezgno commented on GitHub (Apr 20, 2021):
This is the same issue I have as well. If I go and unplug my modem, for example, I can no longer resolve any DNS entries including those locally served/rewrites.
@SubtleShuttle commented on GitHub (Apr 20, 2021):
I apologize, I hope someone else can provide logs for this. I've already moved off of Adguard for now and my Linux knowledge is a bit limited.
@kvervo commented on GitHub (Apr 22, 2021):
For @rhraziel issue, I came across a similar report in #2058
However, I was not able to reproduce the problem 0.105.2
However, I can confirm a similar behavior when disabling protection, DNS rewrites would also stop working. Which I believe should not be the case.
Overall the scenario I believe should be implemented is the following:
@SubtleShuttle commented on GitHub (Apr 27, 2021):
FYI, I've emailed logs to the devteam email address in regards to this.
@SubtleShuttle commented on GitHub (Apr 29, 2021):
I've done a little more testing on this and I'm narrowing down what causes the issue (at least for me). If I use a DoH DNS provider OR I use the "browsing web security service" or the "parental control service", DNS resolution does not come back after an internet outage. If I'm not using DoH or web security or parental control, everything works fine after the internet outage. I added Adguard's ipv4 DNS servers to the bootstrap list but that didn't seem to resolve it. I'm just avoiding using DoH and the security/parental services for now but it would be nice to enable them if it didn't cause the resolution recovery issue.
@Salvora commented on GitHub (May 1, 2021):
I am suffering from the same problem.
I advertise adguard home ip address for the primary DNS from my router. I have local domains that I use consistently but when the internet connection gets interrupted, the whole network is confused. Rewrites doesn't work.
@gabxav commented on GitHub (May 16, 2021):
Same error on AdGuard Home v0.106.2
@amishv commented on GitHub (Jun 28, 2021):
Same issue is seen on MWAN3 switchover on OpenWRT. When the main WAN goes down AdGuard home stops serving the DNS request till I restart the application. I have tried both OpenWRT version on my router and Docker version on my NAS.
dig @AdGuard_ip google.com takes a long time before failing with "no dns server found" ,
a parallel dig @8.8.4.4 google.com almost instantly returns the IP of google.com.
I am using a workaround to restart the Adguard container from the mwan3.user script when any WAN interface goes down or comes up, but this introduces appreciable delay in the network.
@a1ad commented on GitHub (Jun 28, 2021):
Got the same problem! WAN down > adguard refuses to work until i restart adguard. Tested on Docker, linux native and opnsense. v0.106.3
@ikifar2012 commented on GitHub (Jun 28, 2021):
Yep we have had issues with our ISP as well and I had to make a script to kill-9 the adguard process then start the service because the whole process seems to hang
@ameshkov commented on GitHub (Jul 5, 2021):
Hi all, could you please try the edge channel build?
Probably, this issue is a duplicate of #3217 which seems to be fixed there.
@amishv commented on GitHub (Jul 5, 2021):
@ameshkov , I do not see this issue, yet, in Version: v0.107.0-a.95+e113b276. The build is up for more than 30 hours.
@ikifar2012 commented on GitHub (Jul 6, 2021):
What's the best way to switch my current install to edge?
@ameshkov commented on GitHub (Jul 6, 2021):
Depends on your setup.
If you're using snapcraft or docker, just switch to the "edge" tag.
If you're using a binary, download one from the edge channel, replace the old one and restart AdGuard Home.
Binaries links:
https://github.com/AdguardTeam/AdGuardHome#test-unstable-versions
@ikifar2012 commented on GitHub (Jul 7, 2021):
Just had to find the binary on the releases page, I have been running for two days and my ISP is having issues so our internet has dropped at least 50 times, it seems to be doing fine
@jdeluyck commented on GitHub (Jul 27, 2021):
Deployed today's edge after my ISP was playing ping-pong, seems to work.
@ainar-g commented on GitHub (Dec 9, 2021):
@EugeneOne1, I think that your fix for #1558 might have fixed this one as well. Can you look into it?
@EugeneOne1 commented on GitHub (Dec 9, 2021):
@ainar-g, it seems the issue has been fixed even earlier. @norgan, @a1ad, could you please check if the issue reoccurs in the latest
edge/beta-channel builds?@a1ad commented on GitHub (Dec 9, 2021):
Its working fine here
@ainar-g commented on GitHub (Dec 13, 2021):
We'll close this issue then. If anyone has similar issues with the latest beta and edge releases, please open a new issue. Thanks everyone.
@handcoding commented on GitHub (Mar 5, 2022):
Does anyone know when this fix might be landing on the main trunk?
I stopped using AdGuard Home a few months ago because of this issue, but I’d love to come back if by chance this might be fixed on the main branch soon.
@SubtleShuttle commented on GitHub (Mar 7, 2022):
Its been fixed as of version 107
@handcoding commented on GitHub (Mar 8, 2022):
Good to know—thanks, @rhraziel!
@conradseba commented on GitHub (Jun 30, 2022):
Hi. I'm running v0.108.0-b.9 and this is very much ongoing. It's driving me nuts. I'll also ditch AGH if this is not fixed. I'm sorry but I cannot spend time troubleshooting my setup instead of working. Hope you find a final solution :) Thanks.
@EugeneOne1 commented on GitHub (Jun 30, 2022):
@conradseba, could you please collect a verbose log for us? You may send it to devteam@adguard.com.
@abdalians commented on GitHub (Jul 12, 2022):
After weeks of struggling with this issue I finally decided to search and came across this thread.
Setup:
Problem:
@abdalians commented on GitHub (Jul 12, 2022):
this is very much an active issue, please mark the ticket accordingly.
@s1lviu commented on GitHub (Jul 19, 2022):
I can confirm I have this issue too on the latest AGH version.
@ainar-g commented on GitHub (Jul 22, 2022):
@abdalians, @s1lviu, apologies for the late response. Can you collect the verbose logs as EugeneOne1 suggested above? Also, what kind of upstream are you using? DoH, DoT, or DoQ?
@abdalians commented on GitHub (Jul 22, 2022):
I tried DoT and DoH - both of these reproduced the same problem. I have AdGuard filtering services turned off at the moment. I will try and capture logs over the weekend.
@dinosoup1 commented on GitHub (Aug 3, 2022):
Commenting to maintain visibility on this issue - I have had to stop using AdGuard as my ISP is basically useless and anytime my network goes out, AdGuard ruins everything locally.
@conradseba commented on GitHub (Aug 4, 2022):
I can also confirm that v0.108.0-b.11 does not address this issue either.
On Wed, 3 Aug 2022 at 20:37, dinosoup1 @.***> wrote:
@abdalians commented on GitHub (Aug 4, 2022):
the ticket status still remains closed, can we reopen this or do we need to open a new issue and reference this?
@levz0r commented on GitHub (Apr 15, 2023):
Same issue happens on v0.107.28
@sammyke007 commented on GitHub (May 10, 2023):
Still an issue
@yurividal commented on GitHub (May 23, 2023):
Is there a fix or workarround for this?
My ISP was doing some maintanance yesterday, and i noticed none of my local rewrites were resolving while my LAN was offline.
This makes no sense. Local rewrites with private domains and local IP addresses on the LAN should not need internet access in order to resolve.
@daygr commented on GitHub (May 30, 2023):
I ran into this issue today while dealing with a prolonged ISP outage. I did a bit of testing and realized that if a low volume of DNS requests hit AGH, it worked as intended, so as suggested above, I set
max_goroutines: 0inAdGuardHome.yaml. It seems that higher volumes of failed upstream DNS requests slow AGH to the point where rewrites fail to respond.edit: I left this comment as I believe there could be some optimization here, so that
max_goroutinescan still be set during normal operation. Perhaps an "outage mode", with a timer similar to the temporary disable button, could be added, which makes AGH stop trying to serve upstream DNS so it doesn't get overloaded.@merlink01 commented on GitHub (Jun 29, 2023):
For me this error still exists: Version: v0.107.32
Setting max_goroutines: 0 did not help.
Because my home automation is using local DNS this is really critical.
What could we do?
@Qhilm commented on GitHub (Aug 22, 2023):
In my case, AGH does not even start if internet is down. I'm running it on opnsense. If there's a power outage, it's possible the router reboots while Internet is still not available, in this case, adguard does not even come up, which is quite annoying.
Is that a separate issue?
@RedFoxy commented on GitHub (Nov 29, 2023):
Same here! And it's a really big trouble when internet goes down and you can't resolve local dns, I've ADGuard v0.107.36 in Docker and I've max_goroutines: 0 in AdGuardHome.yaml but nothing goes when I'm offline
@Qhilm commented on GitHub (Nov 29, 2023):
So far I have been using Unbound as upstream DNS on AGH and that solved two problems:
I have not tested this thoroughly to be fair, but everything looked good the last 2 times I had Internet down on the ISP side.
@RedFoxy commented on GitHub (Nov 30, 2023):
So you use ubound with AGH as DNS, do you mean like https://dev.to/cipherops/how-to-use-unbound-with-adguard-home-1o5n or what?
@Qhilm commented on GitHub (Dec 2, 2023):
I mean configure upstream DNS like here: https://github.com/AdguardTeam/AdGuardHome/wiki/Configuration#upstreams
I run unbound on port 5353 on the same machine, and I configured 127.0.0.1:5353 as upstream DNS for AGH simply.
@RedFoxy commented on GitHub (Dec 4, 2023):
and about config?
@yurividal commented on GitHub (Dec 4, 2023):
Just to be clear: running a local unbound instance as an upstream for AGH is a workaround for the issue, but should definitely not be considered a fix.
There is no reason why AGH should be trying to resolve upstream names if it has local rewrites.
@yurividal commented on GitHub (Dec 4, 2023):
@norgan can you please reopen this issue?
@merlink01 commented on GitHub (Dec 5, 2023):
Yes, this is not fixed, after a lot of testing, I do now use Opensense as dns and connect to adguard as the upstream DNS Server.
A bad workaround, but I don't want to get my internal network and IOT systems go down on short internet outage.
I think this should have high priority, because it seems like an kritical issue.
A missing internet connection should never cause an internal dns overwrite to be not delivered correctly.
@Mad-Jam commented on GitHub (Dec 11, 2023):
Please reopen this. I want to use my local server when internet is down.
@mcrapts commented on GitHub (Jan 2, 2024):
The solution/workaround in this comment works:
https://github.com/AdguardTeam/AdGuardHome/issues/4825#issuecomment-1866318615
Basically you're whitelisting your own domains from any blocklist. Your DNS rewrites that match the exclusion will then resolve even without an internet connection.
@GentleHoneyLover commented on GitHub (Nov 21, 2024):
That's definitely a workaround, not a solution :)
@derekpurdy commented on GitHub (Mar 5, 2025):
Seen the same issue tonight on the latest build. Is this still ongoing?
@zhouguiheng commented on GitHub (Mar 23, 2025):
This issue still persists with the latest build. The custom filter workaround above doesn't work for me.
AGH just refuses to resolve my local domains when offline, the home page UI doesn't load correctly either, and I won't be able to update the settings using UI when Internet is down. I put the workaround @@||mydomain.tld^ directly into the yaml file and restart AGH, no luck.
It seems that AGH is overloaded with pending DoH requests and the log is flooded with many timeout requests.
Can we reopen this bug?
EDIT: Changing max_goroutines to 0 (and possibly reducing upstream_timeout) does mitigate the starving issue for me. Better to cache the upstream or network online status, and fail fast instead of timeout every request
@abdalians commented on GitHub (Mar 24, 2025):
I personally gave up on this long time ago and spawned a named container which is my primary dns for local domain and agh is the forwarded to the named. This way I always resolve my local domains and get the filtering. The only thing missing is the per client filteting which I dont care about.
Yahoo Mail – Email Simplified
On Sun., 23 Mar. 2025 at 9:16 p.m., @.***> wrote:
This issue still persists with the latest build. The custom filter workaround above doesn't work for me.
AGH just refuses to resolve my local domains when offline, the home page UI doesn't load correctly either, and I won't be able to update the settings using UI when Internet is down. I put the workaround @@||mydomain.tld^ directly into the yaml file and restart AGH, no luck.
It seems that AGH is overloaded with pending DoH requests and the log is flooded with many timeout requests.
Can we reopen this bug?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>
zhouguiheng left a comment (AdguardTeam/AdGuardHome#2657)
This issue still persists with the latest build. The custom filter workaround above doesn't work for me.
AGH just refuses to resolve my local domains when offline, the home page UI doesn't load correctly either, and I won't be able to update the settings using UI when Internet is down. I put the workaround @@||mydomain.tld^ directly into the yaml file and restart AGH, no luck.
It seems that AGH is overloaded with pending DoH requests and the log is flooded with many timeout requests.
Can we reopen this bug?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>
@bvandevliet commented on GitHub (Mar 24, 2025):
Clever workaround. But I still agree this issue should be re-opened and not given up on. It should not be just accepted by us loyal end users that shit hits the fan when internet drops, just because this bug keeps being ignored by the AGH team. And I would say it's quite a critical bug too. If this will for certain never be fixed, I'd like to know as well plz, because then I'll start looking for alternatives to AGH..
@abdalians commented on GitHub (Mar 24, 2025):
100% agreed this is a critical bug and needs the attention it deserves. AGh imho is still the best at what it does. I compred a few 2 years ago and settled here.
Yahoo Mail – Email Simplified
On Mon., 24 Mar. 2025 at 1:54 a.m., Bob @.***> wrote:
I personally gave up on this long time ago and spawned a named container which is my primary dns for local domain and agh is the forwarded to the named. This way I always resolve my local domains and get the filtering. The only thing missing is the per client filteting which I dont care about.
Yahoo Mail – Email Simplified
On Sun., 23 Mar. 2025 at 9:16 p.m., @.***> wrote:
This issue still persists with the latest build. The custom filter workaround above doesn't work for me.
AGH just refuses to resolve my local domains when offline, the home page UI doesn't load correctly either, and I won't be able to update the settings using UI when Internet is down. I put the workaround @@||mydomain.tld^ directly into the yaml file and restart AGH, no luck.
It seems that AGH is overloaded with pending DoH requests and the log is flooded with many timeout requests.
Can we reopen this bug?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>
zhouguiheng left a comment (AdguardTeam/AdGuardHome#2657)
This issue still persists with the latest build. The custom filter workaround above doesn't work for me.
AGH just refuses to resolve my local domains when offline, the home page UI doesn't load correctly either, and I won't be able to update the settings using UI when Internet is down. I put the workaround @@||mydomain.tld^ directly into the yaml file and restart AGH, no luck.
It seems that AGH is overloaded with pending DoH requests and the log is flooded with many timeout requests.
Can we reopen this bug?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>
Clever workaround. But I still agree this issue should be re-opened and not given up on. It should not be just accepted by us loyal end users that shit hits the fan when internet drops, just because this bug keeps being ignored by the AGH team. And I would say it's quite a critical bug too. If this will for certain never be fixed, I'd also be open again to look for alternatives to AGH. So if that is the case, I'd like to know as well plz..
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>
bvandevliet left a comment (AdguardTeam/AdGuardHome#2657)
I personally gave up on this long time ago and spawned a named container which is my primary dns for local domain and agh is the forwarded to the named. This way I always resolve my local domains and get the filtering. The only thing missing is the per client filteting which I dont care about.
Yahoo Mail – Email Simplified
On Sun., 23 Mar. 2025 at 9:16 p.m., @.***> wrote:
This issue still persists with the latest build. The custom filter workaround above doesn't work for me.
AGH just refuses to resolve my local domains when offline, the home page UI doesn't load correctly either, and I won't be able to update the settings using UI when Internet is down. I put the workaround @@||mydomain.tld^ directly into the yaml file and restart AGH, no luck.
It seems that AGH is overloaded with pending DoH requests and the log is flooded with many timeout requests.
Can we reopen this bug?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>
zhouguiheng left a comment (AdguardTeam/AdGuardHome#2657)
This issue still persists with the latest build. The custom filter workaround above doesn't work for me.
AGH just refuses to resolve my local domains when offline, the home page UI doesn't load correctly either, and I won't be able to update the settings using UI when Internet is down. I put the workaround @@||mydomain.tld^ directly into the yaml file and restart AGH, no luck.
It seems that AGH is overloaded with pending DoH requests and the log is flooded with many timeout requests.
Can we reopen this bug?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>
Clever workaround. But I still agree this issue should be re-opened and not given up on. It should not be just accepted by us loyal end users that shit hits the fan when internet drops, just because this bug keeps being ignored by the AGH team. And I would say it's quite a critical bug too. If this will for certain never be fixed, I'd also be open again to look for alternatives to AGH. So if that is the case, I'd like to know as well plz..
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>
@adripo commented on GitHub (Mar 24, 2025):
I think it's easier to open a new issue and reference this one for the details. I doubt the AGH team checks closed issues.