Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Peter Baumgartner <pete@lincolnloop.com>
To: wireguard@lists.zx2c4.com
Subject: MacOS client with local DNS resolver
Date: Fri, 12 Apr 2019 12:07:28 -0600	[thread overview]
Message-ID: <CAC6K9z=3D=xMwTBRf3sA_5=OKR2R8o6aRa3JedGxzxVEzn-+Bw@mail.gmail.com> (raw)

I'm using the official Mac GUI client (version 0.0.20190409) and am
having troubles with DNS after connection. I use a local DNS resolver,
so I have my DNS manually set to 127.0.0.1 on the network interface:

    $ scutil --dns | grep scoped -A50
    DNS configuration (for scoped queries)

    resolver #1
      nameserver[0] : 127.0.0.1
      if_index : 8 (en0)
      flags    : Scoped, Request A records, Request AAAA records
      reach    : 0x00030002 (Reachable,Local Address,Directly Reachable Address)

Once I activate a Wireguard tunnel, the resolvers are updated to the
IP of my Wireguard server:

    $ scutil --dns | grep scoped -A50
    DNS configuration (for scoped queries)

    resolver #1
      nameserver[0] : 10.0.77.1
      if_index : 8 (en0)
      flags    : Scoped, Request A records
      reach    : 0x00000002 (Reachable)

    resolver #2
      nameserver[0] : 10.0.77.1
      if_index : 19 (utun2)
      flags    : Scoped, Request A records
      reach    : 0x00000003 (Reachable,Transient Connection)

Setting `DNS = 127.0.0.1` on the [Interface] section for my client has
no effect.

How can I activate the tunnel, but keep my DNS resolver as 127.0.0.1?
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

                 reply	other threads:[~2019-05-06 20:39 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='CAC6K9z=3D=xMwTBRf3sA_5=OKR2R8o6aRa3JedGxzxVEzn-+Bw@mail.gmail.com' \
    --to=pete@lincolnloop.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).