Andre 77689a9aec fix: make tunnel start despite unreadable DNS answers ...

wstunnel's built-in DNS resolver fails on some DNS servers because it
cannot read their EDNS answers. With a connection pool the client then
never opened the local port. Use the Windows resolver instead.

The port check also took ~2 s per attempt, so the start script showed
an empty window for a long time before the error appeared.

2026-10-23 09:37:41 +02:00

..

chrome.ps1

git init

2026-10-22 21:00:05 +02:00

codex.ps1

git init

2026-10-22 21:00:05 +02:00

common.ps1

fix: make tunnel start despite unreadable DNS answers

2026-10-23 09:37:41 +02:00

path.ps1

git init

2026-10-22 21:00:05 +02:00

tunnel.ps1

git init

2026-10-22 21:00:05 +02:00