The /etc/resolv.conf file parser in rust
Find a file
June Clementine Strawberry 200e958941
use 1-indexed line numbers when displaying error messages
The line numbers stored in the ParseError struct are 0-indexed, which is
reasonable as an internal representation but very confusing in displayed
error messages.

Co-authored-by: Olivia Lee <olivia@computer.surgery>
Signed-off-by: June Clementine Strawberry <june@3.dog>
2025-04-05 17:36:36 -04:00
.github/workflows Upgrade to hostname 0.4 2025-03-13 10:55:02 +01:00
examples Fix formatting with cargo fmt 2025-03-13 10:46:59 +01:00
src use 1-indexed line numbers when displaying error messages 2025-04-05 17:36:36 -04:00
tests Apply suggestions from clippy 2025-03-13 10:46:59 +01:00
.gitignore Minimal working parser (many things are not supported yet) 2015-12-24 19:38:35 +02:00
.rustfmt.toml Fix formatting with cargo fmt 2025-03-13 10:46:59 +01:00
Cargo.toml bump rust edition to 2024 and toolchain to 1.86.0 2025-04-05 17:03:08 -04:00
deny.toml Add cargo-deny configuration 2025-03-13 10:46:59 +01:00
LICENSE-APACHE Changed license to dual MIT/Apache 2016-01-21 13:48:18 +02:00
LICENSE-MIT Changed license to dual MIT/Apache 2016-01-21 13:48:18 +02:00
README.md Fix formatting in readme 2018-02-04 16:14:27 +02:00

Resolv-conf

Status: Beta

A /etc/resolv.conf parser crate for rust.

Why?

  1. There is no bare file parser in the crates.io at the moment
  2. I needed one to make dns resolver for rotor

License

Licensed under either of

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.