libresolv
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.6k
- Forks
- 1.3k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 69
Description
resolv.h exposes facilities to resolve DNS records. See:
- Google Bionic
- GNU C Library (I admit that I am slightly confused why it is not mentioned in the GNU C Library Manual.)
- musl
- FreeBSD
I would like to understand whether there is a particular reason why the symbols in resolv.h are not covered by the libc crate. If there is no particular reason, I would like to start working on inclusion. My original motivation is to resolve DNS records (of type SRV, TXT) and realized that the Rust standard library does not support this. My next natural step was to check the libc crate.
Target Triples: *-unknown-linux-gnu, *-unknown-android, *-unknown-freebsd (* to be narrowed down by testing).
References:
- Zig seems to support it: https://github.com/ziglang/zig/issues/12628
- There's a
resolvcrate, which wrapslibresolv-sys. It might benefit from this API.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the symbols and platform differences in resolv.h from Bionic, glibc, musl, and FreeBSD. Check the libc crate's existing platform bindings and test coverage for *-unknown-linux-gnu, *-unknown-android, and *-unknown-freebsd; done means determining supported target triples and covering the relevant libresolv APIs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100