TTL of cached queries is always one query behind #1894
ghost
started this conversation in
Potential issues
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Seemingly cached queries are returned with outdated TTL and only afterwards the TTL is updated for future queries.
Shouldn't the TTL be updated first, before returning?
What I did was making queries with increasing delay between them e.g. 5, 10, 15 seconds.
With delay 10s the TTL is only 5s down. With delay 15s the TTL is only 10s down. Always one query behind.
Adding a 3rd party DNS-cache fixes this, of course.
edit: fixed in #1895
Beta Was this translation helpful? Give feedback.
All reactions