I had done that already, but:
The external nameserver was contacted through the VPN gateway for DNS resolution of the domain of
my own server hosting the VPN service. This gave the external IP, for which a complex external route was found.
I have now an internal DNS service (dnsmasq), configured to contact external DNS services for anything but
requests for the server domain. In that latter case, the VPN gateway IP is given to the clients.
But since routing all server-related traffic directly to the server is THE purpose of a VPN network,
I think there is a better solution, perhaps related to how the server's internal network is announced
to the clients...