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

Remove DNS as a mandatory item #263

Closed
777petruh opened this issue Apr 7, 2024 · 6 comments
Closed

Remove DNS as a mandatory item #263

777petruh opened this issue Apr 7, 2024 · 6 comments
Labels
enhancement New feature or request

Comments

@777petruh
Copy link

Is it possible to change this parameter in your panel? I don't use DNS. And the panel forcibly asks me to indicate it.

@777petruh 777petruh added the enhancement New feature or request label Apr 7, 2024
@hoggatt
Copy link

hoggatt commented Apr 26, 2024

+1

I have to manually remove the DNS on each client because this requirement breaks in certain cases. I would go so far as to call this a bug, not an enhancement.

@barryboom
Copy link

DNS is set during the install of WG, And as far as i know is needed to instruct somewhere for the client to be able to lookup the endpoint especially when using a a web DNS rather than RAW like i do for my server endpoint.

@hoggatt
Copy link

hoggatt commented Apr 29, 2024

DNS is set during the install of WG, And as far as i know is needed to instruct somewhere for the client to be able to lookup the endpoint especially when using a a web DNS rather than RAW like i do for my server endpoint.

Well, I can say from personal experience that having wireguard with a DNS specified breaks my entire network on the client. If I remove the DNS from wireguard, everything works as expected. YMMV, but this seems like sufficient reason alone to make DNS the default, but not required.

@donaldzou
Copy link
Owner

Hi all, thank you for bringing this issue up. When I was designing the system, DNS is required in my use cases since I'm using to find my WG server. I will push an update to the newest version (v3.6) later today and I already removed the required in the upcoming v4.

Please let me know if there any other issues :)

@donaldzou
Copy link
Owner

Solved in 9e38137 :)

@hoggatt
Copy link

hoggatt commented May 3, 2024

Thanks so much! I did NOT expect this so soon. Excited for v4!

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

No branches or pull requests

4 participants