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

Feature request: Domain support for Wireguard endpoints #2736

Open
KuramaSyu opened this issue Mar 7, 2025 · 1 comment
Open

Feature request: Domain support for Wireguard endpoints #2736

KuramaSyu opened this issue Mar 7, 2025 · 1 comment

Comments

@KuramaSyu
Copy link

What's the feature 🧐

Currently, as wireguard endpoints, only IPs are supported. But I got a domain as Endpoint from my VPN provider. When resolving the domain to get the IP, I get 3 different ones. And I don't know if the IP will change at some point, hence gluetun would fail. This is why support for Domains, instead of IPs for a wireguard endpoint would be nice.

Extra information and references

Example for what I got from Windscribe:

[Peer]
...
Endpoint = zrh-264-wg.whiskergalaxy.com:443

nslookup:

user@debian ~> nslookup zrh-264-wg.whiskergalaxy.com
Server:         192.168.124.1
Address:        192.168.124.1#53

Non-authoritative answer:
Name:   zrh-264-wg.whiskergalaxy.com
Address: 141.255.162.196
Name:   zrh-264-wg.whiskergalaxy.com
Address: 31.7.62.52
Name:   zrh-264-wg.whiskergalaxy.com
Address: 141.255.162.212

well, which one to use know? Will the IP maybe change at some point? Is it at this point even secure, when depending on an IP?

These were my questions I had. The simplest way would be allowing domain names.

Copy link
Contributor

github-actions bot commented Mar 7, 2025

@qdm12 is more or less the only maintainer of this project and works on it in his free time.
Please:

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

1 participant