Bug: WIREGUARD_ENDPOINT_IP doesn't support DNS

[OdinVex]

Is this urgent?

No

Host OS

No response

CPU arch

x86_64

VPN service provider

Custom

What are you using to run the container

docker-compose

What is the version of Gluetun

Running version latest built on 2025-10-06T11:38:57.746Z (commit 3400165)

What's the problem 🤔

I understand most VPN providers/servers use static IP addresses, but I'd like to be able to support a FQDN instead of IP. Wireguard naturally supports it (Endpoint = fqdn.example.com:12345)

Share your logs (at least 10 lines)

========================================
========================================
=============== gluetun ================
========================================
=========== Made with ❤️ by ============
======= https://github.com/qdm12 =======
========================================
========================================
Running version latest built on 2025-10-06T11:38:57.746Z (commit 3400165)
🔧 Need help? ☕ Discussion? https://github.com/qdm12/gluetun/discussions/new/choose
🐛 Bug? ✨ New feature? https://github.com/qdm12/gluetun/issues/new/choose
💻 Email? quentin.mcgaw@gmail.com
💰 Help me? https://www.paypal.me/qmcgaw https://github.com/sponsors/qdm12
2025-10-07T01:36:44Z ERROR reading VPN settings: VPN provider: server selection: files WIREGUARD_ENDPOINT_IP: ParseAddr("FQDN_REMOVED"): unexpected character (at "FQDN_REMOVED")
2025-10-07T01:36:44Z INFO Shutdown successful

Share your configuration

- VPN_SERVICE_PROVIDER=custom
- VPN_TYPE=wireguard


Relying on `/gluetun/wireguard/wg0.conf`

[github-actions]

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

• do not ask for updates, be patient
• 👍 the issue to show your support instead of commenting
  @qdm12 usually checks issues at least once a week, if this is a new urgent bug,
  revert to an older tagged container image

[OdinVex]

how did you determine this

The error message. There's only two locations for that variable WIREGUARD_ENDPOINT_IP, one is Dockerfile (irrelevant to runtime issue experiencing here, the other is internal/configuration/settings/wireguardselection.go:156. The API is for IP addresses only. https://tip.golang.org/src/net/netip/netip.go

[mathieuruellan]

@OdinVex I did a hack, it works, but not complete to be seriously merged.
#2940

[OdinVex]

@OdinVex I did a hack, it works, but not complete to be seriously merged. #2940

Sounds hopeful.

[OdinVex]

@OdinVex I did a hack, it works, but not complete to be seriously merged. #2940

I should note your work doesn't fix anything regarding internal/configuration/settings/wireguardselection.go:156 and such, so it'd still be quite broken. Edit: And hardcoding connectivity-testing entities like that is also something that'd definitely need to be changed/addressed (configurable entities, no defaults, especially to a privacy-raping company like Alphabet (Google)).

[qdm12]

The reason it is like that is: https://github.com/qdm12/gluetun-wiki/blob/main/faq/others.md#server-information

I'm working on allowing DNS for only A/AAAA requests for a single specific domain (the VPN server) whilst the VPN is down. This sounds simple, but is rather complex to implement, it involves fiddling with the DNS server (hence the change from Unbound to custom code I wrote) and the firewall, and hooking all this with the VPN up/down status. Please be patient 😉

Closing this as duplicate of #788

[github-actions]

Closed issues are NOT monitored, so commenting here is likely to be not seen.
If you think this is still unresolved and have more information to bring, please create another issue.

This is an automated comment setup because @qdm12 is the sole maintainer of this project
which became too popular to monitor issues closed.

[OdinVex]

The reason it is like that is: https://github.com/qdm12/gluetun-wiki/blob/main/faq/others.md#server-information

I'm working on allowing DNS for only A/AAAA requests for a single specific domain (the VPN server) whilst the VPN is down. This sounds simple, but is rather complex to implement, it involves fiddling with the DNS server (hence the change from Unbound to custom code I wrote) and the firewall, and hooking all this with the VPN up/down status. Please be patient 😉

Closing this as duplicate of #788

The code parsing as an IP address was I think the biggest issue. Wireguard alone can process it and perform a lookup, so this was just a barrier (unless other parts of Gluetun are held back at the moment).