Benjamin Fry

Results 55 issues of Benjamin Fry

I've been working with `cargo-make` recently, and coverage reports weren't accurate. I came across this project, and found the requirement to specify which test you wanted to run to be...

Getting this error on macOS, trying to use corrode with a signal.h inclusion. ```console /usr/include/signal.h:79: (column 19) [ERROR] >>> Syntax Error ! Syntax error ! The symbol `bsd_signal' does not...

**Is your feature request related to a problem? Please describe.** Allow for rejection of requests coming from unwanted IP ranges. The implementation should support ipv4 and ipv6 CIDR formatted configuration....

ops
crate:server

This is pretty rough right now, probably a lot of work to do, but it does work for some basic queries, for example: `cargo run --all-features --bin recurse -- --debug...

Currently \" is not accepted in Label parsing. In this funtion: https://github.com/bluejekyll/trust-dns/blob/master/crates/proto/src/rr/domain/label.rs#L215 We should 1) better document what these flags do. 2) perhaps change the default match case `_` to...

bug
easy

**Is your feature request related to a problem? Please describe.** We should support both an IP based do-non-query-list as well as a domain name based list. When the IPs will...

ops
crate:resolver
crate:recursor

**Is your feature request related to a problem? Please describe.** For various reasons, it can be important to operators to avoid the usage of either particular interfaces or outbound ports....

ops
crate:proto

**Is your feature request related to a problem? Please describe.** Some namesevers will rate-limit clients. We should come up with new algorithms and policies for how to choose the a...

perf
ops
crate:resolver
crate:recursor

**Is your feature request related to a problem? Please describe.** Once #1710 is merged, we should add a new caching authority that sits in front of the recursor requests and...

perf
crate:resolver
crate:recursor

**Is your feature request related to a problem? Please describe.** Currently only bottom-up (stub resolution) DNSSEC validation is supported. With #1710 and a recursive resolver, DNSSEC validation from the top-down...

feature:dnsssec
crate:recursor