Fixing EAI_NONAME Error (DNS Resolution Failure)

Table of Contents: Introduction Check DNS Resolution Fix DNS in resolv.conf Fix in MySQL/MariaDB Fix in Nginx/Apache Flush DNS Cache Test with cURL/Wget Summary of Fixes

DNS Resolution Error EAI_NONAME troubleshooting

The EAI_NONAME error occurs when a system or application cannot resolve a hostname to an IP address. This is a DNS resolution failure that can happen in:

MySQL/MariaDB connections
Nginx/Apache configurations
cURL or Wget requests
Network or firewall settings

Check Your DNS Resolution

The error means that a domain name cannot be resolved.

Test Domain Resolution

Run:

nslookup yourdomain.com

dig yourdomain.com

If you get an IP address, DNS is working.
If it says "server can't find yourdomain.com: NXDOMAIN", DNS is broken.

Fix DNS in /etc/resolv.conf

If your server has wrong or missing DNS servers, update /etc/resolv.conf.

Open the file:

nano /etc/resolv.conf

Add Google or Cloudflare DNS:

nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 1.1.1.1

Save and restart networking:

systemctl restart networking

Now try running nslookup yourdomain.com again.

Fix EAI_NONAME in MySQL/MariaDB

If you see EAI_NONAME when connecting to MySQL, the database hostname might be incorrect.

Try Connecting with an IP Instead of Hostname

Instead of:

mysql -u user -h database.yourdomain.com -p

Try:

mysql -u user -h 127.0.0.1 -p

Add the Hostname to /etc/hosts

If the hostname must be used, add it to /etc/hosts:

nano /etc/hosts

Add:

127.0.0.1 database.yourdomain.com

Restart MySQL:

systemctl restart mysql

Fix EAI_NONAME in Nginx/Apache

If Nginx or Apache logs show EAI_NONAME, check virtual host settings.

Ensure the ServerName is Correct

For Nginx:

nano /etc/nginx/sites-available/default

server {
    listen 80;
    server_name yourdomain.com;
}

For Apache:

nano /etc/apache2/sites-available/000-default.conf

<VirtualHost *:80>
    ServerName yourdomain.com
</VirtualHost>

Restart:

systemctl restart nginx

systemctl restart apache2

Flush DNS Cache

If DNS was recently updated, clear the cache:

systemd-resolve --flush-caches

For macOS:

sudo killall -HUP mDNSResponder

Test with cURL or Wget

Check if external requests fail:

curl -I yourdomain.com

wget yourdomain.com

If it fails:

Try using an IP address
Check firewall settings (ufw status)

Summary of Fixes

Issue	Fix
Domain not resolving (EAI_NONAME)	Set correct DNS in `/etc/resolv.conf`
MySQL hostname not found	Use `127.0.0.1` or update `/etc/hosts`
Nginx/Apache virtual host error	Correct `server_name` or `ServerName`
Network issues	Flush DNS with `systemd-resolve --flush-caches`
cURL/Wget failing	Try using IP instead of hostname

Now EAI_NONAME should be resolved!

Fixing EAI_NONAME Error (DNS Resolution Failure)

Check Your DNS Resolution

Test Domain Resolution

Fix DNS in /etc/resolv.conf

Fix EAI_NONAME in MySQL/MariaDB

Try Connecting with an IP Instead of Hostname

Add the Hostname to /etc/hosts

Fix EAI_NONAME in Nginx/Apache

Ensure the ServerName is Correct

Flush DNS Cache

Test with cURL or Wget

Summary of Fixes

High-Availability Cloud VDS

Hosting

Cloud Solution

For You

VDS

Website Builders

Our services

Client Area

Select Currency

Fixing EAI_NONAME Error (DNS Resolution Failure)

Check Your DNS Resolution

Test Domain Resolution

Fix DNS in /etc/resolv.conf

Fix EAI_NONAME in MySQL/MariaDB

Try Connecting with an IP Instead of Hostname

Add the Hostname to /etc/hosts

Fix EAI_NONAME in Nginx/Apache

Ensure the ServerName is Correct

Flush DNS Cache

Test with cURL or Wget

Summary of Fixes

High-Availability Cloud VDS

Hosting

Cloud Solution

For You

VDS

Website Builders

Our services

Client Area

Выберите валюту