comparison xml/en/docs/http/ngx_http_core_module.xml @ 143:370cf5ccd3ca

The "resolver" directive now allows specifying multiple name servers.
author Ruslan Ermilov <ru@nginx.com>
date Tue, 25 Oct 2011 11:07:56 +0000
parents b9e5155d8f5d
children 8057b7793bd9
comparison
equal deleted inserted replaced
142:568b4e77c0d0 143:370cf5ccd3ca
1469 1469
1470 </directive> 1470 </directive>
1471 1471
1472 1472
1473 <directive name="resolver"> 1473 <directive name="resolver">
1474 <syntax><argument>address</argument></syntax> 1474 <syntax><argument>address</argument> ...</syntax>
1475 <default/> 1475 <default/>
1476 <context>http</context> 1476 <context>http</context>
1477 <context>server</context> 1477 <context>server</context>
1478 <context>location</context> 1478 <context>location</context>
1479 1479
1480 <para> 1480 <para>
1481 Sets the <argument>address</argument> of a name server, for example: 1481 Configures name servers used to resolve upstream server names,
1482 <example> 1482 for example:
1483 resolver 127.0.0.1; 1483 <example>
1484 </example> 1484 resolver 127.0.0.1 192.0.2.1;
1485 An <argument>address</argument> may also be a hostname, in which case 1485 </example>
1486 the first resolved address is used. 1486 An <argument>address</argument> argument may be specified as
1487 either an IPv4 address or a hostname;
1488 in the latter case, the first resolved IPv4 address is used.
1489 Name servers are queried in a round-robin fashion.
1490 <note>
1491 Before version 1.1.7, only a single name server could be configured.
1492 </note>
1487 </para> 1493 </para>
1488 1494
1489 </directive> 1495 </directive>
1490 1496
1491 1497