Skip to content

Commit 9590d81

Browse files
Trottcodebytere
authored andcommitted
doc: revise text in dns module documentation introduction
PR-URL: #33986 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]>
1 parent a24b8df commit 9590d81

File tree

1 file changed

+4
-6
lines changed

1 file changed

+4
-6
lines changed

doc/api/dns.md

+4-6
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,8 @@ addresses of host names.
1010
Although named for the [Domain Name System (DNS)][], it does not always use the
1111
DNS protocol for lookups. [`dns.lookup()`][] uses the operating system
1212
facilities to perform name resolution. It may not need to perform any network
13-
communication. Developers looking to perform name resolution in the same way
14-
that other applications on the same operating system behave should use
15-
[`dns.lookup()`][].
13+
communication. To perform name resolution the way other applications on the same
14+
system do, use [`dns.lookup()`][].
1615

1716
```js
1817
const dns = require('dns');
@@ -26,9 +25,8 @@ dns.lookup('example.org', (err, address, family) => {
2625
All other functions in the `dns` module connect to an actual DNS server to
2726
perform name resolution. They will always use the network to perform DNS
2827
queries. These functions do not use the same set of configuration files used by
29-
[`dns.lookup()`][] (e.g. `/etc/hosts`). These functions should be used by
30-
developers who do not want to use the underlying operating system's
31-
facilities for name resolution, and instead want to always perform DNS queries.
28+
[`dns.lookup()`][] (e.g. `/etc/hosts`). Use these functions to always perform
29+
DNS queries, bypassing other name-resolution facilities.
3230

3331
```js
3432
const dns = require('dns');

0 commit comments

Comments
 (0)