-
Notifications
You must be signed in to change notification settings - Fork 236
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cache for custom upstream configurations #169
Comments
It'd be better if you provided an example, so far I see no issues with the cache. Here's how to check it:
|
I just discovered that the issue is only happening with clients that I configured in the Client Settings. I only did so to identify the device at NextDNS, so I needed to add the custom DNS server, plus it cleans up the labeling in the query log, but for some reason the caching doesn't work on configured clients. I unconfigured one client and caching works again, but I'd much rather use it. I can't see this being an intentional feature. |
Hmm, this may indeed be a bug. Have you configured a custom upstream for these clients? |
I do have a custom upstream, but it's the same one but just a different identifier in it for each of my clients, but as it was just pointed out, it happens regardless of whether a custom upstream is used or not. |
@ameshkov, we actually have a piece of logic that restricts caching custom upstream results: Line 481 in 0f48436
This is the result of fixing AdguardTeam/AdGuardHome#1301. Should we leave it as is or implement per-client caching? |
@EugeneOne1 needs to be extracted to a new issue in DNS proxy. Indeed, we cannot simply use the global cache here, we should come up with a solution though. |
Thanks. What is the reason that custom upstream clients can't use the global cache? Is that a permanent situation? What is the limitation with that? |
Usually, custom upstreams do additional filtering. For instance, if a client is a Kids device, people may choose to use an upstream that blocks adult websites. Using a global cache would be inconsistent in this case. |
Okay, I see. What about for one of the options in the client settings to choose whether or not that client uses the global cache? |
At the moment I run blocky in the middle between AGH & DOH/DoT upstreams for the sole purpose of caching, and would like to get rid of it when dnsproxy/AGH get caching support for custom up streams. Also, blocky supports custom upstream on per client basis. Not sure how they implement caching for this as I use it with just default upstream. https://0xerr0r.github.io/blocky/configuration/#upstream-configuration Source code for blocky https://github.com/0xERR0R/blocky |
I'm confused after reading the other linked threads. Was this actually resolved or not? |
@Iceman248, I have fixed this on the side of the dnsproxy. If you want to test this client's cache urgently with AdGuard Home, please have a look on the latest edge build version |
Issue Details
v0.107.0-b.11, issue started on v0.106.3, still issue after upgrading to beta
Docker using Unraid Community Apps
DNS assigned via DHCP from router, AGH goes straight to NextDNS as upstream
Expected Behavior
many queries showing fractional ms times
Actual Behavior
Typical ping times for everything, nothing being cached, NextDNS showing many times over more queries as a result
Additional Information
Starting happened in the last 24 hours
The text was updated successfully, but these errors were encountered: