Is a hostname a valid value value for Endpoint?

Is a hostname a valid value value for Endpoint?

[Jonathan Hult]

[-- Attachment #1: Type: text/plain, Size: 965 bytes --]

Greetings,

I would like to know if a hostname is a valid value for *Endpoint*? Today,
the documentation all seems to reference an IP address.

Today, Mullvad <https://mullvad.net/en/> currently sets *EndPoint* to a
hostname (see here <https://api.mullvad.net/public/relays/wireguard/v1/>)

In my case, my host is set to use a DNS server which routes VPN provider
domains to a bad IP (in order to block them).

1. If *EndPoint* should never be a hostname, perhaps we should prevent (or
at least warn) when it is found to be a hostname (instead of an IP address).

2. If *EndPoint* can be a hostname, then I think we want to ensure DNS is
set from the configuration file before attempting to connect. In the wg-quick
script <https://git.zx2c4.com/WireGuard/tree/src/tools/wg-quick/linux.bash>,
I updated the *cmd_up()* function to call *set_dns()* earlier on than it is
currently called. This prevents my host's original DNS server from blocking
anything.

Jonathan

[-- Attachment #2: Type: text/html, Size: 2808 bytes --]

Re: Is a hostname a valid value value for Endpoint?

[Jason A. Donenfeld]

The endpoint can contain a domain, yes.

However, the correct behavior is to look up that domain using the DNS
server that exists prior to turning on WireGuard. Otherwise you'd have
a chicken&egg problem with tunnel-only accessible DNS servers.