From 4dd0b7a42aca04b4ec6c2eaf96141f79c3651e5e Mon Sep 17 00:00:00 2001 From: Vse Mozhet Byt Date: Thu, 26 Jan 2017 18:07:54 +0200 Subject: [PATCH] doc: fix confusing example in dns.md Currently, the example throws 'Error: getHostByAddr ENOTFOUND' The previous example is edited for consistency. --- doc/api/dns.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/api/dns.md b/doc/api/dns.md index e253039b687ef0..39b72202b05550 100644 --- a/doc/api/dns.md +++ b/doc/api/dns.md @@ -10,12 +10,12 @@ This category contains only one function: [`dns.lookup()`][]. **Developers looking to perform name resolution in the same way that other applications on the same operating system behave should use [`dns.lookup()`][].** -For example, looking up `nodejs.org`. +For example, looking up `iana.org`. ```js const dns = require('dns'); -dns.lookup('nodejs.org', (err, addresses, family) => { +dns.lookup('iana.org', (err, addresses, family) => { console.log('addresses:', addresses); }); ``` @@ -28,13 +28,13 @@ functions do not use the same set of configuration files used by developers who do not want to use the underlying operating system's facilities for name resolution, and instead want to _always_ perform DNS queries. -Below is an example that resolves `'nodejs.org'` then reverse resolves the IP +Below is an example that resolves `'archive.org'` then reverse resolves the IP addresses that are returned. ```js const dns = require('dns'); -dns.resolve4('nodejs.org', (err, addresses) => { +dns.resolve4('archive.org', (err, addresses) => { if (err) throw err; console.log(`addresses: ${JSON.stringify(addresses)}`);