From f2ab316b5ddd759ee3a1959d715a93ed8d09f1ab Mon Sep 17 00:00:00 2001
From: Luca Toscano <elukey@apache.org>
Date: Tue, 24 May 2016 11:41:57 +0000
Subject: [PATCH] Adding a note to mod_proxy documentation to clarify DNS
 resolution with origin servers. Follow up from a question on users@.
 Backported from trunk.

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

diff --git a/docs/manual/mod/mod_proxy.xml b/docs/manual/mod/mod_proxy.xml
index e17cf7bdcf..201eb706ef 100644
--- a/docs/manual/mod/mod_proxy.xml
+++ b/docs/manual/mod/mod_proxy.xml
@@ -303,6 +303,17 @@ ProxyPass "/examples" "http://backend.example.com/examples" timeout=10
       Members are added to a balancer using
       <directive module="mod_proxy">BalancerMember</directive>.</p>
 
+      <note><title>DNS resolution for origin domains</title>
+      <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 <directive module="mod_proxy">ProxyPass</directive>
+        parameters).
+        This means that httpd does not perform any DNS resolution caching.
+        </p>
+      </note>
+
     </section> <!-- /workers -->
 
     <section id="access"><title>Controlling Access to Your Proxy</title>
-- 
2.40.0