-
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
Post remaining bounties on some issue? #130
Comments
+1 pfsense #51 |
oh yeah, another vote for pfsense #51 |
I think for this to be successful, inclusion in mass produced hardware will be very helpful. Is it hard to make a pfsense package? |
Ignorant question: does dnschain work in FreeBSD? Update. I can confirm that I can run
The bigger problem is running namecoin. With it is said that |
You can use DNSChain as a traditional DNS server, but I personally don't recommend it (yet). I think PowerDNS' recursor has been tuned to do that job efficiently and well. More work needs to be done on native-dns for it to be at parity with PowerDNS. The two work great together though. |
As far as Namecoin on FreeBSD goes, you can always try compiling namecoind from source. |
After some considered thought, it's become clear to me that Issue #101 — Switch to getdns-node instead of native-dns is of highest priority, so the $120 bounty is going on that, and I strongly encourage other users of DNSChain to donate bounties to that issue as well. Reason being: native-dns is not a very good DNS library, and 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. |
We've got $120 left in BountySource that we can put on something.
I'm thinking maybe one of:
admin
branch tho)cc @SGrondin @wemeetagain
Anyone else feel free to chime in!
The text was updated successfully, but these errors were encountered: