From: Matthias Urlichs <matthias@urlichs.de>
To: wireguard@lists.zx2c4.com
Subject: Re: Add local DNS forwarder to Windows client
Date: Sun, 15 Nov 2020 22:10:34 +0100 [thread overview]
Message-ID: <202a8449-56b7-dee6-8eba-c32cb1e56a97@urlichs.de> (raw)
In-Reply-To: <CADJb3qTCed6GvshAmqOuVV-T9Pk7g6gs=KgHPGFSP7e9J8aMig@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 920 bytes --]
On 15.11.20 19:42, Yves Goergen wrote:
> This reality includes host names like "pc1" and "pc2" in one LAN and
> "pc3" and "pc4" in the other LAN.
So you need a DNS proxy that knows about stripping .one.lan and .two.lan
suffixes from your host names before forwarding the request to the
requisite DNS server. Or one that asks both and merges the replies. None
of this is in any way difficult to code, or indeed specific to Wireguard.
Also, why would you want to reconfigure your DNS proxy whenever the
tunnel state changes? The proxy either gets an answer or it doesn't (or
it gets a ICMP Unreachable back). If not, the tunnel is down, either
because the other end is temporarily unreachable or because you tore
down the tunnel. No reconfiguration required, simply react to timeouts
and ICMPs / EHOSTUNREACH (or whatever the Windows equivalent is) as
appropriate.
--
-- Matthias Urlichs
[-- Attachment #1.1.2: OpenPGP_0x72CF8E5E25B4C293_and_old_rev.asc --]
[-- Type: application/pgp-keys, Size: 48415 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2020-11-15 21:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 10:31 Yves Goergen
2020-11-10 8:14 ` Tomcsanyi, Domonkos
2020-11-10 8:44 ` Der PCFreak
2020-11-10 15:38 ` Yves Goergen
2020-11-10 16:04 ` Matthias Urlichs
2020-11-10 18:08 ` Lech Perczak
2020-11-15 18:42 ` Yves Goergen
2020-11-15 21:10 ` Matthias Urlichs [this message]
2020-11-15 21:43 ` "Tomcsányi, Domonkos"
2020-11-11 7:36 ` Der PCFreak
[not found] ` <CADJb3qTGhm8a=aAA8_6ZgEHHFyBZyOch_GRBkC1p4yym28fN-Q@mail.gmail.com>
2020-11-10 10:47 ` Fwd: " Yves Goergen
2020-11-10 22:24 ` Tomcsanyi, Domonkos
2020-11-11 11:31 Stefan Puch
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=202a8449-56b7-dee6-8eba-c32cb1e56a97@urlichs.de \
--to=matthias@urlichs.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
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).