Puppeteer: net::ERR_NAME_NOT_RESOLVED at <url>

page.goto() rejected because Chrome could not resolve the hostname to an IP address. Puppeteer passes Chrome's network error text through and appends at plus the URL. The same pattern covers related network failures you may see from the same call: net::ERR_CONNECTION_REFUSED (nothing listening on that port), net::ERR_CONNECTION_TIMED_OUT, and net::ERR_CERT_AUTHORITY_INVALID for TLS problems.

Because DNS failed, no request was sent and no response exists. The error arrives immediately rather than after the navigation timeout, and retrying the same URL from the same machine will keep failing until the name or the resolver changes.

What is not wrong: your selectors, waits and page logic. The site may also be perfectly healthy for everyone else; the problem is the name you used or the network the browser sits on.

try {
  await page.goto(url, { waitUntil: 'domcontentloaded' });
} catch (err) {
  if (/net::ERR_NAME_NOT_RESOLVED/.test(err.message)) {
    console.warn(`DNS failed for ${url}`);
  } else {
    throw err;
  }
}

Validate URLs and environment variables at startup, and run browser jobs on a network that can resolve every host they visit. In crawlers, classify net:: errors separately from timeouts so dead domains are skipped rather than retried, and record the failing hostname so configuration mistakes stand out in logs.