subspacecommunity/subspace

SUBSPACE_DISABLE_DNS not working

Opened this issue · 2 comments

The doc says "Use --env SUBSPACE_DISABLE_DNS=1 to make subspace generate WireGuard configs without the DNS option, preserving the user's DNS servers."

In the example in the readme, it says

"
# Optional variable to disable DNS server. Enabled by default.
# consider disabling DNS server, if supporting international VPN clients
--env SUBSPACE_DISABLE_DNS=0
"

So it is ambiguous in order to not have DNS field in the config if we should make the variable 0 or 1.

So I tried both. And no effect on the conf file. No matter what variable you pass dnsmasq always runs and DNS is always set to 10.99.97.1 in the config file.

I checked the env variables in docker and both the times it recognised 0 and 1. Still, the DNS field is getting generated in the config.

see #193 , specially #193 (comment)

See: #208

It has resolved it for me and its a pretty trivial fix if you want to build your own container.