From: Simon McNair <simonmcnair@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: apologies if this DNS conditional forwarding query is a daft question
Date: Mon, 24 Jan 2022 09:59:55 +0000 [thread overview]
Message-ID: <c0520a00-cd2b-db1d-b678-4134593e7206@gmail.com> (raw)
Hi,
Again apologies if this is networking newb question
I have just spent the weekend laboriously learning about wireguard
windows and finally powershell & internet connection sharing. My usage
case is supporting a parents network and/or sharing resources in a small
site(s) to site(s) network.
My question is this. Without buying any extra commodity hardware, or
installing any more software is it possible to set up conditional DNS
forwarding per peer for DNS ? I would like each subnets DNS server (in
this case isp router) to handle DNS for that subnet.
i.e. if the dns request is for a subnet on peer A use DNS server
192.168.100.254 defined in peer A config
if the dns request is made a subnet on peer B use DNS server
192.168.110.254 defined in peer B config
Similar to this:
[Interface]
PrivateKey = pkhere
ListenPort = 12345
Address = 10.250.250.4/24
[PeerA]
PublicKey = peerpkhere
AllowedIPs = 192.168.100.0/24, 10.250.250.0/24
Endpoint = my.ddnsalias.net:5678
DNS = 192.168.100.254
[PeerB]
PublicKey = peerpkhere
AllowedIPs = 192.168.110.0/24, 10.250.250.0/24
Endpoint = my.ddnsalias.net:5678
DNS = 192.168.110.254
I know we already have the Interface level DNS option but that would
fail for peers unless conditional forwarding was configured which isn't
possible on most home routers. I know I can fix this with dnsmasq or a
pihole but that requires another machine on all the time. I was just
wondering if anything clever could easily be done within wireguard. I
know it's a big ask but it would be appreciated as an enhancement request.
Likewise, for the windows version of wireguard it would be cool if there
was an option to enable internet connection sharing on the client. I
have done this successfully (I am happy to share the steps if required)
although it was a huge pita and required dangerousscripts enabling which
I'm not keen on.
Thanks again for all the hard work Jason, I love the app, and it is
running happily on my ER-X and making my life better.
Regards
Simon
next reply other threads:[~2022-01-24 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 9:59 Simon McNair [this message]
2022-01-24 13:28 ` Frank Carmickle
2022-01-24 18:26 ` Simon McNair
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=c0520a00-cd2b-db1d-b678-4134593e7206@gmail.com \
--to=simonmcnair@gmail.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).