🔐 Cloud Server Setup for Django Projects — Part 2

How to Check if Your Domain is Alive Before Deploying Django (and Save Hours of Debugging)

You’ve set up SSH. You can finally log into your Hetzner cloud server without typing that 37-character password every time. You’re feeling unstoppable. But wait — before even thinking of pushing Django to production, there’s one critical step that many devs overlook:

Is your domain even alive?

Let’s not waste time launching Gunicorn, configuring Nginx, or begging Certbot for SSL if your domain example.org doesn’t even point to your server.

This article is part of a hands-on series aimed at getting Django on the cloud, fast. It assumes basic knowledge and skips the theory — which I’ve covered in earlier, more in-depth articles.

Foto di Juan Cruz Mountford su Unsplash

🧪 Step 1: Is the DNS pointing somewhere?

Let’s start with the basics.

Open your terminal and run:

dig yourdomain.org +short

You should see something like:

88.99.123.456

If you see nothing, your domain isn’t pointing anywhere. You might also try:

nslookup yourdomain.org

If that fails too, chances are:

• The domain is not registered
• DNS settings are misconfigured
• Your registrar is on vacation since 2021

🧱 Step 2: Can you ping it?

Okay, suppose the DNS points somewhere. Let’s see if the domain responds:

ping yourdomain.org

If you get something like:

64 bytes from 88.99.123.456: icmp_seq=1 ttl=50 time=23.1 ms

You’re good. But if ping fails and you’re sure the server is up, you might be dealing with:

• ICMP blocked by the firewall
• Nginx not running
• Or, you guessed it — the server’s off

🌐 Step 3: Try connecting over HTTP

Now let’s go Sherlock with curl:

curl -I http://yourdomain.org

Useful responses:

• 200 OK: Server is up and ready
• 403 Forbidden: There’s a server, but it doesn’t like you (yet)
• 404 Not Found: Server’s alive, no content yet
• curl: Could not resolve host: DNS still isn’t pointing anywhere

🔭 Bonus: Use online tools for DNS sanity

Sometimes it’s easier to see what the rest of the world sees. Try:

• https://dnschecker.org/#A/yourdomain.org
• https://www.whatsmydns.net/#A/yourdomain.org

You’ll instantly know if your A record has propagated.

🧰 Your Domain Diagnostic Kit

# Check DNS resolution
dig yourdomain.org +short
# If dig fails
nslookup yourdomain.org
# Ping the domain
ping yourdomain.org
# Check if anything replies via HTTP
curl -I http://yourdomain.org
# Bonus: get domain info
whois yourdomain.org

✅ What you should see before proceeding with Django

🧠 Final thoughts

Before spending your evening cursing Django or doubting your reverse proxy skills, check if the domain you’re using is actually alive and pointing to your server.

Don’t be that dev who configures gunicorn, nginx, certbot, ufw, and systemd — only to find out they mistyped their domain name in the DNS dashboard.