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

Document reasons for use (eg, vs dnsmasq) #9

Closed
pikeas opened this issue Jul 15, 2015 · 3 comments
Closed

Document reasons for use (eg, vs dnsmasq) #9

pikeas opened this issue Jul 15, 2015 · 3 comments

Comments

@pikeas
Copy link

pikeas commented Jul 15, 2015

@progrium suggested using resolvable as an alternative to dnsmasq at gliderlabs/docker-alpine#8.

What prompted the creation of resolvable? Are there any downsides to using resolvable instead of dnsmasq?

@progrium
Copy link
Contributor

Well resolvable was originally based on dnsmasq but we ran into some quirks that worked against our goals. I mean, if you just read the docs (though I get that they aren't great now), they should show the benefits of resolvable vs dnsmasq ...

@pikeas
Copy link
Author

pikeas commented Jul 15, 2015

Explicit is better than implicit. Resolvable is obviously much simpler and easier to use, but the docs should address this directly, and call out catches (stability, performance) if any.

@progrium
Copy link
Contributor

Docs have a long way to go, I agree. But I'm going to close this out because it's already on our radar and I don't really think we need to track it.

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