ginuerzh 92272e0bb4 fix(handler/dns): stop dropping nameservers with a port ...

systemNameservers validated the whole host:port string with net.ParseIP, which rejects anything carrying a port, so a legal resolv.conf entry such as "nameserver 8.8.8.8:5353" was silently skipped and the following SplitHostPort branch (missing port defaults to 53) could never run. Split first, validate the host only, and reassemble with JoinHostPort, which also brackets IPv6 addresses.

The Init fallback chain (hop/metadata DNS -> resolv.conf "system-N" -> hardcoded default) was also untestable: the resolv.conf rung, added in 684a0dd, depends on the host's file, so TestInit_DefaultExchanger failed on any machine that has one. Introduce a resolvConfPath indirection (a no-op var on Windows, where systemNameservers never reads a file) and add TestInit_SystemNameservers, which exposed the parser bug above.

2026-10-14 01:56:16 +00:00

..

handler_test.go

fix(handler/dns): stop dropping nameservers with a port

2026-10-14 01:56:16 +00:00

handler.go

feat(dns): use system nameservers from /etc/resolv.conf as fallback

2026-06-20 15:54:39 +08:00

metadata.go

fix(handler/forward): split readTimeout from pipe idleTimeout to prevent 15s download abort

2026-05-31 17:05:21 +08:00

resolv_unix_test.go

fix(handler/dns): stop dropping nameservers with a port

2026-10-14 01:56:16 +00:00

resolv_unix.go

fix(handler/dns): stop dropping nameservers with a port

2026-10-14 01:56:16 +00:00

resolv_windows.go

fix(handler/dns): stop dropping nameservers with a port

2026-10-14 01:56:16 +00:00