Maximum cache duration? #48
Labels
Milestone
Comments
|
No, there is no option for max duration yet. |
|
Thanks for confirming! My use case is that I want a cache with a fairly short cache duration in order to cache lookups that are very frequently performed, without wasting space in the cache for lookups that are not performed as frequently. |
MichaCo
added a commit
that referenced
this issue
Mar 1, 2020
… long any records should be cached. see #48 * Fixing a bug with non-empty OPT records, see #55. * Changing the logic which removed the EDNS opt record from the results. The record will now be in the additonal records and can have data (the raw bytes). * Added version compatibility testing to make sure I'm not breaking stuff. Optional parameters are not fun sometimes ~~
MichaCo
added a commit
that referenced
this issue
Mar 2, 2020
* some minor things * + Removing the disable server logic which was a bit wanky. + Removing cache by server. In DNS all servers should have the same answer for a question, no need to cache per server! + (work in progress) keep API stable (from 1.1.0 on), adding unit tests + (work in progress) query options & tests * * Added max cache timeout which can be used to set an upper limit how long any records should be cached. see #48 * Fixing a bug with non-empty OPT records, see #55. * Changing the logic which removed the EDNS opt record from the results. The record will now be in the additonal records and can have data (the raw bytes). * Added version compatibility testing to make sure I'm not breaking stuff. Optional parameters are not fun sometimes ~~ * Update azure-pipelines-ci.yml for Azure Pipelines * Update azure-pipelines-ci.yml for Azure Pipelines * cleanup * Update azure-pipelines-ci.yml for Azure Pipelines * Update azure-pipelines-ci.yml for Azure Pipelines * Update azure-pipelines-ci.yml for Azure Pipelines * trying to fix build part 10 * another build update * Readme update * Update azure-pipelines-ci.yml pack build config * trying to change nuget versioning * Update azure-pipelines-ci.yml for Azure Pipelines * Update azure-pipelines-ci.yml for Azure Pipelines * Test build pack * Test build pack - version suffix somehow teleports from one task to another? * Test build pack - version suffix somehow teleports from one task to another? * Test build pack - version suffix somehow teleports from one task to another? * Test build pack - version suffix somehow teleports from one task to another? * Test build pack - version suffix somehow teleports from one task to another? 2nd pack still doesn't work, just ignores anything passed into arguments it seems? * Test build pack - version suffix somehow teleports from one task to another? 2nd pack still doesn't work, just ignores anything passed into arguments it seems? * Test build pack - version suffix somehow teleports from one task to another? 2nd pack still doesn't work, just ignores anything passed into arguments it seems? * new pack script * new pack script - publish seems to finally work, testing publish now * changing to new icon tag * Update azure-pipelines-ci.yml for Azure Pipelines * testing multiple jobs * build configuration not working * build configuration.. * multi build * multi build * multi build targeting * disabling testing on linux for now * add master branch as trigger [skip ci]
|
Hi @Daniel15, I added that feature with the latest PR, you can find the setting / code here |
|
Thanks! I'll take a look when I get some free time :) |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
I see that there is a
MinimumCacheTimeoutoption. Is there some way to have a corresponding maximum cache timeout? I want to just cache responses for a short period of time, rather than for their entire TTL.The text was updated successfully, but these errors were encountered: