In section [5.2 Processing of DS RRs When Validating Responses](https://datatracker.ietf.org/doc/html/rfc4034#section-5.2) it states "The DNSKEY RR referred to in the DS RR MUST be a DNSSEC zone key.".
This changes the verification that a corresponding DNSKEY for a DS RR not only matches the digest, but also is zone key.
Building a `NameServerConfigGroup` using `from_ips_clear` currently
always causes a reallocation of the underlying `Vec<NameServerConfig>`,
because two config entries are inserted per IP, while capacity is only
reserved for one.
This fix adds the missing `2 *` constant factor to `Vec::with_capacity`.
* update all READMEs with notices about the name change
* update changelog for 0.24
* bump crate versions to 0.24
* update version notice information
* update readmes to back reference trust-dns
* rename all crates to hickory counterparts
* replace all Trust-DNS references in code and comments with Hickory DNS
* rename all Trust-DNS references to Hickory DNS in non-code
* rename all trust-dns-resolver references to hickory-resolver
* rename all trust-dns-client references to hickory-client
* rename all trust-dns-proto references to hickory-proto
* rename all trust-dns-server references to hickory-server
* rename all trust-dns-compatibility references to hickory-compatability
* rename all trust-dns-integration references to hickory-integration
* rename all trust-dns-util references to hickory-util
* Update MIT licenses to reference Hickory DNS
* update all trust-dns references to hickory-dns
* update all bluejekyll github references to hickorydns org
* Update name in Changelog
* make sure hickory-dns logs during tests
* add changelogs for recent main additions
* fix references to trust-dns and hickory in architecture
* update a few trust-dns references in READMEs
* fixup some dangling trust_dns references
* replace fka with formerly in change log
* replace all hickoydns org references to hickory-dns
* replace all http links with https
* update logos
* update hickorydns to hickory-dns for all other org references
* fix Notices of Trust-DNS to Hickory in each Readme
When serializing a ClientSubnet, if the source prefix is larger than
the address itself, we return an error. However, when deserializing
the same type we will happily take an invalid prefix. Fix this
consistency issue by rejecting invalid prefixes during
deserialization.