Summary

• Telegram media fetch fails on hosts with broken IPv6 because Node 24 changed the default dns-result-order to verbatim
• Modified resolvePinnedHostnameWithPolicy() in src/infra/net/ssrf.ts to sort IPv4 addresses before IPv6 in the resolved address list
• This ensures Happy Eyeballs (autoSelectFamily) and single-address round-robin try IPv4 first

Test plan

• Added test verifying IPv4-before-IPv6 ordering in pinned DNS
• All 20 SSRF tests pass
• All 35 Telegram tests pass
• TypeScript compiles cleanly

Fixes #23975

🤖 Generated with Claude Code

Greptile Summary

Modified resolvePinnedHostnameWithPolicy() in src/infra/net/ssrf.ts:280 to sort IPv4 addresses before IPv6 addresses in the resolved address list. This ensures Happy Eyeballs (autoSelectFamily) and single-address round-robin selection try IPv4 first, avoiding connection failures on hosts with broken IPv6 routing (common on cloud VMs and WSL2).

• Sorts addresses using toSorted() with a comparator that checks for colons to differentiate IPv6 from IPv4
• Preserves existing deduplication logic using Set
• Added comprehensive test case verifying IPv4-before-IPv6 ordering
• All 20 SSRF tests and 35 Telegram tests pass according to PR description

Confidence Score: 5/5

• Safe to merge with no issues found
• The implementation is simple, well-tested, and addresses a real production issue. The IPv6 detection logic using colon presence is reliable for all valid IP address formats, the sorting logic is straightforward, and test coverage validates the expected behavior. No security concerns or edge cases identified.
• No files require special attention

_{Last reviewed commit: ca53435}