Skip to content
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

Cache sharding: multiple caches, cache key namespacing, etc #121

Open
ambyjkl opened this issue Jan 10, 2025 · 2 comments
Open

Cache sharding: multiple caches, cache key namespacing, etc #121

ambyjkl opened this issue Jan 10, 2025 · 2 comments

Comments

@ambyjkl
Copy link

ambyjkl commented Jan 10, 2025

I want to have a setup where I can forward to different upstream DNS servers depending on the client making the request. These DNS servers may return different results since they have different content filtering settings. However, since all the requests share the same cache, this is not possible, as the cached response from one server is used for requests made to another server. Is it possible to have distinct caches for each policy.FORWARD, or namespacing the cache keys to make this work? Is there a better approach to achieve what I'm looking for?

@vcunat
Copy link
Member

vcunat commented Jan 10, 2025

I don't think that's currently doable in a reasonable way with Knot Resolver.

@vcunat
Copy link
Member

vcunat commented Jan 10, 2025

You could run (some) requests as .STUB with cache turned off, if I recall right. Though that's slightly hacky, too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants