@@ -140,7 +140,7 @@ The resolver instance will send its requests from the specified IP address.
140
140
This allows programs to specify outbound interfaces when used on multi-homed
141
141
systems.
142
142
143
- If a v4 or v6 address is not specified, it is set to the default, and the
143
+ If a v4 or v6 address is not specified, it is set to the default and the
144
144
operating system will choose a local address automatically.
145
145
146
146
The resolver will use the v4 local address when making requests to IPv4 DNS
@@ -222,7 +222,7 @@ such as no available file descriptors.
222
222
223
223
` dns.lookup() ` does not necessarily have anything to do with the DNS protocol.
224
224
The implementation uses an operating system facility that can associate names
225
- with addresses, and vice versa. This implementation can have subtle but
225
+ with addresses and vice versa. This implementation can have subtle but
226
226
important consequences on the behavior of any Node.js program. Please take some
227
227
time to consult the [ Implementation considerations section] [ ] before using
228
228
` dns.lookup() ` .
@@ -268,7 +268,7 @@ The following flags can be passed as hints to [`dns.lookup()`][].
268
268
returned if the current system has at least one IPv4 address configured.
269
269
* ` dns.V4MAPPED ` : If the IPv6 family was specified, but no IPv6 addresses were
270
270
found, then return IPv4 mapped IPv6 addresses. It is not supported
271
- on some operating systems (e.g FreeBSD 10.1).
271
+ on some operating systems (e.g. FreeBSD 10.1).
272
272
* ` dns.ALL ` : If ` dns.V4MAPPED ` is specified, return resolved IPv6 addresses as
273
273
well as IPv4 mapped IPv6 addresses.
274
274
@@ -353,7 +353,7 @@ changes:
353
353
354
354
* ` hostname ` {string} Host name to resolve.
355
355
* ` options ` {Object}
356
- * ` ttl ` {boolean} Retrieve the Time-To-Live value (TTL) of each record.
356
+ * ` ttl ` {boolean} Retrieves the Time-To-Live value (TTL) of each record.
357
357
When ` true ` , the callback receives an array of
358
358
` { address: '1.2.3.4', ttl: 60 } ` objects rather than an array of strings,
359
359
with the TTL expressed in seconds.
@@ -387,7 +387,7 @@ changes:
387
387
* ` err ` {Error}
388
388
* ` addresses ` {string\[ ] | Object\[ ] }
389
389
390
- Uses the DNS protocol to resolve a IPv6 addresses (` AAAA ` records) for the
390
+ Uses the DNS protocol to resolve IPv6 addresses (` AAAA ` records) for the
391
391
` hostname ` . The ` addresses ` argument passed to the ` callback ` function
392
392
will contain an array of IPv6 addresses.
393
393
@@ -501,7 +501,7 @@ added: v0.9.12
501
501
* ` err ` {Error}
502
502
* ` addresses ` {Object\[ ] }
503
503
504
- Uses the DNS protocol to resolve regular expression based records (` NAPTR `
504
+ Uses the DNS protocol to resolve regular expression- based records (` NAPTR `
505
505
records) for the ` hostname ` . The ` addresses ` argument passed to the ` callback `
506
506
function will contain an array of objects with the following properties:
507
507
@@ -793,7 +793,7 @@ added: v15.3.0
793
793
-->
794
794
795
795
Cancel all outstanding DNS queries made by this resolver. The corresponding
796
- promises will be rejected with an error with code ` ECANCELLED ` .
796
+ promises will be rejected with an error with the code ` ECANCELLED ` .
797
797
798
798
### ` dnsPromises.getServers() `
799
799
@@ -857,7 +857,7 @@ such as no available file descriptors.
857
857
858
858
[ ` dnsPromises.lookup() ` ] [ ] does not necessarily have anything to do with the DNS
859
859
protocol. The implementation uses an operating system facility that can
860
- associate names with addresses, and vice versa. This implementation can have
860
+ associate names with addresses and vice versa. This implementation can have
861
861
subtle but important consequences on the behavior of any Node.js program. Please
862
862
take some time to consult the [ Implementation considerations section] [ ] before
863
863
using ` dnsPromises.lookup() ` .
@@ -1072,7 +1072,7 @@ added: v10.6.0
1072
1072
1073
1073
* ` hostname ` {string}
1074
1074
1075
- Uses the DNS protocol to resolve regular expression based records (` NAPTR `
1075
+ Uses the DNS protocol to resolve regular expression- based records (` NAPTR `
1076
1076
records) for the ` hostname ` . On success, the ` Promise ` is resolved with an array
1077
1077
of objects with the following properties:
1078
1078
@@ -1268,11 +1268,11 @@ earlier ones time out or result in some other error.
1268
1268
1269
1269
Each DNS query can return one of the following error codes:
1270
1270
1271
- * ` dns.NODATA ` : DNS server returned answer with no data.
1271
+ * ` dns.NODATA ` : DNS server returned an answer with no data.
1272
1272
* ` dns.FORMERR ` : DNS server claims query was misformatted.
1273
1273
* ` dns.SERVFAIL ` : DNS server returned general failure.
1274
1274
* ` dns.NOTFOUND ` : Domain name not found.
1275
- * ` dns.NOTIMP ` : DNS server does not implement requested operation.
1275
+ * ` dns.NOTIMP ` : DNS server does not implement the requested operation.
1276
1276
* ` dns.REFUSED ` : DNS server refused query.
1277
1277
* ` dns.BADQUERY ` : Misformatted DNS query.
1278
1278
* ` dns.BADNAME ` : Misformatted host name.
@@ -1293,7 +1293,7 @@ Each DNS query can return one of the following error codes:
1293
1293
* ` dns.ADDRGETNETWORKPARAMS ` : Could not find ` GetNetworkParams ` function.
1294
1294
* ` dns.CANCELLED ` : DNS query cancelled.
1295
1295
1296
- The above error codes are also exported by the ` dnsPromises ` API , e.g., ` dnsPromises.NODATA ` .
1296
+ The ` dnsPromises ` API also exports the above error codes , e.g., ` dnsPromises.NODATA ` .
1297
1297
1298
1298
## Implementation considerations
1299
1299
@@ -1329,7 +1329,7 @@ allow the default resolver, `dns.lookup()`, to be replaced.
1329
1329
1330
1330
These functions are implemented quite differently than [ ` dns.lookup() ` ] [ ] . They
1331
1331
do not use getaddrinfo(3) and they _ always_ perform a DNS query on the
1332
- network. This network communication is always done asynchronously, and does not
1332
+ network. This network communication is always done asynchronously and does not
1333
1333
use libuv's threadpool.
1334
1334
1335
1335
As a result, these functions cannot have the same negative impact on other
0 commit comments