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

CacheDB compile #22

Closed
Lammiwinks opened this issue Sep 26, 2022 · 0 comments · Fixed by #23
Closed

CacheDB compile #22

Lammiwinks opened this issue Sep 26, 2022 · 0 comments · Fixed by #23

Comments

@Lammiwinks
Copy link

Hi Crazy-Max. First of all THANK YOU for an amazing image. This is the only docker image I could get working properly :).

QQ: Would you be able to include the cachedb option into a future release?

The Cache DB module must be configured in the module-config: "validator
cachedb iterator" directive and be compiled into the daemon with --en-
able-cachedb. If this module is enabled and configured, the specified
backend database works as a second level cache: When Unbound cannot
find an answer to a query in its built-in in-memory cache, it consults
the specified backend. If it finds a valid answer in the backend, Un-
bound uses it to respond to the query without performing iterative DNS
resolution. If Unbound cannot even find an answer in the backend, it
resolves the query as usual, and stores the answer in the backend.

The main reason for this is it allows you to keep a persistent DB that survives reboots / image updates and means you don’t have to rebuild it all again.

Thanks,

Lammi

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

Successfully merging a pull request may close this issue.

2 participants