From 7cc760f5627714b244b601370a906fd982fc2a25 Mon Sep 17 00:00:00 2001
From: Thomas Hunter II <tom@intrinsic.com>
Date: Fri, 15 Mar 2019 15:01:30 -0700
Subject: [PATCH] doc: note about DNS ANY queries / RFC 8482

PR-URL: https://github.com/nodejs/node/pull/26695
Reviewed-By: Gus Caplan <me@gus.host>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Bryan English <bryan@bryanenglish.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
---
 doc/api/dns.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/doc/api/dns.md b/doc/api/dns.md
index ca4ca4bad529a6..ecbd85160eb05b 100644
--- a/doc/api/dns.md
+++ b/doc/api/dns.md
@@ -367,6 +367,10 @@ Here is an example of the `ret` object passed to the callback:
     minttl: 60 } ]
 ```
 
+DNS server operators may choose not to respond to `ANY`
+queries. It may be better to call individual methods like [`dns.resolve4()`][],
+[`dns.resolveMx()`][], and so on. For more details, see [RFC 8482][].
+
 ## dns.resolveCname(hostname, callback)
 <!-- YAML
 added: v0.3.2
@@ -1142,5 +1146,6 @@ uses. For instance, _they do not use the configuration from `/etc/hosts`_.
 [`util.promisify()`]: util.html#util_util_promisify_original
 [DNS error codes]: #dns_error_codes
 [Implementation considerations section]: #dns_implementation_considerations
+[RFC 8482]: https://tools.ietf.org/html/rfc8482
 [rfc5952]: https://tools.ietf.org/html/rfc5952#section-6
 [supported `getaddrinfo` flags]: #dns_supported_getaddrinfo_flags