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

Alternative to dnsmasq? #158

Closed
cjcullen opened this issue Oct 10, 2017 · 5 comments
Closed

Alternative to dnsmasq? #158

cjcullen opened this issue Oct 10, 2017 · 5 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@cjcullen
Copy link
Member

Should we replace dnsmasq w/ something memory safe?

Following up on the CVE-2017-14491 discussion, we should think about what it would take to replace dnsmasq.

@MrHohn
Copy link
Member

MrHohn commented Oct 10, 2017

Ref the coredns proposal kubernetes/community#1100.

@bowei
Copy link
Member

bowei commented Oct 10, 2017

CoreDNS seems to be a leading contender. Although there are always going to be bugs...

@valentin2105
Copy link

DNSDIST ?

https://dnsdist.org/

@bowei
Copy link
Member

bowei commented Nov 2, 2017

sig-network has a proposal to replace everything with coredns, a golang-based resolver.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/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 Jan 31, 2018
@thockin thockin closed this as completed Jan 31, 2018
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

7 participants