starred/hickory-dns

Fork 0

mirror of https://github.com/hickory-dns/hickory-dns.git synced 2026-04-24 18:55:55 +03:00

[GH-ISSUE #4] Support the DNSCrypt protocol #301

New issue

Open

opened 2026-03-15 21:50:46 +03:00 by kerem · 5 comments

kerem commented

2026-03-15 21:50:46 +03:00

Owner

Originally created by @tarcieri on GitHub (Sep 15, 2015).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/4

It would be nice if this server supported the DNSCrypt protocol:

https://dnscrypt.org/

cc @jedisct1

Originally created by @tarcieri on GitHub (Sep 15, 2015). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/4 It would be nice if this server supported the DNSCrypt protocol: https://dnscrypt.org/ cc @jedisct1

kerem added the

labels

2026-03-15 21:50:46 +03:00

kerem commented

2026-03-15 21:50:57 +03:00

Author

Owner

@bluejekyll commented on GitHub (Sep 15, 2015):

I'm definitely planning on supporting DNSSEC, I can probably do this too.

@bluejekyll commented on GitHub (Sep 15, 2015): I'm definitely planning on supporting DNSSEC, I can probably do this too.

kerem commented

2026-03-15 21:51:02 +03:00

Author

Owner

@tarcieri commented on GitHub (Sep 15, 2015):

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.

@tarcieri commented on GitHub (Sep 15, 2015): 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.

kerem commented

2026-03-15 21:51:07 +03:00

Author

Owner

@bluejekyll commented on GitHub (Sep 15, 2015):

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.

@bluejekyll commented on GitHub (Sep 15, 2015): 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.

kerem commented

2026-03-15 21:51:12 +03:00

Author

Owner

@bluejekyll commented on GitHub (Aug 22, 2016):

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).

@bluejekyll commented on GitHub (Aug 22, 2016): 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).

kerem commented

2026-03-15 21:51:17 +03:00

Author

Owner

@bluejekyll commented on GitHub (Aug 22, 2016):

btw, the dnscrypt branch has some initial certificate code. so this is maybe 25% done at this point.

@bluejekyll commented on GitHub (Aug 22, 2016): btw, the dnscrypt branch has some initial certificate code. so this is maybe 25% done at this point.

kerem referenced this issue

2026-03-15 22:28:56 +03:00

[GH-ISSUE #300] change default LookupIpStrategy from Ipv4AndIpv6 to Ipv4thenIpv6? #434

kerem referenced this issue

2026-03-16 02:01:53 +03:00

[PR #301] [MERGED] "change default LookupIpStrategy from Ipv4AndIpv6 to Ipv4thenIpv6" #1355

kerem referenced this issue

2026-03-16 07:43:38 +03:00

[PR #1332] [CLOSED] 6️⃣ Change default LookupIpStrategy back to Ipv4AndIpv6 #2220