Fix wg0 DNS comment

[Jorundur]

Pull request

Purpose
Hope I'm not mistaken, but should we not make sure to remove the DNS line in our wg0-fix.conf file, regardless of its value? The container then sets the DNS values, right?

• These changes meet the standards for contributing.
• I have read the code of conduct.

[bokkoman]

I'm not sure, but i believe the environment variables overrule the wg0 dns setting.
If we know this for sure, we can ignore it in the conf file.

[bakerboy448]

With VPN_CONF you can set the name used for your WireGuard config. This is an example of how your wg0.conf file should look like. If there's a lot of extra stuff, remove it unless you know what it's there for. The WireGuard config is automatically modified to use AllowedIPs = 0.0.0.0/1,128.0.0.0/1 for compatibility with Synology/QNAP/Asustor/WSL2 systems if you append -fix, so VPN_CONF=wg0-fix. WSL2 users can also compile their own kernel if they don't wanna use this workaround.

[Interface]
PrivateKey = supersecretprivatekey
Address = xx.xx.xxx.xxx/32 # Yes, /32
DNS = x.x.x.x

[Peer]
PublicKey = publickey
AllowedIPs = 0.0.0.0/0
Endpoint = xxx.x.xxx.x:51820

[bokkoman]

@bakerboy448 but regardless of that, does the DNS settings in the template for qbit override the DNS setting in the conf?

[bakerboy448]

@bakerboy448 but regardless of that, does the DNS settings in the template for qbit override the DNS setting in the conf?

This is answered in hotio's documentation.