Why can WireGuard peer only be set to an IP address vs FQDN?

ok, thanks for the confirmation.

I’ve been looking at every feature in VyOS to try to understand what supports FQDNs and what doesn’t.
Was thinking on telling Wireguard to just send the traffic to a local address and than have that translated or routed to the actual destination.
NAT doesn’t seem to support FQDN from what I can tell.

Is there any routing or service in VyOS that would be capable of doing this?

I understand some of the arguments on another post regarding FQDNs, Wireguard issues - #7 by hagbard, where it mentions things such as that dynamic re-creation will cause packet loss.
Well, if the IP changes on the target endpoint, the entire tunnel connection will go down.

Also considering exploring setting a Task Scheduler to directly change the config when an IP change is detected, but haven’t read the docs on that in detail yet.

Any ideas or workaround would be appreciated.