-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Total speed check failure shouldn't be cached #1737
Comments
Old results will be cached until the ttl set by the domain owner has expired; empty results will be cached; no results will not be cached. Maybe I don't understand. I hope you can give me an example. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am setting up a VPN (for IPv6) and noticed that resolution fails for domain X when none of the IP(v6)s is reachable. This alone does not make any practical difference, but when the IPs becomes pingable, the old result is still cached so the domain fails to resolve while it should. IMHO this is not a desired behavior.
I am on SmartDNS 45 and I apologize in advance if I missed the configuration option for this.
The text was updated successfully, but these errors were encountered: