Benjamin Fry

This seems reasonable. One issue I see is if there are any additional requests made (to follow a CNAME chain for example). So we'll need a way to handle that...

For some reason I thought that landed with the `_FOR_LEGACY_USE_ONLY`, but I guess I misunderstood some of the emails I saw fly by.

This is a great question. I really think we need to start a “book” that describes all of these things. I started a while ago, but never finished. in any...

Hm that’s awkward. I have seen an odd hang in one of the tests, but I haven’t looked into it. I wonder if it could be related. It sounds like...

I get the reasoning behind this, but I have some concerns. Specifically with DNSSec, masking a zone, i.e. your override upstream records request, seems like it would always fail DNSSec...

@balboah I think this would be more possible today than it was before. This configuration file is for a forwarder: https://github.com/bluejekyll/trust-dns/blob/master/tests/test-data/named_test_configs/example_forwarder.toml#L40-L41 I had an intention of allowing for chained resolvers,...

Ah, yes, we should clean this up. Probably deprecate the `new`? Some of these changes have come in as we've genericized the AsyncResolver across runtimes beyond Tokio into Fuchsia and...

I'm going to create a new category for this... they're more about DNS compliance than bugs, so going to move them in that direction.

At the moment I am not aware of anyone working on a DNS proxy as it relates to this project. I'm not sure if there is one in Rust based...

> expected trait object `dyn std::iter::Iterator`, found struct `std::slice::Iter` You will either need to cast this, i.e. `let response = &response as &dyn Iterator` or box it, `let response =...