Skip to content

Force TTL

Hi,

when using cache.maxttl set to e.g. 1h, any records with a longer TTL are "passed" down with that longer TTL (which is the correct and intendet behaviour, I aware of the meaning of cache.maxttl).

For our setup it would be desirable, to lower the TTL artifically to match (in our case the cache.maxttl). Is this achievable somehow?

Or in other words: how about a 'forcettl' option that overwrites the upstream TTL?

Regards, Daniel

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information