Development discussion of WireGuard
 help / color / mirror / Atom feed
From: David Crawshaw <crawshaw@tailscale.com>
To: Chris Johnson <johnsonc@astro.ucla.edu>
Cc: wireguard@lists.zx2c4.com,
	 "Alexander A. Klimov" <grandmaster@al2klimov.de>
Subject: Re: MacOS: DNS setting has no effect if the tunnel is not the default gw
Date: Wed, 2 Dec 2020 09:17:25 -0500	[thread overview]
Message-ID: <CANdrats9wwABmNEnP4SVQPZF5KitahcAQitWR1-_8GV9pSCwoA@mail.gmail.com> (raw)
In-Reply-To: <1d429a71-415e-2623-e0b5-34cca394ae9c@astro.ucla.edu>

On Wed, Dec 2, 2020 at 8:48 AM Chris Johnson <johnsonc@astro.ucla.edu> wrote:
>
> I am now running into this problem. I'm still running Mojave (10.14.6),
> if that makes any difference.
>
> If AllowedIPs is everything, then /etc/resolv.conf is modified with the
> remote DNS server.
> If AllowedIPs is a remote private network(s), then /etc/resolv.conf
> remains untouched, and DNS is local ISP.
>
> Did you ever find a solution or workaround? I do not want all of my
> traffic to go through this tunnel, but I *do* want DNS to resolve for
> those private subnet hosts.

I believe this behavior has changed in macOS 11 (Big Sur), and
resolv.conf is updated even if you don't set a default route through
the tunnel. I could not find any Apple API that can change this on
earlier versions of macOS.


> Cheers,
>
> Chris
>
> On 2020/10/31 07:38, Alexander A. Klimov wrote:
> > Hello there!
> >
> > I have two almost identical tunnels. The only difference:
> >
> > -AllowedIPs=0.0.0.0/0, ::/0
> > +AllowedIPs=192.168.234.153/32, 64:ff9b::192.168.234.153/128,
> > 192.168.234.186/32, 64:ff9b::192.168.234.186/128
> >
> > The first one's setting DNS=192.168.234.153 has an effect, the second
> > one's not.
> >
> > Has anyone seen this problem, too?
> > Does anyone even know how to workaround it?
> >
> > Best,
> > AK

      reply	other threads:[~2020-12-02 18:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-31 14:38 Alexander A. Klimov
2020-12-01 19:39 ` Chris Johnson
2020-12-02 14:17   ` David Crawshaw [this message]

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=CANdrats9wwABmNEnP4SVQPZF5KitahcAQitWR1-_8GV9pSCwoA@mail.gmail.com \
    --to=crawshaw@tailscale.com \
    --cc=grandmaster@al2klimov.de \
    --cc=johnsonc@astro.ucla.edu \
    --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).