edgedns
trust-dns
Our great sponsors
| edgedns | trust-dns | |
|---|---|---|
| 2 | 14 | |
| 498 | 3,254 | |
| - | - | |
| 0.0 | 7.1 | |
| over 3 years ago | 6 months ago | |
| Rust | Rust | |
| ISC License | GNU General Public License v3.0 or later |
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.
edgedns
- Ask HN: What side projects landed you a job?
-
How to build a CDN (1/3): introduction and basic components
For the biggest pioneers, there is also a variant to build your own GeoDNS service with your own name servers. But for this to make sense and real value, anycast IP addresses would be needed. Also a number of other reliable servers around the world with DDoS protection and then understand, select and adapt eg EdgeDNS or Czech Knot DNS (which also uses Cloudflare). However, commercial GeoDNS services are relatively cheap and reliable, so we can’t imagine an ROI that would make sense with our own small, non-commercial DNS solution.
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.
What are some alternatives?
rust-memcache - memcache client for rust
parity-bitcoin - The Parity Bitcoin client
moka - A high performance concurrent caching library for Rust
woodpecker - Drill is an HTTP load testing application written in Rust
dns-over-wikipedia - Redirect `.idk` domains using Wikipedia
citybound - A work-in-progress, open-source, multi-player city simulation game.
cachepot - cachepot is `sccache` with extra sec, which in turn is `ccache` with cloud storage
Parallel
vodo - A primitive DNS server written in Rust for fun.
rsedis - Redis re-implemented in Rust.
hitbox - A high-performance caching framework suitable for single-machine and for distributed applications in Rust
tauri - Build smaller, faster, and more secure desktop applications with a web frontend.