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

Is there an option to prefetch for Nodelocal DNS Cache #652

Open
bennypea opened this issue Oct 23, 2024 · 2 comments
Open

Is there an option to prefetch for Nodelocal DNS Cache #652

bennypea opened this issue Oct 23, 2024 · 2 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@bennypea
Copy link

My current settings for cache is

    cache {
        success 9984 30
        denial 9984 5
    }

If I add the prefetch nothing seems to change.

    cache {
        success 9984 30
        denial 9984 5
        prefetch 1 30s 10%
    }

I cant see prefetched requested in the logs either. I have tested using it using serve_stale which works but is not what I am looking for. At the moment I am going off what is in here: https://coredns.io/plugins/cache/. Is there any documentation you can point me to to understand what I can and cant use for Nodelocal DNS Cache?

Has anyone else successfully used prefetch with nodelocaldns?

Thanks.

@firecow
Copy link

firecow commented Nov 6, 2024

I would be very nice with a prefetching function, like unbound has, in node-local-dns, so our applications don't notice cache expirys.
We see an increase (5-10ms) in dns lookup time for the 99 percentile, when a record is expired and node-local-dns has to ask coredns.

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants