* 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
This allows custom runtimes to provide the hosts configuration in their
own way, like using io_uring instead of the std::fs::File::open() to
read the system hosts file.
Currently, if queries to name servers over UDP result in either a
truncated response, or any kind of error, the query will be retried over
TCP. It should be possible to only use TCP for the case of oversized
messages, and avoid it in the common case. This change makes this the
default behavior and adds an option to ResolverOpts that can be enabled
to get the current behavior.
