Mercurial > hg > nginx-site

comparison xml/en/docs/http/ngx_http_core_module.xml @ 527:58d79f8c412d

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Documented 1.3.1 changes in "resolver".
author Ruslan Ermilov <ru@nginx.com>
date Tue, 05 Jun 2012 22:11:50 +0000
parents ef11546f75ee
children d8c7160527ae
comparison
equal deleted inserted replaced
526:4f907cde0382 527:58d79f8c412d
1843 <context>http</context> 1843 <context>http</context>
1844 <context>server</context> 1844 <context>server</context>
1845 <context>location</context> 1845 <context>location</context>
1846 1846
1847 <para> 1847 <para>
1848 Configures name servers used to resolve names of upstream servers, 1848 Configures name servers used to resolve names of upstream servers
1849 for example: 1849 into addresses, for example:
1850 <example> 1850 <example>
1851 resolver 127.0.0.1 192.0.2.1; 1851 resolver 127.0.0.1 [::1]:5353;
1852 </example> 1852 </example>
1853 An <value>address</value> parameter may be specified as 1853 An address can be specified as a domain name or IP address,
1854 either an IPv4 address or a hostname; 1854 and an optional port (1.3.1).
1855 in the latter case, the first resolved IPv4 address is used. 1855 <!--
1856 If address is specified using a domain name, only the first
1857 resolved IPv4 address is used.
1858 -->
1859 If port is not specified, the port 53 is used.
1856 Name servers are queried in a round-robin fashion. 1860 Name servers are queried in a round-robin fashion.
1857 <note> 1861 <note>
1858 Before version 1.1.7, only a single name server could be configured. 1862 Before version 1.1.7, only a single name server could be configured.
1863 Specifying name servers using IPv6 addresses is supported
1864 starting from version 1.3.1.
1859 </note> 1865 </note>
1860 By default, nginx caches answers using the TTL value of a response. 1866 By default, nginx caches answers using the TTL value of a response.
1861 An optional <literal>valid</literal> parameter allows to override it: 1867 An optional <literal>valid</literal> parameter allows to override it:
1862 <example> 1868 <example>
1863 resolver 127.0.0.1 192.0.2.1 valid=30s; 1869 resolver 127.0.0.1 [::1]:5353 valid=30s;
1864 </example> 1870 </example>
1865 <note> 1871 <note>
1866 Before version 1.1.9, tuning of caching time was not possible, 1872 Before version 1.1.9, tuning of caching time was not possible,
1867 and nginx always cached answers for the duration of 5 minutes. 1873 and nginx always cached answers for the duration of 5 minutes.
1868 </note> 1874 </note>