Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Jonathan Hult <jonathan@jonathanhult.com>
To: wireguard@lists.zx2c4.com
Subject: Is a hostname a valid value value for Endpoint?
Date: Mon, 18 Jun 2018 15:49:48 -0400	[thread overview]
Message-ID: <CAAmL+SmFnHXTQTQ+PjYHei_HQ4bw5gQAasPnPve9uNUFaryFsw@mail.gmail.com> (raw)

[-- 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 --]

             reply	other threads:[~2018-06-18 19:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-18 19:49 Jonathan Hult [this message]
2018-06-21 23:55 ` Jason A. Donenfeld

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAAmL+SmFnHXTQTQ+PjYHei_HQ4bw5gQAasPnPve9uNUFaryFsw@mail.gmail.com \
    --to=jonathan@jonathanhult.com \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).