Website down: DNS or hosting first?

[NiceNIC_COM]

When a website suddenly stops loading, the cause is not always the hosting server.

It could be DNS resolution, nameserver settings, DNS records, CDN configuration, SSL, browser cache, or the web server itself. In website support cases, checking the domain and DNS setup early can often save time.

For people managing websites, client projects, or hosting customers, what is your normal first check?

Do you start with DNS and nameservers, or go straight to the hosting server, logs, and uptime monitoring?

 

[Charlese]

Normally, i first check if DNS resolution is working properly, then check the server, and finally check the logs.

 

[AlexTechie]

Start with DNS first, If DNS is working correctly then check the hosting server. DNS issues are quick to rule out before troubleshooting hosting issue.

 

[bbvideo]

In my experience with production sites, once the domain and DNS are initialised and fully propagated, DNS issues are extremely rare unless someone mistakenly edited records or nameservers.

If an already running, stable site suddenly stops loading or becomes sluggish, my immediate go-to is always the hosting server itself.

My first step is SSHing into the server and checking resource usage in real-time using CLI tools like htop or top. Most sudden slowdowns or crashes are caused by resource exhaustion—usually a traffic spike, a runaway background process, or an active DDoS/bot attack choking CPU and RAM. Checking real-time server metrics and error logs gets to the root cause way faster than re-checking DNS.