From 9205125fd8894836665a24afcec055a75e630a83 Mon Sep 17 00:00:00 2001
From: Luca Toscano <elukey@apache.org>
Date: Tue, 24 May 2016 11:42:26 +0000
Subject: [PATCH] Documentation rebuild

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1745344 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/manual/mod/mod_proxy.html.en | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/docs/manual/mod/mod_proxy.html.en b/docs/manual/mod/mod_proxy.html.en
index 7a49fab4a6..6b0128a98d 100644
--- a/docs/manual/mod/mod_proxy.html.en
+++ b/docs/manual/mod/mod_proxy.html.en
@@ -341,6 +341,17 @@ 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>The DNS domain resolution happens when the socket to
+        the origin server is created for the first time.
+        When connection pooling is used, the DNS resolution is performed
+        again only when the <code>ttl</code> of the connection expires
+        (please check <code class="directive"><a href="#proxypass">ProxyPass</a></code>
+        parameters).
+        This means that httpd does not perform any DNS resolution caching.
+        </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>
-- 
2.40.0