getaddrinfo EAI_AGAIN
Temporary DNS failure
Seen in Node.js, Docker containers, Linux (Temporary failure in name resolution)
The DNS lookup couldn't complete, usually because no resolver answered in time.
Common causes
- No network or no DNS resolver configured (common in containers and CI).
- The resolver is down or blocked by a firewall (UDP/TCP 53).
- The domain's authoritative servers are failing (SERVFAIL).
How to fix it
- Check the machine's resolver settings and network.
- Allow outbound DNS or set a working resolver.
- Check the domain answers correctly from public resolvers.
Got a different message? Paste it into the error explainer.
Related errors
- getaddrinfo ENOTFOUND · The hostname doesn't exist in DNS
- ENETUNREACH · Network is unreachable
- ECONNREFUSED · Connection refused
- ETIMEDOUT · Connection timed out
- ECONNRESET · Connection reset by peer
- EHOSTUNREACH · No route to host
- Broken pipe · Wrote to a connection or pipe that was already closed
- Software caused connection abort · Your own system aborted the connection
- WSAETIMEDOUT (10060) · Windows connection attempt timed out
- WSAECONNREFUSED (10061) · Windows connection refused
- Request timed out. · Ping got no reply
- Destination host unreachable. · No path to the host could be found