comparison xml/en/docs/http/ngx_http_core_module.xml @ 185:05e7496801ec

Documented recent changes in the "resolver" directive.
author Ruslan Ermilov <ru@nginx.com>
date Wed, 16 Nov 2011 13:14:10 +0000
parents 0883fc5aabc9
children 09b8c8b2b865
comparison
equal deleted inserted replaced
184:4840aa7bab2c 185:05e7496801ec
1668 1668
1669 </directive> 1669 </directive>
1670 1670
1671 1671
1672 <directive name="resolver"> 1672 <directive name="resolver">
1673 <syntax><argument>address</argument> ...</syntax> 1673 <syntax>
1674 <argument>address</argument> ...
1675 [<parameter>valid</parameter>=<argument>time</argument>]
1676 </syntax>
1674 <default/> 1677 <default/>
1675 <context>http</context> 1678 <context>http</context>
1676 <context>server</context> 1679 <context>server</context>
1677 <context>location</context> 1680 <context>location</context>
1678 1681
1686 either an IPv4 address or a hostname; 1689 either an IPv4 address or a hostname;
1687 in the latter case, the first resolved IPv4 address is used. 1690 in the latter case, the first resolved IPv4 address is used.
1688 Name servers are queried in a round-robin fashion. 1691 Name servers are queried in a round-robin fashion.
1689 <note> 1692 <note>
1690 Before version 1.1.7, only a single name server could be configured. 1693 Before version 1.1.7, only a single name server could be configured.
1694 </note>
1695 By default, nginx caches answers using the TTL value of a response.
1696 An optional <parameter>valid</parameter> parameter allows to override it:
1697 <example>
1698 resolver 127.0.0.1 192.0.2.1 valid=30s;
1699 </example>
1700 <note>
1701 Before version 1.1.9, tuning of caching time was not possible,
1702 and nginx always cached answers for the duration of 5 minutes.
1691 </note> 1703 </note>
1692 </para> 1704 </para>
1693 1705
1694 </directive> 1706 </directive>
1695 1707