WhatBrokeToday
GTA 6FAQ
Bun

Bun node:dns resolve6 Rejects with ENOTFOUND Instead of ENODATA

medium

Is it fixed? Not yet.

Ongoing since Nov 12, 17:16 UTC. First reported Nov 12, 17:16 UTC.

What happened

Bun's node:dns implementation incorrectly rejects resolve6 calls with ENOTFOUND instead of ENODATA when a queried name lacks AAAA records, alongside an existing issue where resolveTxt splits multi-string TXT records. These bugs affect versions 1.4.2 and 1.4.4 across Linux, macOS, and Windows platforms.

What caused it?

Under active investigation. No report has identified a root cause yet.

No verified workaround yet

None of the linked reports describe a mitigation. This page updates when one appears.

Official fix

Timeline

  1. Investigating(current)
  2. Workaround available(upcoming)
  3. Resolved(upcoming)
  1. First report on GitHub issue

    node:dns resolveTxt splits one multi-string TXT record into separate records (still on 1.4.4)

    Source

Evidence

2 reports · 2 GitHubShow
  1. [1]
    GitHub First report
    node:dns resolveTxt splits one multi-string TXT record into separate records (still on 1.4.4)(opens GitHub issue in a new tab)

    What version of Bun is running? 1.4.4+38afee6c8 (also seen on 1.4.2) What platform is your computer? macOS arm64 (also seen on Linux x64) What steps can reproduce the bug? 20251104._domainkey.google.com is one TXT record made of two character-strings, 255 and 155 bytes long: $ dig +short TXT 20251104._domainkey.google.com "v=DKIM1; k=rsa; p=MIIBIjANBgkq...K8f8" "wQoKmzK+ft0+...IDAQAB" import dns from "node:dns"; import { Resolver } from "node:dns/promises"; const name =…

    by alex28042 0upvotes 0comments

  2. [2]
    GitHub
    node:dns: resolve6 rejects with ENOTFOUND instead of ENODATA when a name has no AAAA records(opens GitHub issue in a new tab)

    What version of Bun is running? 1.4.4 (also 1.4.2) What platform is your computer? Linux x64 (Debian 13) and Windows 11 x64 What steps can reproduce the bug? // repro.mjs import { Resolver } from "node:dns/promises"; import dns from "node:dns"; const name = "github.com"; // has A records, no AAAA records const r = new Resolver({ timeout: 1000, tries: 1 }); for (const [label, fn] of [ ["resolver.resolve6", () => r.resolve6(name)], ["dns.promises.resolve6", () => dns.promises.resolve6(name)], ])…

    by rhuanbarreto 0upvotes 1comments92% match

FAQ

What happened in the Bun issue?

Bun's node:dns implementation incorrectly rejects resolve6 calls with ENOTFOUND instead of ENODATA when a queried name lacks AAAA records, alongside an existing issue where resolveTxt splits multi-string TXT records. These bugs affect versions 1.4.2 and 1.4.4 across Linux, macOS, and Windows platforms.

What is affected by the Bun issue?

Bun (versions: 1.4.2, 1.4.4).

When did the Bun issue start and end?

It started Nov 12, 17:16 UTC and is still ongoing (6 d 11 h so far). This page updates as it develops.

How do I get alerts for Bun?

Subscribe to the Bun RSS feed for every new Bun incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Bun is down. Bun feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 2 reports from 1 independent source.