From 395e039e8e770cea906bb10860753b88110fdf12 Mon Sep 17 00:00:00 2001 From: "Yichun Zhang (agentzh)" Date: Tue, 27 Mar 2018 14:33:06 -0700 Subject: [PATCH] doc: fixed the resolv.conf file name, reported by Thibault Charbonnier. --- README.markdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.markdown b/README.markdown index 258b770..f4d7a67 100644 --- a/README.markdown +++ b/README.markdown @@ -11,7 +11,7 @@ Table of Contents * [For Users](#for-users) * [For Bundle Maintainers](#for-bundle-maintainers) * [Additional Features](#additional-features) - * [resolve.conf parsing](#resolveconf-parsing) + * [resolv.conf parsing](#resolvconf-parsing) * [Mailing List](#mailing-list) * [Report Bugs](#report-bugs) * [Copyright & License](#copyright--license) @@ -70,7 +70,7 @@ In additional to the standard nginx core features, this bundle also supports the [Back to TOC](#table-of-contents) -resolve.conf parsing +resolv.conf parsing -------------------- **syntax:** *resolver address ... [valid=time] [ipv6=on|off] [local=on|off|path]* @@ -80,10 +80,10 @@ resolve.conf parsing **context:** *http, stream, server, location* Similar to the [`resolver` directive](https://nginx.org/en/docs/http/ngx_http_core_module.html#resolver) -in standard nginx core with additional support for parsing additional resolvers from the `resolve.conf` file +in standard nginx core with additional support for parsing additional resolvers from the `resolv.conf` file format. -When `local=on`, the standard path of `/etc/resolver.conf` will be used. You may also specify arbitrary +When `local=on`, the standard path of `/etc/resolv.conf` will be used. You may also specify arbitrary path to be used for parsing, for example: `local=/tmp/test.conf`. When `local=off`, parsing will be disabled (this is the default).