Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SUBSPACE_DISABLE_DNS not working #200

Open
kmskrishna opened this issue Jul 2, 2021 · 2 comments
Open

SUBSPACE_DISABLE_DNS not working #200

kmskrishna opened this issue Jul 2, 2021 · 2 comments

Comments

@kmskrishna
Copy link

kmskrishna commented Jul 2, 2021

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.

@gchamon
Copy link

gchamon commented Jul 4, 2021

see #193 , specially #193 (comment)

@maduggan
Copy link

See: #208

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants