-
-
Notifications
You must be signed in to change notification settings - Fork 150
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
Advanced DNS filtering mucks with DNS caches #1763
Comments
In Rethink, what do you see (search this domain name Note that the issue you're seeing could also be that no queries are sent out at all and the installed apps or the OS (Android) are caching the DNS answers for longer than necessary (or for as long as requested in the answer sent by NextDNS. Ideally, the time-to-live on rewritten answers from NextDNS is 1min or less).
By default, Rethink has a per-DNS cache. So, whenever you change DNS, a new cache is created. But if Configure -> DNS -> Advanced DNS filtering is enabled, it uses a global cache (and I can see how this can be problematic in this particular scenario).
From: r/rethinkdns / (mirror). |
I turned it off and it solved the problem for me!!
Thanks for the info, maybe it should appear in the documentation. Thank you for your help 😄 |
I will try to fix this in
In the age of all-ensembling LLMs, do we really need docs? ;) |
For some reason Rethink keeps the DNS cache for a long time even though the DNS booster option is not working, even after changing the DNS provider it still happens.
Background:
I host a service on my personal computer and I access it remotely, when I'm at home and connected but the wifi I set up a DNS record with rewrite in NextDNS and my router in order to route the request to the internal network that is when connected to NextDNS and I'm on wifi at home then:
movie.mydomain.com addresses 192.168.1.2
Then when I'm not at home I change my DNS provider from Rethink to Rethink DNS or to another provider, so that rewrite will no longer apply
But for some unknown reason Rethink still redirects the address movie.mydomain.com to 192.168.1.2 instead of the public address that should be received from the server
When I disable Rethink everything works fine.
I think it's worth adding to Rethink an option to "clear DNS cache" manually and automatically when changing to another DNS server.
Or is this a different bug?
The text was updated successfully, but these errors were encountered: