WireGuard Outbound DNS Regression #6567

Integrity requirements

• I have read all the comments in the issue template and ensured that this issue meet the requirements.
• I confirm that I have read the documentation, understand the meaning of all the configuration items I wrote, and did not pile up seemingly useful options or default values.
• I provided the complete config and logs, rather than just providing the truncated parts based on my own judgment.
• I searched issues and did not find any similar issues.
• The problem can be successfully reproduced in the latest Release

Description

proxy/wireguard/client.go:353

After PR #6287, WG outbound now ignores built-in DNS server completely, and uses hard coded Cloudflare DNS for ALL domain based outbounds through WG, which is a contradiction to the documentation and a regression, because the code path right now does not respect DNS caching at all (it now uses a copied DNS resolver from upstream wireguard-go library which is very basic and feature poor) and requries for every new connection for TCP and every packet for UDP!

Reproduction Method

x

Client config

x

Server config

x

Client log

x

Server log

x