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

Drop native-dns and switch to latest .setServers NodeJS API [$120] #101

Closed
taoeffect opened this issue Jan 19, 2015 · 3 comments
Closed

Comments

@taoeffect
Copy link
Member

taoeffect commented Jan 19, 2015

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 of native-dns.

Apologies for misunderstanding that the Node bindings for getdns were lacking for our purposes!

Ignore everything below


https://github.com/getdnsapi/getdns-node

While native-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 additional oldDNS method for getdns and make it the default that DNSChain uses.
  • Update all related code as necessary.

--- Did you help close this issue? Go claim the **[$120 bounty](https://www.bountysource.com/issues/7860737-drop-native-dns-and-switch-to-latest-setservers-nodejs-api?utm_campaign=plugin&utm_content=tracker%2F528702&utm_medium=issues&utm_source=github)** on [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F528702&utm_medium=issues&utm_source=github).
@taoeffect taoeffect self-assigned this Jan 19, 2015
@taoeffect taoeffect changed the title Investigate getdns-node Switch off of native-dns to getdns-node Oct 15, 2015
@taoeffect taoeffect changed the title Switch off of native-dns to getdns-node Switch to getdns-node instead of native-dns Oct 15, 2015
@john-light john-light changed the title Switch to getdns-node instead of native-dns Switch to getdns-node instead of native-dns [$120] Oct 15, 2015
@taoeffect taoeffect removed their assignment Oct 15, 2015
@taoeffect
Copy link
Member Author

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:

  1. Contribute additional bounty to this issue.
  2. Work on this issue and claim the bounty for yourself.

@taoeffect taoeffect changed the title Switch to getdns-node instead of native-dns [$120] Drop native-dns and switch to latest .setServers NodeJS API [$120] Mar 24, 2016
@taoeffect
Copy link
Member Author

Changed title of the issue and edited OP requirements to add:

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 of native-dns.

Apologies for misunderstanding that the Node bindings for getdns were lacking for our purposes!

@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! ^_^)

@taoeffect
Copy link
Member Author

Oops, been away from this codebase for too long. Just realized that .setServers is not sufficient for what we need, as we still need a way to create DNS packets for sending them back, not just choosing DNS servers to query.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants