Skip to content
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

Feature Request: Force clear cache #1905

Closed
hoshsadiq opened this issue Jul 22, 2020 · 10 comments
Closed

Feature Request: Force clear cache #1905

hoshsadiq opened this issue Jul 22, 2020 · 10 comments
Labels
duplicate Duplicate or merged issues.

Comments

@hoshsadiq
Copy link

Problem Description

I had created a new domain, with new DNS entries, however, because I did a dig request locally to just before the DNS had propagated, it refused to return valid values despite the DNS records TTL having expired. I found out that this was because AdGuardHome has a local DNS cache, however, this meant that my DNS refused to resolve. I couldn't find any documentation on this either besides the config values, so I ended up taking a stab in the dark and restarted AdGuard Home as I'd figured the cache must be in memory.

Proposed Solution

  • First, the documentation should be updated to mention that there is local caching happening, and how it can be cleared.
  • In addition to the that, a nice to have solution is an option somewhere in the UI to clear the cache.
@ameshkov
Copy link
Member

Quick update: cache will be cleared if you disable and then enable protection.

@ameshkov
Copy link
Member

This may be implemented alongside #1685

@ameshkov ameshkov added this to the v0.107 milestone Jul 23, 2020
@hoshsadiq
Copy link
Author

Quick update: cache will be cleared if you disable and then enable protection.

Odd, I did try that, but the record still wouldn't resolve. If it happens again, I'll definitely double check and perhaps raise a bug issue.

@Aikatsui
Copy link
Contributor

#1145

@linus-ha
Copy link

linus-ha commented Jan 2, 2022

I have to clear my DNS cache on a regular basis, and it cannot be the official solution to set the cache size to zero, wait a bit and re-enable the cache afterwards. A button would be really helpful here!

@meichthys
Copy link

Quick update: cache will be cleared if you disable and then enable protection.

This does not seem to work for me. Queries continue to be served from cache. Do we also need to set the cache size to 0 before re-enabling protection?

@SiNONiMiTY
Copy link

Quick update: cache will be cleared if you disable and then enable protection.

This does not seem to work for me. Queries continue to be served from cache. Do we also need to set the cache size to 0 before re-enabling protection?

yes, set the cache size to 0

@meichthys
Copy link

Ok, Then to re-enable caching, can we just change the cache size, or do we need to also toggle protection?

@Eyeborgs
Copy link

Eyeborgs commented Feb 28, 2022

This does not seem to work for me. Queries continue to be served from cache.

@meichthys, As a temporary solution to reset the cache, I'm restarting the service

@ammnt
Copy link

ammnt commented Feb 2, 2023

@ainar-g, FYI. It looks done already in: #5190

@ainar-g ainar-g added duplicate Duplicate or merged issues. and removed feature request P3: Medium labels Feb 2, 2023
@ainar-g ainar-g removed this from the v0.108.0 milestone Feb 2, 2023
@ainar-g ainar-g closed this as not planned Won't fix, can't repro, duplicate, stale Feb 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Duplicate or merged issues.
Projects
None yet
Development

No branches or pull requests

10 participants