dns: error ECONNREFUSED when using resolveSrv

[chasyumen]

Version

20.20.0, 22.22.0, 24.13.0, 25.3.0

Platform

Microsoft Windows NT 10.0.26200.0 x64

Subsystem

dns

What steps will reproduce the bug?

import dnsPromises from "dns/promises";
(async () => {
  try {
    console.log(await dnsPromises.resolveSrv("example.com")); // any string value triggers an error
  } catch (e) { console.error(e); }
})();

How often does it reproduce? Is there a required condition?

Errored every time when I use resolveSrv on following broken versions on Windows. (Worked OK on linux, not tested on macOS)

• 20.20.0
• 22.22.0
• 24.13.0
• 25.3.0

Works fine on

• 20.19.6
• 22.21.1
• 24.12.0
• 25.2.1

What is the expected behavior? Why is that the expected behavior?

Error: querySrv ENODATA
    at QueryReqWrap.onresolve [as oncomplete] (node:internal/dns/promises:294:17) {
  errno: undefined,
  code: 'ENODATA',
  syscall: 'querySrv'
}

(in production when I used 22.21.1)

What do you see instead?

Error: querySrv ECONNREFUSED example.com
    at QueryReqWrap.onresolve [as oncomplete] (node:internal/dns/promises:294:17) {
  errno: undefined,
  code: 'ECONNREFUSED',
  syscall: 'querySrv',
  hostname: 'example.com'
}

(used 22.22.0)

Additional information

No response

[Cherry]

This also impacts the resolveMx function:

require('dns').resolveMx('google.com', console.log)

Fails on Windows with the same ECONNREFUSED, Nodejs 24.13.0, but works fine on 24.12.0

[targos]

@nodejs/dns This might be related to c-ares/c-ares#1056