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
... | ... |
@@ -268,9 +268,11 @@ not match |
268 | 268 |
If |
269 | 269 |
.B host |
270 | 270 |
is a DNS name which resolves to multiple IP addresses, |
271 |
-one will be randomly |
|
272 |
-chosen, providing a sort of basic load-balancing and |
|
273 |
-failover capability. |
|
271 |
+OpenVPN will try them in the order that the system getaddrinfo() |
|
272 |
+presents them, so priorization and DNS randomization is done |
|
273 |
+by the system library. Unless an IP version is forced by the |
|
274 |
+protocol specification (4/6 suffix), OpenVPN will try both IPv4 |
|
275 |
+and IPv6 addresses, in the order getaddrinfo() returns them. |
|
274 | 276 |
.\"********************************************************* |
275 | 277 |
.TP |
276 | 278 |
.B \-\-remote\-random\-hostname |