trust-dns
woodpecker
Our great sponsors
trust-dns | woodpecker | |
---|---|---|
14 | 4 | |
3,254 | 1,967 | |
- | - | |
7.1 | 2.0 | |
6 months ago | about 2 months ago | |
Rust | Rust | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
trust-dns
-
Hickory DNS
If you don't know what is Trust-DNS / Hickory DNS, this seems to be the repo: https://github.com/bluejekyll/trust-dns
-
You might want async in your project
IO is not a part of the async runtime contract (I don't know if this is good or bad), and Tokio & futures famously have different `Async{Read,Write}` traits. I once had to do this [0] to adapt between them.
This means that any crate that uses IO will be bound to a limited number of Runtimes. Everything being Tokio-only is pretty bad (though Tokio itself is great), but here we are...
[0] https://github.com/bluejekyll/trust-dns/pull/1373#issuecomme...
-
Extract cert.pem and privkey.pem from acme.json
I need a cert.pem and privkey.pem for https://github.com/bluejekyll/trust-dns but even using the extractor to get a cert.pem and privkey.pem from the acme.json file it seems invalid.
-
What would you rewrite in Rust?
You might be interested in Trust DNS - "A Rust based DNS client, server, and Resolver, built to be safe and secure from the ground up."
-
Announcing `async-dns`
It looks like you need to reach for a separate crate for that: https://github.com/bluejekyll/trust-dns/blob/7dcb7b983f5407d95d93b800af13caeee975aaa8/crates/async-std-resolver/src/lib.rs
- Trust-Dns - A rust based dns client, server, and resolver
-
What I learned from making a DNS client in Rust
You might be interested in new alternative to dig called dns https://github.com/bluejekyll/trust-dns/blob/main/util/src/dns.rs . I found out about it from https://twitter.com/benj_fry/status/1513269287229657091
- Show HN: A Trust-DNS based dig alternative
-
Docker: Binary compiled with Musl works but not the one compiled with glibc
I've found the Trust-DNS Resolver crate and it does the job! Now the binary seems to not use any dynamic library to look up the ip of a host.
woodpecker
- My impressions of using the Drill performance testing tool
- What are some less popular but well-made crates you'd like others to know about?
-
[Media] Introducing `pdc` a load testing library that can hit 500,000 req/sec
drill
-
[ANN] servant-benchmark v0.1.1.1
I've recently published servant-benchmark, a small library that produces request files from Servant APIs to be used by external benchmarking tools. It currently supports exports for wrk, siege, and drill.
What are some alternatives?
parity-bitcoin - The Parity Bitcoin client
woodpecker - Drill is an HTTP load testing application written in Rust
citybound - A work-in-progress, open-source, multi-player city simulation game.
habitat - Modern applications with built-in automation
Parallel
coreutils - Cross-platform Rust rewrite of the GNU coreutils
rsedis - Redis re-implemented in Rust.
tauri - Build smaller, faster, and more secure desktop applications with a web frontend.
PumpkinDB - Immutable Ordered Key-Value Database Engine
tokei - Count your code, quickly.
ripgrep - ripgrep recursively searches directories for a regex pattern while respecting your gitignore