From: Luca Toscano <elukey@apache.org>
Date: Wed, 22 Jun 2016 10:43:34 +0000 (+0000)
Subject: Add mod-proxy DNS caching information to the documentation (follow up from users@)
X-Git-Tag: 2.4.23~72
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=1ac575b7823de599905ad8b5153c41cbef347141;p=thirdparty%2Fapache%2Fhttpd.git

Add mod-proxy DNS caching information to the documentation (follow up from users@)

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

diff --git a/docs/manual/mod/mod_proxy.xml b/docs/manual/mod/mod_proxy.xml
index e17cf7bdcf3..4aef0883a7f 100644
--- a/docs/manual/mod/mod_proxy.xml
+++ b/docs/manual/mod/mod_proxy.xml
@@ -303,6 +303,18 @@ 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>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 <directive module="mod_proxy">ProxyPass</directive>
+        parameters for more details about connection reuse.
+        </p>
+      </note>
+
     </section> <!-- /workers -->
 
     <section id="access"><title>Controlling Access to Your Proxy</title>