Fixing wg-quick's DNS= directive with a hatchet
geokozey at mailfence.com
Fri Oct 27 00:01:50 CEST 2017
> From: Jason A. Donenfeld <Jason at zx2c4.com>
> Sent: Thu Oct 26 23:11:02 CEST 2017
> To: Geo Kozey <geokozey at mailfence.com>
> Subject: Re: Fixing wg-quick's DNS= directive with a hatchet
> On Thu, Oct 26, 2017 at 9:58 PM, Geo Kozey <geokozey at mailfence.com> wrote:
> > What about usecases where more nameservers are needed, i.e. local nameserver used for caching, adblocking or whatever?
> Presumably those users wouldn't be using DNS= anyways, since they'd
> want a fixed resolv.conf with the address of their local nameserver.
> So, that's outside the scope of this discussion.
No, with fixed resolv.conf pointing to local namserver only there would be no DNS resolution as your cache has to come from somewhere. I'm talking specifically about local nameserver without external connectivity but I think users may want to use their own static nameservers with dynamic one which they get from wg for whatever reason. Having to chose one over another as only possibility isn't best solution IMO.
More information about the WireGuard