Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Mark Felder" <feld@feld.me>
To: wireguard@lists.zx2c4.com
Subject: [MacOS] DNS search path not working?
Date: Thu, 28 Apr 2022 09:14:13 -0400	[thread overview]
Message-ID: <80f2d9f4-9917-4e59-87fc-6713e80b1880@www.fastmail.com> (raw)

Hello,

I've observed this on MacOS 12 Monterey. I have also tested on iOS 15.4.1 where it works as expected. (I know they share the same codebase).

On MacOS I have my DNS configured correctly as DNS = 1.2.3.4, int.foo.com but it doesn't seem to actually work. e.g., if I have a host named server.int.foo.com I cannot just "ping server"; I have to use the FQDN of server.int.foo.com.

This behavior works correctly with an OpenVPN connection using the Viscosity software. I have compared the output of scutil --dns and verified that both OpenVPN and Wireguard appear to generate identical DNS configuration. I'm not sure where else to look for differences between what OpenVPN/Viscosity and Wireguard are doing.

Any tips?


Thanks!


Mark

-- 
  Mark Felder
  feld@feld.me

                 reply	other threads:[~2022-04-30 14:41 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=80f2d9f4-9917-4e59-87fc-6713e80b1880@www.fastmail.com \
    --to=feld@feld.me \
    --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).