Hi Christian,
I don't condone shipping patched binaries to your users, and I won't
provide support for that here. What I'd recommend instead, if you want
really fine grained control over DNS resolution, is to just resolve
your DNS names prior to calling wg(8), and then apply whatever policy
you wa
Lonnie,
Thanks for the quick response and the trivial fix! This is perfect
Best,
Christian
On Tue, Jun 15, 2021 at 9:24 AM Lonnie Abelbeck
wrote:
>
>
> > On Jun 15, 2021, at 5:52 AM, Jason A. Donenfeld wrote:
> >
> > This is intended behavior. DNS resolution happens at config parsing time.
>
>
Hey All,
I ran into some unexpected behavior with a script that calls
"/installtunnelservice" waits a bit, then calls
"/uninstalltunnelservice". This happens in a loop with some
connectivity checks in between.
When the tunnel service itself ("wireguard.exe /tunnelservice ...") is
killed, I notice
> On Jun 15, 2021, at 5:52 AM, Jason A. Donenfeld wrote:
>
> This is intended behavior. DNS resolution happens at config parsing time.
Christian,
While I appreciate Jason's strict DNS requirement, for the last 2.5 years our
project has implemented a trivial patch [1] to ignore endpoint DNS f
This is intended behavior. DNS resolution happens at config parsing time.
Jason,
Assume a tunnel with say 3 peers. Peer A is accessible via an IPv4
address, Peer B by some FQDN, and Peer C by some other FQDN. Let's
also assume that Peer C was misconfigured with an unresolvable FQDN.
wg syncconf (and setconf) fails with 'Name does not
resolve...Configuration parsing erro
