Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Shulhan <>
To: Devanath S <>
Cc: WireGuard mailing list <>
Subject: Re: wireguard-go on MACos
Date: Tue, 20 Sep 2022 01:29:39 +0700	[thread overview]
Message-ID: <20220920012939.78a8be42@inspiro.localdomain> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]

Hi Dev,

On Mon, 19 Sep 2022 10:47:29 -0700
Devanath S <> wrote:

> Hi All,
> We are using wireguard-go on MACOS/LINUX and a dns-proxy is listening
> on wireguard device. dns-proxy is receiving dns requests from the
> desktop (destined to wireguarddeviceip:53) on linuxos. But the same
> does not work on MACos.
> I have tried to create tun/ap using go-library (water) and was able to
> receive the requests, but the same fails when using a wireguard device
> created using wireguard-go. Also ping to wireguard device ip from the
> desktop fails miserably.

I assume you want to make all peers request to the same DNS server, yes?

In that case, instead of installing dns-proxy on each user, setup a
central DNS server and let the WireGuard handle the rest.

For example, in my experience, I setup rescached [1] (or any DNS
caches/forwarder) on the "server" peer at and set the DNS
option on each "client" peer to that address

  DNS =

With this mode, client does not need to install or setup anything except
the WireGuard application.


{ "git":"", "site":"" }

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2022-09-19 18:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19 17:47 Devanath S
2022-09-19 18:29 ` Shulhan [this message]
2022-09-19 18:55 ` Devanath S

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220920012939.78a8be42@inspiro.localdomain \ \ \ \

* 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).