Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Chris Johnson <johnsonc@astro.ucla.edu>
To: wireguard@lists.zx2c4.com
Cc: "Alexander A. Klimov" <grandmaster@al2klimov.de>
Subject: Re: MacOS: DNS setting has no effect if the tunnel is not the default gw
Date: Tue, 1 Dec 2020 11:39:57 -0800
Message-ID: <1d429a71-415e-2623-e0b5-34cca394ae9c@astro.ucla.edu> (raw)
In-Reply-To: <9f61c27c-3cae-3283-30e0-ce99fe73a305@al2klimov.de>

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.

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 13:38 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 [this message]
2020-12-02 14:17   ` David Crawshaw

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=1d429a71-415e-2623-e0b5-34cca394ae9c@astro.ucla.edu \
    --to=johnsonc@astro.ucla.edu \
    --cc=grandmaster@al2klimov.de \
    --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

Development discussion of WireGuard

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.vuxu.org/wireguard/0 wireguard/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 wireguard wireguard/ https://inbox.vuxu.org/wireguard \
		wireguard@lists.zx2c4.com
	public-inbox-index wireguard

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.wireguard


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git