-
Notifications
You must be signed in to change notification settings - Fork 427
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
Support the DNSCrypt protocol #4
Comments
I'm definitely planning on supporting DNSSEC, I can probably do this too. |
Awesome. The use case is a bit orthogonal to DNSSEC (confidentiality and integrity within an "intranet"-style deployment between clients and a DNS server), but I would certainly consider it a welcome addition given your present roadmap. |
Yeah, sorry, I get that it serves a different purpose, but it lines up with the set of features I want in the platform. I only get to work on this in my spare time at the moment, so it might be a while before I get all that in here. |
FYI, in issue #38 there is a suggesting of first supporting https://tools.ietf.org/html/rfc7858. Would people want to weigh in on that? I'll probably only end up really supporting one for a while (as either will fit my needs). |
btw, the dnscrypt branch has some initial certificate code. so this is maybe 25% done at this point. |
minimal local network with working resolution
It would be nice if this server supported the DNSCrypt protocol:
https://dnscrypt.org/
cc @jedisct1
The text was updated successfully, but these errors were encountered: