build(deps): bump the hickory group across 1 directory with 2 updates

[dependabot]

Bumps the hickory group with 1 update in the / directory: hickory-resolver.

Updates hickory-resolver from 0.25.2 to 0.26.1

Release notes

Sourced from hickory-resolver's releases.

v0.26.1

This point release for the 0.26 release series brings in several bug fixes, and no user-facing changes. Two security reports are addressed: RUSTSEC-2026-0120 and RUSTSEC-2026-0119.

What's Changed

• net: avoid infinite loop in NSEC3 processing by @​djc in hickory-dns/hickory-dns#3597
• Limit work expended on name compression (backport) by @​divergentdave in hickory-dns/hickory-dns#3615

Full Changelog: hickory-dns/hickory-dns@v0.26.0...v0.26.1

0.26.0

13 months after the release of 0.25.0, we finally have a bigger feature release of Hickory DNS, the suite of DNS libraries and authoritative/recursive name servers written in pure Rust. A lot of work has gone into this release, so we wanted to take a moment to release this before we continue work on deploying the Hickory DNS recursive resolver at Let's Encrypt (and did you see that Hickory is being used in some of Google's Pixel devices?). Because of the ongoing work, we expect that 0.27.0 might happen quite a bit sooner than in 13 months from now.

These release notes describe a number of high-level improvements as well as API changes that are likely to break a larger fraction of our downstream users. Feedback (both on these notes and the release itself) is always welcome in our issue tracker or via our Discord server.

Most of the following notes are broken up by specific components: the server binary and our library crates. However, for this release we've made several changes to the structure of our crates itself:

• Network protocol support has moved out of the hickory-proto crate, into a new hickory-net crate (#3394); this allows the hickory-proto crate to cleanly focus on message encoding and decoding.
• The hickory-client crate has been subsumed into hickory-net, in the client module (#3366). No future releases of the hickory-client crate are expected.
• The hickory-recursor crate has been merged into hickory-resolver (#3370), guarded by a recursor feature which must be enabled explicitly. The recursor implementation was already tightly coupled to the resolver internals, so keeping it separate didn't really make sense.

Additionally, substantial cross-crate changes have been made to improve our error handling:

• More error handling simplification
• proto: split NetError out of ProtoError
• proto: clean up ProtoError
• Be more strict about decode errors
• resolver: remove unnecessary ResolveError wrapper
• Avoid large errors

hickory-dns (the server binary)

• We've added a number of ways to optimize performance via low-level networking configuration:
  • Use SO_REUSEADDR for tcp sockets
  • Allow configuring UDP socket buffer sizes
  • Add SO_REUSEPORT support with configurable UDP socket count
  • More TCP tuning options
• We further extended and reworked our metrics:
  • Additional recursive resolver metrics
  • Minor metrics tidying
  • Initial histogram metrics support
• Miscellaneous changes:
  • Implement RFC 5001 NSID for authoritative server
  • Add server SSLKEYLOGFILE support
  • Add systemd readiness + watchdog support
  • prometheus: enable gzip compression on metrics endpoint
  • Add support for jemalloc + profiling

hickory-server (the library API)

... (truncated)

Commits

• f093210 Limit number of names that may be compressed
• a9b884b Skip search when name compression is disabled
• 6e70e93 Limit number of name pointers stored in BinEncoder
• c2bdb8c Add benchmark for encoding message with many names
• 9e0b528 Bump version to 0.26.1
• 14cc3c8 net: respect caller timeout for DoT TCP connect
• fc2e3f4 resolver: release connections lock before TCP/TLS handshake
• bbdfcd2 Add tests combining NSEC and NSEC3 via CNAME chain
• 994076b Update rustls-webpki to 0.103.13
• 3b265fb net: check query name is in zone when building encloser candidates
• Additional commits viewable in compare view

Updates hickory-proto from 0.25.2 to 0.26.1

Release notes

Sourced from hickory-proto's releases.

v0.26.1

This point release for the 0.26 release series brings in several bug fixes, and no user-facing changes. Two security reports are addressed: RUSTSEC-2026-0120 and RUSTSEC-2026-0119.

What's Changed

• net: avoid infinite loop in NSEC3 processing by @​djc in hickory-dns/hickory-dns#3597
• Limit work expended on name compression (backport) by @​divergentdave in hickory-dns/hickory-dns#3615

Full Changelog: hickory-dns/hickory-dns@v0.26.0...v0.26.1

0.26.0

13 months after the release of 0.25.0, we finally have a bigger feature release of Hickory DNS, the suite of DNS libraries and authoritative/recursive name servers written in pure Rust. A lot of work has gone into this release, so we wanted to take a moment to release this before we continue work on deploying the Hickory DNS recursive resolver at Let's Encrypt (and did you see that Hickory is being used in some of Google's Pixel devices?). Because of the ongoing work, we expect that 0.27.0 might happen quite a bit sooner than in 13 months from now.

These release notes describe a number of high-level improvements as well as API changes that are likely to break a larger fraction of our downstream users. Feedback (both on these notes and the release itself) is always welcome in our issue tracker or via our Discord server.

Most of the following notes are broken up by specific components: the server binary and our library crates. However, for this release we've made several changes to the structure of our crates itself:

• Network protocol support has moved out of the hickory-proto crate, into a new hickory-net crate (#3394); this allows the hickory-proto crate to cleanly focus on message encoding and decoding.
• The hickory-client crate has been subsumed into hickory-net, in the client module (#3366). No future releases of the hickory-client crate are expected.
• The hickory-recursor crate has been merged into hickory-resolver (#3370), guarded by a recursor feature which must be enabled explicitly. The recursor implementation was already tightly coupled to the resolver internals, so keeping it separate didn't really make sense.

Additionally, substantial cross-crate changes have been made to improve our error handling:

• More error handling simplification
• proto: split NetError out of ProtoError
• proto: clean up ProtoError
• Be more strict about decode errors
• resolver: remove unnecessary ResolveError wrapper
• Avoid large errors

hickory-dns (the server binary)

• We've added a number of ways to optimize performance via low-level networking configuration:
  • Use SO_REUSEADDR for tcp sockets
  • Allow configuring UDP socket buffer sizes
  • Add SO_REUSEPORT support with configurable UDP socket count
  • More TCP tuning options
• We further extended and reworked our metrics:
  • Additional recursive resolver metrics
  • Minor metrics tidying
  • Initial histogram metrics support
• Miscellaneous changes:
  • Implement RFC 5001 NSID for authoritative server
  • Add server SSLKEYLOGFILE support
  • Add systemd readiness + watchdog support
  • prometheus: enable gzip compression on metrics endpoint
  • Add support for jemalloc + profiling

hickory-server (the library API)

... (truncated)

Commits

• f093210 Limit number of names that may be compressed
• a9b884b Skip search when name compression is disabled
• 6e70e93 Limit number of name pointers stored in BinEncoder
• c2bdb8c Add benchmark for encoding message with many names
• 9e0b528 Bump version to 0.26.1
• 14cc3c8 net: respect caller timeout for DoT TCP connect
• fc2e3f4 resolver: release connections lock before TCP/TLS handshake
• bbdfcd2 Add tests combining NSEC and NSEC3 via CNAME chain
• 994076b Update rustls-webpki to 0.103.13
• 3b265fb net: check query name is in zone when building encloser candidates
• Additional commits viewable in compare view

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[cratelyn]

superseded by #4544.

[dependabot]

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml