Benjamin Fry

Depends on the connection type. For UDP it doesn't mean much, an open socket awaiting a response, but a new socket will be used for every request to ensure we...

So we have some example configs for this, and basically the `trust-dns` binary needs this features: `sqlite` and `dnssec-ring`. With that enabled you can follow this example: https://github.com/bluejekyll/trust-dns/blob/dc5c414ec0553af8a65441d0c747fb8e9f8e174e/tests/test-data/named_test_configs/dnssec_with_update.toml#L46 and you'll...

I reread your question, and realize I didn't answer it properly. Sqlite is currently only used for a journal in trust-dns. This has some limitations, especially in regards to zone...

In #1710 I've got the beginning of a recursive resolver, it needs a bit of cleanup though.

What you're talking about here @vlmutolo is something similar to what we used to do but ended up removing. The history around it was that for the general use case,...

> Have to be very careful about which kinds of error responses count as failures in this case, I suppose? yes, this is where we've run into issues in the...

Hm, it's possible that there is a bug/feature in the SRV lookup logic. We might only be resolving the first SRV record fully? Given that this is just a filter...

More specifically, this might be the problem area: https://github.com/bluejekyll/trust-dns/blob/master/crates/resolver/src/lookup_state.rs#L261-L291 We might be filtering a little too aggressively. The trust-dns-resolver tries to put an easy to use API around this stuff,...

This seems like a promising change.

That's a good point on the naming of the binary. We should definitely consider that. Today, we actually do have the named binary in it's own crate. The only complexity...