From 2ac5e9889aba461f5a54d320973d2574980d206b Mon Sep 17 00:00:00 2001 From: btea <2356281422@qq.com> Date: Wed, 26 Apr 2023 16:56:04 +0800 Subject: [PATCH] dns: expose getDefaultResultOrder PR-URL: https://github.com/nodejs/node/pull/46973 Fixes: https://github.com/nodejs/node/issues/46919 Reviewed-By: Matteo Collina Reviewed-By: Paolo Insogna --- doc/api/dns.md | 20 ++++++++++++++++ lib/dns.js | 2 ++ lib/internal/dns/promises.js | 2 ++ lib/internal/dns/utils.js | 5 ++++ .../test-dns-getDefaultResultOrder.js | 24 +++++++++++++++++++ 5 files changed, 53 insertions(+) create mode 100644 test/internet/test-dns-getDefaultResultOrder.js diff --git a/doc/api/dns.md b/doc/api/dns.md index 59a56c7d1c2aa8..2bb997bb0a2b4e 100644 --- a/doc/api/dns.md +++ b/doc/api/dns.md @@ -792,6 +792,18 @@ priority than [`--dns-result-order`][]. When using [worker threads][], [`dns.setDefaultResultOrder()`][] from the main thread won't affect the default dns orders in workers. +## `dns.getDefaultResultOrder()` + + + +Get the default value for `verbatim` in [`dns.lookup()`][] and +[`dnsPromises.lookup()`][]. The value could be: + +* `ipv4first`: for `verbatim` defaulting to `false`. +* `verbatim`: for `verbatim` defaulting to `true`. + ## `dns.setServers(servers)` + +Get the value of `dnsOrder`. + ### `dnsPromises.setServers(servers)`