Home
last modified time | relevance | path

Searched refs:setDefaultResultOrder (Results 1 – 5 of 5) sorted by relevance

/third_party/node/test/parallel/
Dtest-dns-set-default-order.js32 assert.throws(() => dns.setDefaultResultOrder('my_order'), {
35 assert.throws(() => dns.promises.setDefaultResultOrder('my_order'), {
38 assert.throws(() => dns.setDefaultResultOrder(4), {
41 assert.throws(() => dns.promises.setDefaultResultOrder(4), {
54 dns.setDefaultResultOrder('verbatim');
64 dns.setDefaultResultOrder('ipv4first');
74 dns.promises.setDefaultResultOrder('verbatim');
84 dns.promises.setDefaultResultOrder('ipv4first');
/third_party/node/lib/
Ddns.js45 setDefaultResultOrder,
292 setDefaultResultOrder, property
337 promises.setDefaultResultOrder = setDefaultResultOrder;
/third_party/node/lib/internal/dns/
Dutils.js210 function setDefaultResultOrder(value) { function
225 setDefaultResultOrder, property
/third_party/node/doc/api/
Ddns.md193 configurable using [`dns.setDefaultResultOrder()`][] or
636 ## `dns.setDefaultResultOrder(order)`
648 The default is `ipv4first` and [`dns.setDefaultResultOrder()`][] have higher
650 [`dns.setDefaultResultOrder()`][] from the main thread won't affect the default
799 configurable using [`dns.setDefaultResultOrder()`][] or
1154 ### `dnsPromises.setDefaultResultOrder(order)`
1166 The default is `ipv4first` and [`dnsPromises.setDefaultResultOrder()`][] have
1168 [`dnsPromises.setDefaultResultOrder()`][] from the main thread won't affect the
1300 [`dns.setDefaultResultOrder()`]: #dns_dns_setdefaultresultorder_order
1318 [`dnsPromises.setDefaultResultOrder()`]: #dns_dnspromises_setdefaultresultorder_order
Dcli.md196 The default is `ipv4first` and [`dns.setDefaultResultOrder()`][] have higher
1696 [`dns.setDefaultResultOrder()`]: dns.md#dns_dns_setdefaultresultorder_order