From: Luca Toscano Date: Sat, 18 Jun 2016 10:14:08 +0000 (+0000) Subject: Documentation rebuild X-Git-Tag: 2.5.0-alpha~1495 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=6ad65bbc764e2ca61a6d24a0ebb7884b57c572d0;p=thirdparty%2Fapache%2Fhttpd.git Documentation rebuild git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1748949 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_proxy.html.en b/docs/manual/mod/mod_proxy.html.en index fa88427cb4c..9a40141b36c 100644 --- a/docs/manual/mod/mod_proxy.html.en +++ b/docs/manual/mod/mod_proxy.html.en @@ -342,13 +342,14 @@ ProxyPass "/examples" "http://backend.example.com/examples" timeout=10 BalancerMember.

DNS resolution for origin domains

-

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 ttl of the connection expires - (please check ProxyPass - parameters). - This means that httpd does not perform any DNS resolution caching. +

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 ProxyPass + parameters for more details about connection reuse.