From: John Clendenen <john@dotdigital.digital>
To: wireguard@lists.zx2c4.com
Subject: macOS Client DNS
Date: Tue, 27 Apr 2021 13:47:05 -0400 [thread overview]
Message-ID: <CAGPm-BR2O2x56ryW9cGx6NWaoZSnQo_OSyHXp7KmNjOgZZWRcQ@mail.gmail.com> (raw)
Hi,
Looking for the proper place to get help with DNS in the macOS client.
If this is not it, please point me in the right direction.
I have macOS clients using wireguard to remote into the office. It
works great except the DNS server configured in the wg config (DNS =
X.X.X.X) is not always honored. The system will use the DNS server
configured on the physical interface instead.
This of course causes failure resolving records on the private lan and
DNS leaks.
Is this expected? Do I need to engineer some sort of workaround or is
this a bug?
I have run into this in previous cases with L2TP/ipsec in which case
the solution was to adjust the interface “service order” in macOS, but
the wireguard interface does not appear in that list.
reply other threads:[~2021-04-28 0:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAGPm-BR2O2x56ryW9cGx6NWaoZSnQo_OSyHXp7KmNjOgZZWRcQ@mail.gmail.com \
--to=john@dotdigital.digital \
--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).