On Tue, Oct 07, 2025 at 09:25:20PM -0700, Cy Schubert wrote: C> Without more context in the upstream commit log message it's difficult we C> must surmise that the wait for ARP/NDP resolution could be due to a very C> busy unbound service combined with latency in ARP/NDP resolution. I haven't C> found any upstream Github issues that document this problem.
When a system can't send UDP packets due to no ARP/NDP entry for the next hop, the packets are not stored in the send buffer. Or does unbound do this for the TCP socket? -- Gleb Smirnoff
