the original WireGuard implementation resolves DNS name of peer endpoint once at startup. it does not re-resolve the DNS name. the developer said "it's not a bug". a script, reresolve-dns, to "refresh" addresses is provided for Un*x machines. i believe this behavior is not part of the spec, but other implementations, including the upstream and OpenBSD's wg(4) for example, do the same. One implementation supports DNS resolution in its driver (DNS Updates to WireGuard Endpoints | Pro Custodibus).
the original WireGuard implementation resolves DNS name of peer endpoint once at startup. it does not re-resolve the DNS name. the developer said "it's not a bug". a script, reresolve-dns, to "refresh" addresses is provided for Un*x machines. i believe this behavior is not part of the spec, but other implementations, including the upstream and OpenBSD's wg(4) for example, do the same. One implementation supports DNS resolution in its driver (DNS Updates to WireGuard Endpoints | Pro Custodibus).