]> git.ipfire.org Git - thirdparty/openvpn.git/commitdiff
Correct note about DNS randomization in openvpn.8
authorGert Doering <gert@greenie.muc.de>
Sun, 24 May 2015 07:56:12 +0000 (09:56 +0200)
committerGert Doering <gert@greenie.muc.de>
Sun, 24 May 2015 11:18:02 +0000 (13:18 +0200)
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 <gert@greenie.muc.de>
Acked-by: Arne Schwabe <arne@rfc2549.org>
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

index 67e6ddd59b983d729639e0722166756ac6561a83..07219c3ec26c31609be729009b0fa84fc8443913 100644 (file)
@@ -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