resolve domain endpoints

[geraveoyomama]

Since IP addresses may not be constant, allowing nylon.domain.tld to be resolved would allow for an always on connecting if the ip does change.

It is not foolproof and I see issues with nylon when it comes to caching DNS requests and then waiting (or not) to determine the best route.

[encodeous]

Yeah, I have been thinking of this as well for the use case of DDNS. We can definitely re-resolve domains once in a while, but there is a slight inconsistency where vanilla wireguard clients don't re-resolve domains (to my knowledge), so we'd have to at least document that.

[geraveoyomama]

True andthat would be a boon Nylon has over vanilla wireguard then :)

Sidenote: I've looked through the code but I can't seem to find where Nylon parses the endpoints (ip:port). It'll be very obvious but I am currently not finding it :(

[encodeous]

I think a good start would be to simply replace

nylon/state/config.go

Line 21 in b30c2f7

Endpoints []netip.AddrPort

with a url