From: Luca Toscano <elukey@apache.org>
Date: Wed, 22 Jun 2016 10:43:51 +0000 (+0000)
Subject: Documentation rebuild
X-Git-Tag: 2.4.23~71
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=182c0b45056cfc88ad6f0396b3de4ece36ddc8e5;p=thirdparty%2Fapache%2Fhttpd.git

Documentation rebuild

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1749651 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/mod/mod_proxy.html.en b/docs/manual/mod/mod_proxy.html.en
index 7a49fab4a60..ddffcbecff6 100644
--- a/docs/manual/mod/mod_proxy.html.en
+++ b/docs/manual/mod/mod_proxy.html.en
@@ -341,6 +341,18 @@ ProxyPass "/examples" "http://backend.example.com/examples" timeout=10</pre>
       Members are added to a balancer using
       <code class="directive"><a href="#balancermember">BalancerMember</a></code>.</p>
 
+      <div class="note"><h3>DNS resolution for origin domains</h3>
+      <p>DNS resolution happens when the socket to
+        the origin domain is created for the first time.
+        When connection pooling is used, each backend domain is resolved 
+        only once per child process, and reused for all further connections 
+        until the child is recycled. This information should to be considered 
+        while planning DNS maintenance tasks involving backend domains. 
+        Please also check <code class="directive"><a href="#proxypass">ProxyPass</a></code>
+        parameters for more details about connection reuse.
+        </p>
+      </div>
+
     </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
 <div class="section">
 <h2><a name="access" id="access">Controlling Access to Your Proxy</a></h2>