-
Notifications
You must be signed in to change notification settings - Fork 170
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
Drop native-dns and switch to latest .setServers NodeJS API [$120] #101
Comments
We've placed a $120 bounty on this issue (the entirety of the remaining $ we had set aside for DNSChain). If you'd like to help DNSChain there are two things you can do:
|
Changed title of the issue and edited OP requirements to add:
@wemeetagain Since you started a bit of work on this that we can't use let me buy you dinner next time in SF? (Might be this Sunday! ^_^) |
Oops, been away from this codebase for too long. Just realized that So since it seems the Node API for get-dns is insufficient, and the built-in API is insufficient, the only game in town is still native-dns, which needs a new maintainer. So for now closing this issue. |
EDIT March 24, 2016: Since it seems getdns is not suitable for our purposes, but Node.js now finally has a simple way to set the DNS servers via
.setServers
, use that instead ofnative-dns
.Apologies for misunderstanding that the Node bindings for getdns were lacking for our purposes!
Ignore everything below
https://github.com/getdnsapi/getdns-nodeWhilenative-dns
works OK, it seems to be somewhat abandoned right now. I do not have the time to work on improving it. With a switch to getdns, DNSChain should work great as a standalone DNS server for traditional DNS and we wouldn't need to recommend PowerDNS alongside it.For this task:Add an additionaloldDNS
method for getdns and make it the default that DNSChain uses.Update all related code as necessary.The text was updated successfully, but these errors were encountered: