Daniel McCarney

@buschtoens We still have not implemented the "orders" field on account objects and we're not considering this a required feature for the V2 launch. I expect it will be a...

> @cpu, can we expect to see any movement on this anytime soon? Unlikely. It's a non-trivial amount of work for a convenience and there is still substantial higher priority...

@rolandshoemaker was this resolved by https://github.com/letsencrypt/boulder/pull/2716 ?

I bumped into this updating some code from v0.23.2 to latest. On 0.23.2 this code works without panic when run with `--features dns-over-https-rustls` alone: ```rust use trust_dns_proto::rr::RecordType; use trust_dns_resolver::config::{ResolverConfig, ResolverOpts};...

I think there's two issues here: 1. Addressing what should happen if a feature for the source of trust anchors isn't provided (e.g. accounting for the `webpki-roots` default being removed)...

> I think there's two issues here: > > Addressing what should happen if a feature for the source of trust anchors isn't provided (e.g. accounting for the webpki-roots default...

> Probably in one of the error conversions in one of the error.rs modules. Good pointer, thanks! It's the `Clone` impl for `ProtoErrorKind`, specifically the `else` clause here: https://github.com/hickory-dns/hickory-dns/blob/6c2a1e2c238eaecff2b6b6c1c0e435685bc0997e/crates/proto/src/error.rs#L644-L648 That...

> there's no way to extract the existing custom error kind or something like that By my read we have the original error with full info as `e` from the...

> Breaking change is fine Sounds good. Here's a fix: https://github.com/hickory-dns/hickory-dns/pull/2181 I think it might be sensible to consider landing it & https://github.com/hickory-dns/hickory-dns/pull/2179 both, but with the `InvalidCertificate(UnknownIssuer)` error coming...

In general my understanding is that underscores are forbidden for **host names** but may occur in domain names in other contexts as the DNS is general beyond host names. Notably...