From: Enzo A <r33int@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Weird behavior with IPv6 on Windows
Date: Thu, 15 Oct 2020 14:04:58 +0200 [thread overview]
Message-ID: <CAC=m+TjA+J8RqsiLwJWXtNoFvPUJ0xVHS=UKVUUeh=2yRz8yqA@mail.gmail.com> (raw)
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!
next reply other threads:[~2020-10-16 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 12:04 Enzo A [this message]
2020-10-16 15:12 ` Jérémy Prego
-- strict thread matches above, loose matches on Subject: below --
2020-10-14 23:50 Enzo A
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAC=m+TjA+J8RqsiLwJWXtNoFvPUJ0xVHS=UKVUUeh=2yRz8yqA@mail.gmail.com' \
--to=r33int@gmail.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).