Weird behavior with IPv6 on Windows
r33int at gmail.com
Thu Oct 15 01:50:09 CEST 2020
First of all, thanks a lot for developing and maintaining Wireguard.
It really is an amazing product!
I am running with a strange issue with Wireguard on Windows. When my
tunnel is enabled, DNS-resolving hosts that are in AllowedIPs results
in the A (IPv4) record of the (sub)domain being resolved over the AAAA
(IPv6) record, which gets ignored when wireguard is enabled.
The intended behavior is that the AAAA record always gets resolved in priority.
Here is my client config: https://del.dog/easocerran.txt, and here are
also some screenshots of an example ping showing the issue:
More information about the WireGuard