Weird behavior with IPv6 on Windows

[Enzo A]

Hello everyone,

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:
https://imgur.com/a/dnlg6nd

Thanks!