Feature request: Permit FQDNs in place of IP addresses everywhere in the configuration file

noseshimself commented 2 years ago

What version of `nebula` are you using?

1.6.0

What operating system are you using?

Linux

Describe the Bug

(All symbolic names are on the reachable DNS and correctly defined.)

static_host_map:
  "172.31.255.254": ["81.20.89.254:4255"]

is working while

static_host_map:
  "lighthouse.backbone.nebula.domain.com": ["lighhouse.public.address..com:4255"]

is not.

relay:
  relays:
    - 172.31.254.254

is working while

relay:
  # Relays are a list of Nebula IP's that peers can use to relay packets to me.
  # IPs in this list must have am_relay set to true in their configs, otherwise
  # they will reject relay requests.
  relays:
    - relay.backbone.nebula.domain.com

is causing an error.

As running a full name server is helpful for address management and generating certificates using it for configuration files would be logical.

Logs from affected hosts

No response

Config files from affected hosts

No response

fabspro commented 2 years ago

In other words, you want to put private IP addresses into your public DNS to make management easier?

noseshimself commented 2 years ago

I'm using a mesh to make my life easier (call it "easiest applicable software defined network on the market" if you want). But that's besides the real question. The moment I have a nebula connection I can ask a private DNS. So another client wanting to reach me by relay has to have a connection already and could do a DNS lookup on a private server. The lighthouse would be a bit more of a problem but if people want to do that, why not?

virtadpt commented 2 years ago

It would be very helpful to be able to specify the FQDN of the lighthouse server in config files. If only so that it would be easy to determine which lighthouse is associated with a given host.

slackhq / nebula