WP-Admin Extremely Slow and “Could not resolve host: api.wordpress.org”: Quick DNS Fix

Common Symptoms

• WP-Admin loads very slowly despite low CPU and RAM usage.
• WordPress News section does not load.
• Theme and plugin updates fail to fetch.
• cURL error 6 or Could not resolve host appears.
• Site Health reports loopback or REST API errors.

All of these indicate that WordPress cannot properly connect to external services, especially api.wordpress.org.

Why DNS Can Make WP-Admin Slow

Whenever WordPress needs to communicate with external APIs (update checks, news feeds, webhooks, third-party services), the server must:

Application → DNS lookup → Get IP address → Establish HTTPS connection

If DNS resolution fails or is delayed, every outgoing request waits until timeout. This makes WP-Admin appear frozen or extremely slow, even though Nginx/Apache and PHP are functioning normally.

How to Quickly Confirm It’s a DNS Issue

SSH into your server and run:

curl https://api.wordpress.org

If you see:

curl: (6) Could not resolve host: api.wordpress.org

This confirms the server cannot resolve the domain name — a DNS problem.

Check your current DNS configuration:

cat /etc/resolv.conf

If it shows a VPS provider’s nameserver (for example, 108.61.10.10) and you suspect instability, you can temporarily switch to a public DNS resolver to test.

Temporary Fix (No Permanent Configuration Required)

Edit the resolver file:

sudo nano /etc/resolv.conf

Replace its contents with:

nameserver 1.1.1.1
nameserver 8.8.8.8

Save the file and test again:

curl https://api.wordpress.org

If it immediately returns JSON data and WP-Admin becomes responsive again, the original DNS resolver was the problem.

Note: This is a temporary solution. On many VPS setups, /etc/resolv.conf may be overwritten after a reboot. However, for quickly restoring WP-Admin performance and eliminating cURL resolution errors, this is the fastest and most effective method.

Conclusion

When WP-Admin becomes unusually slow or shows “Could not resolve host” errors, do not immediately blame WordPress, plugins, or server resources. Check DNS first. A simple change in /etc/resolv.conf can restore full functionality within seconds.

In production environments, a stable DNS resolver is just as critical as your web server or PHP configuration. A small configuration file can determine whether your WordPress site runs smoothly or constantly times out.