dns.resolveSoa returns EBADRESP if hostname has a CNAME record

<!-- Thank you for reporting an issue. This issue tracker is for bugs and issues found within Node.js core. If you require more general support please file an issue on our help repo. https://github.com/nodejs/help Please fill in as much of the template below as you're able. Version: output of `node -v` Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows) Subsystem: if known, please specify affected core module name --> * **Version(s)**: v12.16.3 / v12.18.3 / v12.18.0 * **Platform**: Windows / Windows Subsystem for Linux (Debian) / Red Hat Enterprise Linux Server release 7.8 * **Subsystem**: DNS ### What steps will reproduce the bug? ``` const dns = require('dns'); const resolver = new dns.promises.Resolver(); // ************************************************************** async function test(hostname) { let data = ''; console.log('hostname:', hostname); try { data = await resolver.resolveCname(hostname); console.log('CNAME result:', data); } catch (error) { console.log('CNAME result:', error.message); } try { data = await resolver.resolveSoa(hostname); console.log('SOA result:', JSON.stringify(data)); } catch (error) { console.log('SOA result:', error.message); } console.log(); } // ************************************************************** (async function main() { await test('support.microsoft.com'); })(); ``` ### Actual Results hostname: support.microsoft.com CNAME result: [ 'ev.support.microsoft.com.edgekey.net' ] SOA result: querySoa EBADRESP support.microsoft.com ### Expected Results hostname: support.microsoft.com CNAME result: [ 'ev.support.microsoft.com.edgekey.net' ] SOA result: querySoa ENODATA support.microsoft.com ### Additional information This seems to happen for any hostname with a CNAME record. Another example: hostname: store.gocomics.com CNAME result: [ 'gocomicsstore.wpengine.com' ] SOA result: querySoa EBADRESP store.gocomics.com I would expect to get an 'ENODATA' instead o…