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
Comments
Quick update: cache will be cleared if you disable and then enable protection. |
This may be implemented alongside #1685 |
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. |
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! |
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 |
Ok, Then to re-enable caching, can we just change the cache size, or do we need to also toggle protection? |
@meichthys, As a temporary solution to reset the cache, I'm restarting the service |
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
The text was updated successfully, but these errors were encountered: