[PR #2578] [CLOSED] Use larger fallback for `max_payload()` to accommodate larger nam server responses #3151

New issue

Closed

opened 2026-03-16 11:28:10 +03:00 by kerem · 0 comments

kerem commented

2026-03-16 11:28:10 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/hickory-dns/hickory-dns/pull/2578
Author: @alexrenz
Created: 11/18/2024
Status: ❌ Closed

Base: main ← Head: patch-1

📝 Commits (1)

1af7762 Use larger default buffer size

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 crates/proto/src/op/message.rs (+1 -1)

📄 Description

First off, let me say: thank you for developing the hickory set of crates 💛 These are super helpful!

We are using the hickory resolver in reqwest and ran into an issue in Azure, where hickory failed to resolve our URLs with warnings like this:

2024-11-07T15:48:47.050514Z  WARN hickory_proto::udp::udp_client_stream: dropped malformed message waiting for id: 50916 err: unexpected end of input reached

After some investigation, we figured out that Azure name servers were sending responses that were larger than 512 bytes to non-eDNS requests. In our understanding, this is a problem because hickory seems to use a receive buffer of 512 bytes for non-eDNS responses.

This PR increases the buffer size for non-eDNS responses to avoid this problem.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/hickory-dns/hickory-dns/pull/2578 **Author:** [@alexrenz](https://github.com/alexrenz) **Created:** 11/18/2024 **Status:** ❌ Closed **Base:** `main` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`1af7762`](https://github.com/hickory-dns/hickory-dns/commit/1af7762cfad6127e3aa249afb222e43b550800bf) Use larger default buffer size ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `crates/proto/src/op/message.rs` (+1 -1) </details> ### 📄 Description First off, let me say: thank you for developing the hickory set of crates 💛 These are super helpful! We are using the hickory resolver in reqwest and ran into an issue in Azure, where hickory failed to resolve our URLs with warnings like this: ``` 2024-11-07T15:48:47.050514Z WARN hickory_proto::udp::udp_client_stream: dropped malformed message waiting for id: 50916 err: unexpected end of input reached ``` After some investigation, we figured out that Azure name servers were sending responses that were larger than 512 bytes to non-eDNS requests. In our understanding, this is a problem because hickory seems to use a receive buffer of 512 bytes for non-eDNS responses. This PR increases the buffer size for non-eDNS responses to avoid this problem. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>