learning-rust-trust-dns-resolver
trust-dns
| learning-rust-trust-dns-resolver | trust-dns | |
|---|---|---|
| 6 | 14 | |
| 0 | 3,254 | |
| - | - | |
| 0.0 | 7.1 | |
| 6 months ago | 7 months ago | |
| Rust | Rust | |
| MIT 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.
learning-rust-trust-dns-resolver
-
Rust: Move from binary to library and Add Documentation Examples that are tested.
I will give main details. But if you really want to look at the gory details, take a look at this diff
-
SPF: Adding Support for A and MX Mechanisms in Rust
A-Mechanism <-> MX-Mechanism click here
-
Rust Basic Testing
You can find the code related to this aritcle here
-
Manage Rust Code by Breaking it Up
If you want to see the code at this stage you can access it here
-
Deconstructing SPF with Rust using Generics
The code for this aritcle can be found here
-
Deconstructing SPF Records with Rust
You can get a copy of the complete code at the time of this writing here
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?
tunneler - Tunnel TCP or UDP traffic over TCP, (mutual) TLS or DNS (authoritative server or direct connection), implemented in Rust
parity-bitcoin - The Parity Bitcoin client
ipnetwork - A library to work with CIDRs in rust
woodpecker - Drill is an HTTP load testing application written in Rust
dog - A command-line DNS client.
citybound - A work-in-progress, open-source, multi-player city simulation game.
Parallel
rsedis - Redis re-implemented in Rust.
tauri - Build smaller, faster, and more secure desktop applications with a web frontend.
tokei - Count your code, quickly.
Servo - Servo, the embeddable, independent, memory-safe, modular, parallel web rendering engine
tv-renamer - Mirror of https://gitlab.com/mmstick/tv-renamer