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 plugin: authoritative/non-authoritative flag confuses old(er) clients #2887

Closed
m4r10k opened this issue Jun 13, 2019 · 0 comments

Comments

Projects
None yet
2 participants
@m4r10k
Copy link
Contributor

commented Jun 13, 2019

As described in #2588 (comment) and #2588 (comment) the cache plugin is currently confusing old(er) DNS clients or client implementations (Pyhton, Ruby, ...)

This happens because only the first answer from the DNS cache is provided as authoritative, all other ones (until the TTL is running out) are responded with non-authoritative.

@miekg has provided a PR which pins the answers given from the cache to authoritative.

PR: #2885
Kubernetes Issue trackback: kubernetes/kubeadm#1512

@miekg We have testet the PR in an own build on-premises and the old(er) clients can now work with the cached DNS records without any problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.