sing-box/protocol/trojan
世界 961b56b176
Use domain resolver for ECH config queries
When ECH is enabled without a static config, the HTTPS record query for
the ECH config list went through the DNS rules instead of the domain
resolver, and the migration of outbound DNS rule items to the domain
resolver left no way to select a DNS server for it. A rule rejecting
HTTPS records refused the query, and a default DNS server detoured
through the same outbound waited for its own connection until the query
timed out.

Send the query to the domain resolver of the dial fields, then the
default domain resolver, then the only DNS server, and fail it when
none of them is available. DNS servers must set their own domain
resolver for it, as they do for a domain server address.
2026-11-16 06:50:44 +00:00
..
inbound.go Refactor lifecycle to scoped cleanup 2026-10-09 12:36:03 +08:00
outbound.go Use domain resolver for ECH config queries 2026-11-16 06:50:44 +00:00