SaaSHub helps you find the best software and product alternatives Learn more →
Hickory-dns Alternatives
Similar projects and alternatives to hickory-dns
-
-
InfluxDB
InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.
-
-
-
rustdesk
An open-source remote desktop application designed for self-hosting, as an alternative to TeamViewer.
-
-
-
openobserve
🚀 10x easier, 🚀 140x lower storage cost, 🚀 high performance, 🚀 petabyte scale - Elasticsearch/Splunk/Datadog alternative for 🚀 (logs, metrics, traces, RUM, Error tracking, Session replay).
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
comprehensive-rust
This is the Rust course used by the Android team at Google. It provides you the material to quickly teach Rust.
-
-
-
burn
Burn is a next generation Deep Learning Framework that doesn't compromise on flexibility, efficiency and portability.
-
-
aardvark-dns
Authoritative dns server for A/AAAA container records. Forwards other request to host's /etc/resolv.conf
-
-
-
-
-
rust-by-practice
Learning Rust By Practice, narrowing the gap between beginner and skilled-dev through challenging examples, exercises and projects.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
hickory-dns discussion
hickory-dns reviews and mentions
-
DNS Piracy Blocking Orders: Google, Cloudflare, and OpenDNS Respond Differently
google.com DOMContentLoaded: ~160ms, page loaded: ~290ms
So it's quite reasonable to do full recursive resolution, and you'll still benefit from caching after the first time it's loaded. One other idea I had but never looked into it was instead of throwing out entries after TTL expiry to just refresh it and keep it cached, no idea if BIND/Unbound can do that but you can probably build something with https://github.com/hickory-dns/hickory-dns to achieve that.
-
Getting Started with Rust
9. Hickory DNS Hickory is a DNS client, server, and resolver. This project allows you to see how Rust can be used to handle low-level networking tasks.
-
More Memory Safety for Let's Encrypt: Deploying ntpd-rs
I'm the person driving this.
NTP is worth moving to a memory safe language but of course it's not the single most critical thing in our entire stack to make memory safe. I don't think anyone is claiming that. It's simply the first component that got to production status, a good place to start.
NTP is a component worth moving to a memory safe language because it's a widely used critical service on a network boundary. A quick Google for NTP vulnerabilities will show you that there are plenty of memory safety vulnerabilities lurking in C NTP implementations:
https://www.cvedetails.com/vulnerability-list/vendor_id-2153...
Some of these are severe, some aren't. It's only a matter of time though until another severe one pops up.
I don't think any critical service on a network boundary should be written in C/C++, we know too much at this point to think that's a good idea. It will take a while to change that across the board though.
If I had to pick the most important thing in the context of Let's Encrypt to move to a memory safe language it would be DNS. We have been investing heavily in Hickory DNS but it's not ready for production at Let's Encrypt yet (our usage of DNS is a bit more complex than the average use case).
https://github.com/hickory-dns/hickory-dns
Work is proceeding at a rapid pace and I expect Hickory DNS to be deployed at Let's Encrypt in 2025.
- Trust-DNS has rebranded to Hickory DNS
-
A note from our sponsor - SaaSHub
www.saashub.com | 24 Jun 2025
Stats
hickory-dns/hickory-dns is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of hickory-dns is Rust.