Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: clarify what dns.setResolvers() affects #25570

Closed
wants to merge 1 commit into from

Conversation

sam-github
Copy link
Contributor

It does not affect dns.lookup().

cf. #25560

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • documentation is changed or added
  • commit message follows commit guidelines

@nodejs-github-bot nodejs-github-bot added dns Issues and PRs related to the dns subsystem. doc Issues and PRs related to the documentations. labels Jan 18, 2019
The `dns.setServers()` method affects only the methods of [`dns.Resolver`][]
that have equivalents as `dns.*()` APIs (and specifically *not*
[`dns.lookup()`][]). It must not be called while those methods are in progress.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: unneeded empty line?

doc/api/dns.md Outdated Show resolved Hide resolved
doc/api/dns.md Outdated Show resolved Hide resolved
@sam-github
Copy link
Contributor Author

Also, calling dns.setServers() should always be okay in recent versions of Node. Calling resolver.setServers() is also okay, but will yield an error if there are active queries.

I haven't changed this text, and don't want to get into it here. I'll add it to my todo list. Can you reference the PR that did this? It'll need YAML change markers. If you don't know, I'll track it down some time.

The structure of the docs are confusing. The Resolver class refers to the global docs, but it really be the other way around, the Resolver methods should be documented, and the globals should state that there is a global Resolver. An astute reader could guess that its implemented like this, but it isn't clearly stated.

@addaleax
Copy link
Member

I think the relevant PRs were #14891 (error out when active queries are on the resolver + change global default resolver when calling dns.setServers()) and, if you want, #14518 (adding the Resolver class).

It does not affect dns.lookup().
@sam-github
Copy link
Contributor Author

@sam-github
Copy link
Contributor Author

Landed in 0ce615c

@sam-github sam-github closed this Jan 25, 2019
@sam-github sam-github deleted the doc-clarify-setservers branch January 25, 2019 18:18
pull bot pushed a commit to zys-contrib/node that referenced this pull request Jan 25, 2019
It does not affect dns.lookup().

PR-URL: nodejs#25570
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
addaleax pushed a commit that referenced this pull request Jan 28, 2019
It does not affect dns.lookup().

PR-URL: #25570
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
@targos targos mentioned this pull request Jan 29, 2019
BethGriggs pushed a commit that referenced this pull request Apr 29, 2019
It does not affect dns.lookup().

PR-URL: #25570
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
@BethGriggs BethGriggs mentioned this pull request May 1, 2019
BethGriggs pushed a commit that referenced this pull request May 10, 2019
It does not affect dns.lookup().

PR-URL: #25570
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
MylesBorins pushed a commit that referenced this pull request May 16, 2019
It does not affect dns.lookup().

PR-URL: #25570
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dns Issues and PRs related to the dns subsystem. doc Issues and PRs related to the documentations.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants