Thanks, addressed in v2. This version documents that --preresolve reuses resolved addresses on reconnects, and mentions the trade-off for dynamic DNS names and DNS64/NAT64 roaming.
Sam On Monday, June 29th, 2026 at 3:08 PM, Arne Schwabe <[email protected]> wrote: > Am 27.06.26 um 22:37 schrieb Sami Rusani via Openvpn-devel: > > > > Hi, > > > > Please find attached a small documentation patch for OpenVPN/openvpn#532. > > Thanks. This is a good start but I think we can improve this to give a > bit more context: > > +--preresolve > + Resolve configured ``--remote``, ``--local``, ``--http-proxy``, and > + ``--socks-proxy`` hostnames at startup before opening the connection. > + > > > I think we should mention that this also causes OpenVPN to never > reresolve the hostnames on reconnect. Which is a good thing if you use > something like persist-tun and DNS will not work while the VPN is down > but maybe is counter-productive if you have a dyndns name for your VPN > server or roaming to/from DNS64/NAT64 network where the IP address might > change. > > Arne >
v2-0001-Document-preresolve-option.patch
Description: Binary data
_______________________________________________ Openvpn-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openvpn-devel
