Replies: 2 comments 1 reply
-
Note that setting If you say 'it doesn't work', please show exactly what you tried, what you expected and what you saw, including diagnostic commands used and their output. Also checks logs. But to take one step back: what problem are you trying to solve? |
Beta Was this translation helpful? Give feedback.
-
Do note that some caching resolvers (also stub resolvers in clients) only regard a TTL as a hint. Relying on short lived DNS records is tricky at best. PowerDNS Recursor does respect TTLs, entries will be not be used if they have expired (unless server stale is enabled and the auth does not respond). Short TTLs do increase the load on the recursor and authoritative servers, so use with care. |
Beta Was this translation helpful? Give feedback.
-
Hi,
We're using PowerDNS Recursor 5.2.0 and we are trying to disable cache for certain request patterns. For example : when a client requests "blablabla.com", the recursor should not cache the answer.
So far we tried:
The preresolve() function and "dq.variable = true", but it doesn't seem to work as we can't resolve our records anymore.
The postresolve() function, like this (with and without the dq.variable // with a ttl set at 1 second):
But it doesn't work either, the answer is still cached.
Any (simple) idea?
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions