dns: Resolver timeout seemingly doubled upon tries=1

### Version v26.7.0 ### Platform ```text `Linux 58e331aa718d 7.1.4-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 18 Jul 2026 17:30:57 +0000 x86_64 GNU/Linux` (a Docker container of `node:26.7.0-trixie-slim`) Also reproduces with: - `node-v27.0.0-nightly20260816d099639740-linux-x64` (fetched https://nodejs.org/download/nightly/v27.0.0-nightly20260816d099639740/) with `Linux REDACTED 7.1.4-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 18 Jul 2026 17:30:57 +0000 x86_64 GNU/Linux` - `v26.7.0` with `Linux REDACTED 7.1.4-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 18 Jul 2026 17:30:57 +0000 x86_64 GNU/Linux` ``` ### Subsystem dns ### What steps will reproduce the bug? 1. Initialize a Resolver with config `{ timeout: 1000, tries: 1, maxTimeout: 1000 }`. 2. Configure your local network to block (drop) DNS traffic, or use a server netloc that won't respond (e.g. `resolver.setServers(["1.1.1.1:9999"])`) so that any query shall timeout. 3. Make a query (e.g. resolve4). Here's a sample script: ```javascript const { Resolver } = require("dns"); const { promisify } = require("util"); (async () => { const resolver = new Resolver({ timeout: 1000, tries: 1, maxTimeout: 1000 }); resolver.setServers(["1.1.1.1:9999"]); // expect ETIMEOUT here await promisify(resolver.resolve4.bind(resolver))("example.com"); })(); ``` ### How often does it reproduce? Is there a required condition? Every time. No required condition other than what's stated above. ### What is the expected behavior? Why is that the expected behavior? An `ETIMEOUT` shall raise after 1 second since it is configured so (both timeouts being 1000 and tries=1). ### What do you see instead? It takes 2 seconds to throw the timeout exception. E.g.: ``` $ time node a.js node:internal/dns/callback_resolver:45 this.callback(new DNSException(err, this.bindingName, this.hostname)); ^ Error: queryA ETIMEOUT example.com at QueryReqWrap.onresolve [as oncomplete] (node:internal/dns/callback_resolver:45:19) { errno: undefined, code…