# HG changeset patch
# User Ruslan Ermilov <ru@nginx.com>
# Date 1321449250 0
# Node ID 05e7496801ec19e1fa68fb0622712421a9f61d37
# Parent  4840aa7bab2c931a6a5d43470488698bc90b0c41
Documented recent changes in the "resolver" directive.

diff --git a/xml/en/docs/http/ngx_http_core_module.xml b/xml/en/docs/http/ngx_http_core_module.xml
--- a/xml/en/docs/http/ngx_http_core_module.xml
+++ b/xml/en/docs/http/ngx_http_core_module.xml
@@ -1670,7 +1670,10 @@ closed normally.
 
 
 <directive name="resolver">
-<syntax><argument>address</argument> ...</syntax>
+<syntax>
+<argument>address</argument> ...
+[<parameter>valid</parameter>=<argument>time</argument>]
+</syntax>
 <default/>
 <context>http</context>
 <context>server</context>
@@ -1689,6 +1692,15 @@ Name servers are queried in a round-robi
 <note>
 Before version 1.1.7, only a single name server could be configured.
 </note>
+By default, nginx caches answers using the TTL value of a response.
+An optional <parameter>valid</parameter> parameter allows to override it:
+<example>
+resolver 127.0.0.1 192.0.2.1 valid=30s;
+</example>
+<note>
+Before version 1.1.9, tuning of caching time was not possible,
+and nginx always cached answers for the duration of 5 minutes.
+</note>
 </para>
 
 </directive>