The "EAI_NONAME - Neither nodename nor servname provided, or not known" error in FileZilla FTP Client occurs when the hostname cannot be resolved to an IP address. This is a DNS issue, meaning your computer is unable to locate the FTP server[citation:1][citation:8].
In this guide, we will go through step-by-step troubleshooting to resolve this error, ensuring a smooth FTP connection.
The error is fundamentally a name resolution error[citation:1]. Your system's DNS (Domain Name System) cannot convert the provided hostname (like ftp.yourdomain.com) into a numerical IP address that FileZilla can connect to. Common specific causes include:
Always start with the simplest check. Confirm you are using the exact FTP hostname provided by your web host. This is often different from your website's main address[citation:4].
ftp.yourdomain.com or a dedicated server address like server123.hosting.com.Before changing settings in FileZilla, test if your computer can resolve the hostname at all.
nslookup ftp.yourdomain.com
Or use the ping command to see if it returns an IP address[citation:7][citation:9].
ping ftp.yourdomain.com
dig ftp.yourdomain.com
or
host ftp.yourdomain.com
Expected Result: You should see an IP address in the output.
Error Result: Messages like "server can't find..." or "Host not found" confirm a DNS failure[citation:1].
This is the most effective and immediate workaround[citation:1][citation:4][citation:9]. Since the problem is DNS, bypass it entirely by connecting directly via the server's IP address.
ping command as shown above.ftp.yourdomain.com) with the IP address (e.g., 192.168.1.10).Why this works: If the connection succeeds with the IP but fails with the hostname, you have definitively confirmed the issue is with DNS resolution and not with your network or the FTP server itself[citation:1].
If you use Cloudflare or another CDN, it may be causing the issue. These services often proxy web traffic but can interfere with FTP.
The solution is to ensure your FTP subdomain (e.g., ftp.yourdomain.com) is not proxied by the CDN[citation:4][citation:6].
ftp (or your FTP hostname).| Issue | Primary Fix | How to Confirm |
|---|---|---|
| Misspelled or wrong hostname | Use the exact hostname from your host. | Check spelling; review hosting panel. |
| General DNS failure | Use the server's IP address in FileZilla[citation:1][citation:4][citation:9]. | nslookup or ping fails. |
| CDN/Proxy (e.g., Cloudflare) blocking | Set FTP subdomain to "DNS only" (grey cloud)[citation:4][citation:6]. | IP works, hostname doesn't; you use a CDN. |
| DNS propagation delay | Wait 24-48 hours or use IP address. | Recent DNS changes; check with online DNS checker[citation:4]. |
By systematically following these steps, you should be able to resolve the EAI_NONAME error and connect successfully. The most reliable long-term solution for a static server is often to simply use the IP address in FileZilla's Site Manager[citation:4].