getaddrinfo ENOTFOUND
The hostname doesn't exist in DNS
Seen in Node.js, npm, Linux and macOS resolvers
The resolver returned no address for the name.
Common causes
- A typo or a record that was deleted.
- An internal name used outside the network that defines it.
- The domain's registration expired or its nameservers are broken.
How to fix it
- Check the spelling and that the record exists publicly.
- Use the correct internal DNS (VPN) for private names.
- Check the domain's registration and nameservers.
Got a different message? Paste it into the error explainer.
Related errors
- getaddrinfo EAI_AGAIN · Temporary DNS failure
- 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