From 0322510375b5c54f63f5302b9088972d58b32b76 Mon Sep 17 00:00:00 2001 From: Gert Doering Date: Sun, 24 May 2015 09:56:12 +0200 Subject: [PATCH] Correct note about DNS randomization in openvpn.8 Commit 4880739c17b502d00a removed DNS randomization, and the dual-stack patches for 2.4 completely changed the getaddrinfo() result handling again, but neither fact ever made it into the man page. Trac #411 Signed-off-by: Gert Doering Acked-by: Arne Schwabe Message-Id: <1432454172-1318-1-git-send-email-gert@greenie.muc.de> URL: http://article.gmane.org/gmane.network.openvpn.devel/9730 --- doc/openvpn.8 | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/openvpn.8 b/doc/openvpn.8 index 67e6ddd59..07219c3ec 100644 --- a/doc/openvpn.8 +++ b/doc/openvpn.8 @@ -268,9 +268,11 @@ not match If .B host is a DNS name which resolves to multiple IP addresses, -one will be randomly -chosen, providing a sort of basic load-balancing and -failover capability. +OpenVPN will try them in the order that the system getaddrinfo() +presents them, so priorization and DNS randomization is done +by the system library. Unless an IP version is forced by the +protocol specification (4/6 suffix), OpenVPN will try both IPv4 +and IPv6 addresses, in the order getaddrinfo() returns them. .\"********************************************************* .TP .B \-\-remote\-random\-hostname -- 2.47.2