diff options
author | Rich Trott <rtrott@gmail.com> | 2021-10-11 07:55:04 +0300 |
---|---|---|
committer | Antoine du Hamel <duhamelantoine1995@gmail.com> | 2021-10-20 12:59:11 +0300 |
commit | d0b58c0287e67a139137aa906819d95f8314b093 (patch) | |
tree | e9a92870138d89b608b1c6e6568611744c32c4f2 /doc/api/dns.md | |
parent | a7c17e08de658cbc0beefd8e9583803b5a62ac7e (diff) |
doc: format doc/api/*.md with markdown formatter
PR-URL: https://github.com/nodejs/node/pull/40403
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Zijian Liu <lxxyxzj@gmail.com>
Reviewed-By: Michaƫl Zasso <targos@protonmail.com>
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Diffstat (limited to 'doc/api/dns.md')
-rw-r--r-- | doc/api/dns.md | 161 |
1 files changed, 110 insertions, 51 deletions
diff --git a/doc/api/dns.md b/doc/api/dns.md index b5bcff0820e..63d0fbba9ab 100644 --- a/doc/api/dns.md +++ b/doc/api/dns.md @@ -52,6 +52,7 @@ dns.resolve4('archive.org', (err, addresses) => { See the [Implementation considerations section][] for more information. ## Class: `dns.Resolver` + <!-- YAML added: v8.3.0 --> @@ -94,6 +95,7 @@ The following methods from the `dns` module are available: * [`resolver.setServers()`][`dns.setServers()`] ### `Resolver([options])` + <!-- YAML added: v8.3.0 changes: @@ -117,6 +119,7 @@ Create a new resolver. each name server before giving up. **Default:** `4` ### `resolver.cancel()` + <!-- YAML added: v8.3.0 --> @@ -125,6 +128,7 @@ Cancel all outstanding DNS queries made by this resolver. The corresponding callbacks will be called with an error with code `ECANCELLED`. ### `resolver.setLocalAddress([ipv4][, ipv6])` + <!-- YAML added: - v15.1.0 @@ -148,17 +152,19 @@ servers, and the v6 local address when making requests to IPv6 DNS servers. The `rrtype` of resolution requests has no impact on the local address used. ## `dns.getServers()` + <!-- YAML added: v0.11.3 --> -* Returns: {string[]} +* Returns: {string\[]} Returns an array of IP address strings, formatted according to [RFC 5952][], that are currently configured for DNS resolution. A string will include a port section if a custom port is used. <!-- eslint-disable semi--> + ```js [ '4.4.4.4', @@ -169,6 +175,7 @@ section if a custom port is used. ``` ## `dns.lookup(hostname[, options], callback)` + <!-- YAML added: v0.1.90 changes: @@ -250,6 +257,7 @@ is not set to `true`, it returns a `Promise` for an `Object` with `address` and `family` properties. ### Supported getaddrinfo flags + <!-- YAML changes: - version: @@ -271,6 +279,7 @@ The following flags can be passed as hints to [`dns.lookup()`][]. well as IPv4 mapped IPv6 addresses. ## `dns.lookupService(address, port, callback)` + <!-- YAML added: v0.11.14 --> @@ -303,6 +312,7 @@ If this method is invoked as its [`util.promisify()`][]ed version, it returns a `Promise` for an `Object` with `hostname` and `service` properties. ## `dns.resolve(hostname[, rrtype], callback)` + <!-- YAML added: v0.1.27 --> @@ -311,15 +321,15 @@ added: v0.1.27 * `rrtype` {string} Resource record type. **Default:** `'A'`. * `callback` {Function} * `err` {Error} - * `records` {string[] | Object[] | Object} + * `records` {string\[] | Object\[] | Object} Uses the DNS protocol to resolve a host name (e.g. `'nodejs.org'`) into an array of the resource records. The `callback` function has arguments `(err, records)`. When successful, `records` will be an array of resource records. The type and structure of individual results varies based on `rrtype`: -| `rrtype` | `records` contains | Result type | Shorthand method | -|-----------|--------------------------------|-------------|--------------------------| +| `rrtype` | `records` contains | Result type | Shorthand method | +| --------- | ------------------------------ | ----------- | ------------------------ | | `'A'` | IPv4 addresses (default) | {string} | [`dns.resolve4()`][] | | `'AAAA'` | IPv6 addresses | {string} | [`dns.resolve6()`][] | | `'ANY'` | any records | {Object} | [`dns.resolveAny()`][] | @@ -331,12 +341,13 @@ records. The type and structure of individual results varies based on `rrtype`: | `'PTR'` | pointer records | {string} | [`dns.resolvePtr()`][] | | `'SOA'` | start of authority records | {Object} | [`dns.resolveSoa()`][] | | `'SRV'` | service records | {Object} | [`dns.resolveSrv()`][] | -| `'TXT'` | text records | {string[]} | [`dns.resolveTxt()`][] | +| `'TXT'` | text records | {string\[]} | [`dns.resolveTxt()`][] | On error, `err` is an [`Error`][] object, where `err.code` is one of the [DNS error codes](). ## `dns.resolve4(hostname[, options], callback)` + <!-- YAML added: v0.1.16 changes: @@ -354,7 +365,7 @@ changes: with the TTL expressed in seconds. * `callback` {Function} * `err` {Error} - * `addresses` {string[] | Object[]} + * `addresses` {string\[] | Object\[]} Uses the DNS protocol to resolve a IPv4 addresses (`A` records) for the `hostname`. The `addresses` argument passed to the `callback` function @@ -362,6 +373,7 @@ will contain an array of IPv4 addresses (e.g. `['74.125.79.104', '74.125.79.105', '74.125.79.106']`). ## `dns.resolve6(hostname[, options], callback)` + <!-- YAML added: v0.1.16 changes: @@ -379,7 +391,7 @@ changes: strings, with the TTL expressed in seconds. * `callback` {Function} * `err` {Error} - * `addresses` {string[] | Object[]} + * `addresses` {string\[] | Object\[]} Uses the DNS protocol to resolve a IPv6 addresses (`AAAA` records) for the `hostname`. The `addresses` argument passed to the `callback` function @@ -390,7 +402,7 @@ will contain an array of IPv6 addresses. * `hostname` {string} * `callback` {Function} * `err` {Error} - * `ret` {Object[]} + * `ret` {Object\[]} Uses the DNS protocol to resolve all records (also known as `ANY` or `*` query). The `ret` argument passed to the `callback` function will be an array containing @@ -398,22 +410,23 @@ various types of records. Each object has a property `type` that indicates the type of the current record. And depending on the `type`, additional properties will be present on the object: -| Type | Properties | -|------|------------| -| `'A'` | `address`/`ttl` | -| `'AAAA'` | `address`/`ttl` | -| `'CNAME'` | `value` | -| `'MX'` | Refer to [`dns.resolveMx()`][] | -| `'NAPTR'` | Refer to [`dns.resolveNaptr()`][] | -| `'NS'` | `value` | -| `'PTR'` | `value` | -| `'SOA'` | Refer to [`dns.resolveSoa()`][] | -| `'SRV'` | Refer to [`dns.resolveSrv()`][] | -| `'TXT'` | This type of record contains an array property called `entries` which refers to [`dns.resolveTxt()`][], e.g. `{ entries: ['...'], type: 'TXT' }` | +| Type | Properties | +| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | +| `'A'` | `address`/`ttl` | +| `'AAAA'` | `address`/`ttl` | +| `'CNAME'` | `value` | +| `'MX'` | Refer to [`dns.resolveMx()`][] | +| `'NAPTR'` | Refer to [`dns.resolveNaptr()`][] | +| `'NS'` | `value` | +| `'PTR'` | `value` | +| `'SOA'` | Refer to [`dns.resolveSoa()`][] | +| `'SRV'` | Refer to [`dns.resolveSrv()`][] | +| `'TXT'` | This type of record contains an array property called `entries` which refers to [`dns.resolveTxt()`][], e.g. `{ entries: ['...'], type: 'TXT' }` | Here is an example of the `ret` object passed to the callback: <!-- eslint-disable semi --> + ```js [ { type: 'A', address: '127.0.0.1', ttl: 299 }, { type: 'CNAME', value: 'example.com' }, @@ -435,6 +448,7 @@ queries. It may be better to call individual methods like [`dns.resolve4()`][], [`dns.resolveMx()`][], and so on. For more details, see [RFC 8482][]. ## `dns.resolveCname(hostname, callback)` + <!-- YAML added: v0.3.2 --> @@ -442,7 +456,7 @@ added: v0.3.2 * `hostname` {string} * `callback` {Function} * `err` {Error} - * `addresses` {string[]} + * `addresses` {string\[]} Uses the DNS protocol to resolve `CNAME` records for the `hostname`. The `addresses` argument passed to the `callback` function @@ -450,6 +464,7 @@ will contain an array of canonical name records available for the `hostname` (e.g. `['bar.example.com']`). ## `dns.resolveCaa(hostname, callback)` + <!-- YAML added: - v15.0.0 @@ -459,7 +474,7 @@ added: * `hostname` {string} * `callback` {Function} * `err` {Error} - * `records` {Object[]} + * `records` {Object\[]} Uses the DNS protocol to resolve `CAA` records for the `hostname`. The `addresses` argument passed to the `callback` function @@ -468,6 +483,7 @@ available for the `hostname` (e.g. `[{critical: 0, iodef: 'mailto:pki@example.com'}, {critical: 128, issue: 'pki.example.com'}]`). ## `dns.resolveMx(hostname, callback)` + <!-- YAML added: v0.1.27 --> @@ -475,7 +491,7 @@ added: v0.1.27 * `hostname` {string} * `callback` {Function} * `err` {Error} - * `addresses` {Object[]} + * `addresses` {Object\[]} Uses the DNS protocol to resolve mail exchange records (`MX` records) for the `hostname`. The `addresses` argument passed to the `callback` function will @@ -483,6 +499,7 @@ contain an array of objects containing both a `priority` and `exchange` property (e.g. `[{priority: 10, exchange: 'mx.example.com'}, ...]`). ## `dns.resolveNaptr(hostname, callback)` + <!-- YAML added: v0.9.12 --> @@ -490,7 +507,7 @@ added: v0.9.12 * `hostname` {string} * `callback` {Function} * `err` {Error} - * `addresses` {Object[]} + * `addresses` {Object\[]} Uses the DNS protocol to resolve regular expression based records (`NAPTR` records) for the `hostname`. The `addresses` argument passed to the `callback` @@ -504,6 +521,7 @@ function will contain an array of objects with the following properties: * `preference` <!-- eslint-skip --> + ```js { flags: 's', @@ -516,6 +534,7 @@ function will contain an array of objects with the following properties: ``` ## `dns.resolveNs(hostname, callback)` + <!-- YAML added: v0.1.90 --> @@ -523,7 +542,7 @@ added: v0.1.90 * `hostname` {string} * `callback` {Function} * `err` {Error} - * `addresses` {string[]} + * `addresses` {string\[]} Uses the DNS protocol to resolve name server records (`NS` records) for the `hostname`. The `addresses` argument passed to the `callback` function will @@ -531,6 +550,7 @@ contain an array of name server records available for `hostname` (e.g. `['ns1.example.com', 'ns2.example.com']`). ## `dns.resolvePtr(hostname, callback)` + <!-- YAML added: v6.0.0 --> @@ -538,13 +558,14 @@ added: v6.0.0 * `hostname` {string} * `callback` {Function} * `err` {Error} - * `addresses` {string[]} + * `addresses` {string\[]} Uses the DNS protocol to resolve pointer records (`PTR` records) for the `hostname`. The `addresses` argument passed to the `callback` function will be an array of strings containing the reply records. ## `dns.resolveSoa(hostname, callback)` + <!-- YAML added: v0.11.10 --> @@ -567,6 +588,7 @@ be an object with the following properties: * `minttl` <!-- eslint-skip --> + ```js { nsname: 'ns.example.com', @@ -580,6 +602,7 @@ be an object with the following properties: ``` ## `dns.resolveSrv(hostname, callback)` + <!-- YAML added: v0.1.27 --> @@ -587,7 +610,7 @@ added: v0.1.27 * `hostname` {string} * `callback` {Function} * `err` {Error} - * `addresses` {Object[]} + * `addresses` {Object\[]} Uses the DNS protocol to resolve service records (`SRV` records) for the `hostname`. The `addresses` argument passed to the `callback` function will @@ -599,6 +622,7 @@ be an array of objects with the following properties: * `name` <!-- eslint-skip --> + ```js { priority: 10, @@ -609,15 +633,18 @@ be an array of objects with the following properties: ``` ## `dns.resolveTxt(hostname, callback)` + <!-- YAML added: v0.1.27 --> <!--lint disable no-undefined-references list-item-bullet-indent--> + * `hostname` {string} * `callback` {Function} * `err` {Error} - * `records` <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Data_structures#String_type" class="type"><string[][]></a> + * `records` <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Data_structures#String_type" class="type">\<string\[]\[]></a> + <!--lint enable no-undefined-references list-item-bullet-indent--> Uses the DNS protocol to resolve text queries (`TXT` records) for the @@ -628,6 +655,7 @@ one record. Depending on the use case, these could be either joined together or treated separately. ## `dns.reverse(ip, callback)` + <!-- YAML added: v0.1.16 --> @@ -635,7 +663,7 @@ added: v0.1.16 * `ip` {string} * `callback` {Function} * `err` {Error} - * `hostnames` {string[]} + * `hostnames` {string\[]} Performs a reverse DNS query that resolves an IPv4 or IPv6 address to an array of host names. @@ -644,6 +672,7 @@ On error, `err` is an [`Error`][] object, where `err.code` is one of the [DNS error codes][]. ## `dns.setDefaultResultOrder(order)` + <!-- YAML added: - v16.4.0 @@ -654,6 +683,7 @@ added: Set the default value of `verbatim` in [`dns.lookup()`][] and [`dnsPromises.lookup()`][]. The value could be: + * `ipv4first`: sets default `verbatim` `false`. * `verbatim`: sets default `verbatim` `true`. @@ -663,11 +693,12 @@ priority than [`--dns-result-order`][]. When using [worker threads][], dns orders in workers. ## `dns.setServers(servers)` + <!-- YAML added: v0.11.3 --> -* `servers` {string[]} array of [RFC 5952][] formatted addresses +* `servers` {string\[]} array of [RFC 5952][] formatted addresses Sets the IP address and port of servers to be used when performing DNS resolution. The `servers` argument is an array of [RFC 5952][] formatted @@ -688,17 +719,18 @@ The `dns.setServers()` method must not be called while a DNS query is in progress. The [`dns.setServers()`][] method affects only [`dns.resolve()`][], -`dns.resolve*()` and [`dns.reverse()`][] (and specifically *not* +`dns.resolve*()` and [`dns.reverse()`][] (and specifically _not_ [`dns.lookup()`][]). This method works much like [resolve.conf](https://man7.org/linux/man-pages/man5/resolv.conf.5.html). That is, if attempting to resolve with the first server provided results in a -`NOTFOUND` error, the `resolve()` method will *not* attempt to resolve with +`NOTFOUND` error, the `resolve()` method will _not_ attempt to resolve with subsequent servers provided. Fallback DNS servers will only be used if the earlier ones time out or result in some other error. ## DNS promises API + <!-- YAML added: v10.6.0 changes: @@ -717,6 +749,7 @@ that return `Promise` objects rather than using callbacks. The API is accessible via `require('dns').promises` or `require('dns/promises')`. ### Class: `dnsPromises.Resolver` + <!-- YAML added: v10.6.0 --> @@ -764,6 +797,7 @@ The following methods from the `dnsPromises` API are available: * [`resolver.setServers()`][`dnsPromises.setServers()`] ### `resolver.cancel()` + <!-- YAML added: - v15.3.0 @@ -774,17 +808,19 @@ Cancel all outstanding DNS queries made by this resolver. The corresponding promises will be rejected with an error with code `ECANCELLED`. ### `dnsPromises.getServers()` + <!-- YAML added: v10.6.0 --> -* Returns: {string[]} +* Returns: {string\[]} Returns an array of IP address strings, formatted according to [RFC 5952][], that are currently configured for DNS resolution. A string will include a port section if a custom port is used. <!-- eslint-disable semi--> + ```js [ '4.4.4.4', @@ -795,6 +831,7 @@ section if a custom port is used. ``` ### `dnsPromises.lookup(hostname[, options])` + <!-- YAML added: v10.6.0 --> @@ -861,6 +898,7 @@ dnsPromises.lookup('example.com', options).then((result) => { ``` ### `dnsPromises.lookupService(address, port)` + <!-- YAML added: v10.6.0 --> @@ -887,6 +925,7 @@ dnsPromises.lookupService('127.0.0.1', 22).then((result) => { ``` ### `dnsPromises.resolve(hostname[, rrtype])` + <!-- YAML added: v10.6.0 --> @@ -899,12 +938,12 @@ of the resource records. When successful, the `Promise` is resolved with an array of resource records. The type and structure of individual results vary based on `rrtype`: -| `rrtype` | `records` contains | Result type | Shorthand method | -|-----------|--------------------------------|-------------|--------------------------| +| `rrtype` | `records` contains | Result type | Shorthand method | +| --------- | ------------------------------ | ----------- | -------------------------------- | | `'A'` | IPv4 addresses (default) | {string} | [`dnsPromises.resolve4()`][] | | `'AAAA'` | IPv6 addresses | {string} | [`dnsPromises.resolve6()`][] | | `'ANY'` | any records | {Object} | [`dnsPromises.resolveAny()`][] | -| `'CAA'` | CA authorization records | {Object} | [`dnsPromises.resolveCaa()`][] | +| `'CAA'` | CA authorization records | {Object} | [`dnsPromises.resolveCaa()`][] | | `'CNAME'` | canonical name records | {string} | [`dnsPromises.resolveCname()`][] | | `'MX'` | mail exchange records | {Object} | [`dnsPromises.resolveMx()`][] | | `'NAPTR'` | name authority pointer records | {Object} | [`dnsPromises.resolveNaptr()`][] | @@ -912,12 +951,13 @@ based on `rrtype`: | `'PTR'` | pointer records | {string} | [`dnsPromises.resolvePtr()`][] | | `'SOA'` | start of authority records | {Object} | [`dnsPromises.resolveSoa()`][] | | `'SRV'` | service records | {Object} | [`dnsPromises.resolveSrv()`][] | -| `'TXT'` | text records | {string[]} | [`dnsPromises.resolveTxt()`][] | +| `'TXT'` | text records | {string\[]} | [`dnsPromises.resolveTxt()`][] | On error, the `Promise` is rejected with an [`Error`][] object, where `err.code` is one of the [DNS error codes](). ### `dnsPromises.resolve4(hostname[, options])` + <!-- YAML added: v10.6.0 --> @@ -934,6 +974,7 @@ Uses the DNS protocol to resolve IPv4 addresses (`A` records) for the addresses (e.g. `['74.125.79.104', '74.125.79.105', '74.125.79.106']`). ### `dnsPromises.resolve6(hostname[, options])` + <!-- YAML added: v10.6.0 --> @@ -950,6 +991,7 @@ Uses the DNS protocol to resolve IPv6 addresses (`AAAA` records) for the addresses. ### `dnsPromises.resolveAny(hostname)` + <!-- YAML added: v10.6.0 --> @@ -962,22 +1004,23 @@ records. Each object has a property `type` that indicates the type of the current record. And depending on the `type`, additional properties will be present on the object: -| Type | Properties | -|------|------------| -| `'A'` | `address`/`ttl` | -| `'AAAA'` | `address`/`ttl` | -| `'CNAME'` | `value` | -| `'MX'` | Refer to [`dnsPromises.resolveMx()`][] | -| `'NAPTR'` | Refer to [`dnsPromises.resolveNaptr()`][] | -| `'NS'` | `value` | -| `'PTR'` | `value` | -| `'SOA'` | Refer to [`dnsPromises.resolveSoa()`][] | -| `'SRV'` | Refer to [`dnsPromises.resolveSrv()`][] | -| `'TXT'` | This type of record contains an array property called `entries` which refers to [`dnsPromises.resolveTxt()`][], e.g. `{ entries: ['...'], type: 'TXT' }` | +| Type | Properties | +| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `'A'` | `address`/`ttl` | +| `'AAAA'` | `address`/`ttl` | +| `'CNAME'` | `value` | +| `'MX'` | Refer to [`dnsPromises.resolveMx()`][] | +| `'NAPTR'` | Refer to [`dnsPromises.resolveNaptr()`][] | +| `'NS'` | `value` | +| `'PTR'` | `value` | +| `'SOA'` | Refer to [`dnsPromises.resolveSoa()`][] | +| `'SRV'` | Refer to [`dnsPromises.resolveSrv()`][] | +| `'TXT'` | This type of record contains an array property called `entries` which refers to [`dnsPromises.resolveTxt()`][], e.g. `{ entries: ['...'], type: 'TXT' }` | Here is an example of the result object: <!-- eslint-disable semi --> + ```js [ { type: 'A', address: '127.0.0.1', ttl: 299 }, { type: 'CNAME', value: 'example.com' }, @@ -995,6 +1038,7 @@ Here is an example of the result object: ``` ### `dnsPromises.resolveCaa(hostname)` + <!-- YAML added: - v15.0.0 @@ -1010,6 +1054,7 @@ certification authority authorization records available for the `hostname` 'pki.example.com'}]`). ### `dnsPromises.resolveCname(hostname)` + <!-- YAML added: v10.6.0 --> @@ -1021,6 +1066,7 @@ the `Promise` is resolved with an array of canonical name records available for the `hostname` (e.g. `['bar.example.com']`). ### `dnsPromises.resolveMx(hostname)` + <!-- YAML added: v10.6.0 --> @@ -1033,6 +1079,7 @@ containing both a `priority` and `exchange` property (e.g. `[{priority: 10, exchange: 'mx.example.com'}, ...]`). ### `dnsPromises.resolveNaptr(hostname)` + <!-- YAML added: v10.6.0 --> @@ -1051,6 +1098,7 @@ of objects with the following properties: * `preference` <!-- eslint-skip --> + ```js { flags: 's', @@ -1063,6 +1111,7 @@ of objects with the following properties: ``` ### `dnsPromises.resolveNs(hostname)` + <!-- YAML added: v10.6.0 --> @@ -1075,6 +1124,7 @@ records available for `hostname` (e.g. `['ns1.example.com', 'ns2.example.com']`). ### `dnsPromises.resolvePtr(hostname)` + <!-- YAML added: v10.6.0 --> @@ -1086,6 +1136,7 @@ Uses the DNS protocol to resolve pointer records (`PTR` records) for the containing the reply records. ### `dnsPromises.resolveSoa(hostname)` + <!-- YAML added: v10.6.0 --> @@ -1105,6 +1156,7 @@ following properties: * `minttl` <!-- eslint-skip --> + ```js { nsname: 'ns.example.com', @@ -1118,6 +1170,7 @@ following properties: ``` ### `dnsPromises.resolveSrv(hostname)` + <!-- YAML added: v10.6.0 --> @@ -1134,6 +1187,7 @@ the following properties: * `name` <!-- eslint-skip --> + ```js { priority: 10, @@ -1144,6 +1198,7 @@ the following properties: ``` ### `dnsPromises.resolveTxt(hostname)` + <!-- YAML added: v10.6.0 --> @@ -1158,6 +1213,7 @@ one record. Depending on the use case, these could be either joined together or treated separately. ### `dnsPromises.reverse(ip)` + <!-- YAML added: v10.6.0 --> @@ -1171,6 +1227,7 @@ On error, the `Promise` is rejected with an [`Error`][] object, where `err.code` is one of the [DNS error codes](). ### `dnsPromises.setDefaultResultOrder(order)` + <!-- YAML added: - v16.4.0 @@ -1181,6 +1238,7 @@ added: Set the default value of `verbatim` in [`dns.lookup()`][] and [`dnsPromises.lookup()`][]. The value could be: + * `ipv4first`: sets default `verbatim` `false`. * `verbatim`: sets default `verbatim` `true`. @@ -1190,11 +1248,12 @@ higher priority than [`--dns-result-order`][]. When using [worker threads][], default dns orders in workers. ### `dnsPromises.setServers(servers)` + <!-- YAML added: v10.6.0 --> -* `servers` {string[]} array of [RFC 5952][] formatted addresses +* `servers` {string\[]} array of [RFC 5952][] formatted addresses Sets the IP address and port of servers to be used when performing DNS resolution. The `servers` argument is an array of [RFC 5952][] formatted @@ -1217,7 +1276,7 @@ progress. This method works much like [resolve.conf](https://man7.org/linux/man-pages/man5/resolv.conf.5.html). That is, if attempting to resolve with the first server provided results in a -`NOTFOUND` error, the `resolve()` method will *not* attempt to resolve with +`NOTFOUND` error, the `resolve()` method will _not_ attempt to resolve with subsequent servers provided. Fallback DNS servers will only be used if the earlier ones time out or result in some other error. |