Link Namecheap Domain to DigitalOcean Droplet with Nginx in 9 Steps

Setting up a domain and a server can feel overwhelming, but connecting the two doesn’t have to be complicated. You’ve purchased a domain from Namecheap and spun up a Virtual Private Server (VPS) on DigitalOcean. The next logical step is making sure your domain points to your server and your website loads when visitors arrive. Unlike shared hosting platforms, DigitalOcean doesn’t automate this connection for you, so manual configuration is required.

This guide walks you through the entire process in clear, beginner-friendly steps. By the end, your domain will resolve to your DigitalOcean Droplet, Nginx will serve your site, and HTTPS will be enabled to ensure secure connections.

How the Domain-to-Server Connection Works

Before diving into settings, it’s helpful to visualize the flow. Think of your domain as a human-readable address—like a street address for your business. Your DigitalOcean Droplet is the physical location—your server where files are stored. Domain Name System (DNS) acts as the postal service, translating your domain name into the server’s IP address. Nginx, the web server software, then receives the request and delivers your website content to the visitor’s browser.

Here’s the full path:

Namecheap Domain → DNS points to DigitalOcean IP → DigitalOcean Droplet → Nginx Web Server → Your Website

Step 1: Create a DigitalOcean Droplet

Start by creating a Droplet in your DigitalOcean account. For testing or lightweight projects, a basic configuration is sufficient:

• Ubuntu 22.04 LTS (Long-Term Support)
• Basic Droplet with 1 GB RAM

Once created, DigitalOcean will assign a public IP address to your Droplet. It will look similar to:

159.89.xxx.xxx

Copy this IP address and keep it secure. You’ll need it in the next steps to configure DNS and server access.

Step 2: Configure DNS Records in Namecheap

Now, log in to your Namecheap account and navigate to your domain’s management panel. Go to Domain List → Manage → Advanced DNS. Here, you’ll add DNS records to point your domain to your DigitalOcean server.

You have two main options. The first and simplest is using A Records.

Option A: Using A Records (Recommended for Beginners)

Add these two A records:

• Type: A Record, Host: @, Value: Your DigitalOcean IP
• Type: A Record, Host: www, Value: Your DigitalOcean IP

For example, if your IP is 159.89.xxx.xxx:

Type    Host   Value
A Record @      159.89.xxx.xxx
A Record www    159.89.xxx.xxx

This setup ensures both example.com and www.example.com point to your server. The TTL (Time to Live) can remain at the default value.

Option B: Using DigitalOcean Nameservers (For Advanced Setups)

Alternatively, you can manage DNS entirely from DigitalOcean. In your DigitalOcean dashboard, go to Networking → Domains → Add Domain and enter your domain. DigitalOcean will provide nameservers such as:

ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

Copy these nameservers and return to Namecheap. Go to Domain → Manage → Nameservers → Custom DNS, paste the DigitalOcean nameservers, and save.

This method is ideal if you plan to use multiple subdomains like api.example.com, blog.example.com, or app.example.com.

For most beginners, Option A (A Records) is the best starting point.

Step 3: Wait for DNS Propagation

After saving your DNS changes, propagation begins. While some changes take effect within minutes, others may take several hours. In most cases, expect the following timeline:

• 5 minutes to 1 hour: Common for small changes
• Up to 24 hours: Possible in rare cases

Use a DNS lookup tool like DNS Checker to verify whether your domain is correctly pointing to your server IP. Avoid making additional changes immediately, as DNS may still be updating in the background.

Step 4: Connect to Your Server via SSH

With DNS configured, it’s time to access your server. Open a terminal on macOS or Linux, or use PowerShell or PuTTY on Windows. Connect using SSH with the command:

ssh root@YOUR_SERVER_IP

For example:

ssh root@159.89.xxx.xxx

Upon first connection, your terminal may prompt for confirmation. Type yes and press Enter. Then enter your password or use your SSH key, depending on how you set up the Droplet.

Step 5: Install and Configure Nginx

Once logged in, update your package list and install Nginx:

sudo apt update
sudo apt install nginx -y

Check Nginx status to confirm it’s running:

sudo systemctl status nginx

If active, visiting your server’s IP in a browser should display the default Nginx welcome page. This confirms your web server is operational.

Step 6: Secure Your Server with a Firewall

Ubuntu servers often use ufw (Uncomplicated Firewall) for traffic management. Allow essential services:

sudo ufw allow 'Nginx Full'
sudo ufw allow OpenSSH

Enable the firewall:

sudo ufw enable

Verify the rules:

sudo ufw status

You should see HTTP, HTTPS, and SSH traffic permitted.

Step 7: Set Up Your Website Files

Create a directory for your website and a simple test page:

sudo mkdir -p /var/www/myproject

Use a text editor to create an index.html file:

sudo nano /var/www/myproject/index.html

Add this basic content:

<h1>Hello from DigitalOcean</h1>

Save and exit with CTRL + X, then Y, then Enter.

Step 8: Create an Nginx Server Block

Nginx uses server blocks to manage different domains or applications. Create a new configuration file:

sudo nano /etc/nginx/sites-available/myproject

Paste the following template, replacing example.com with your actual domain:

server {
    listen 80;
    server_name example.com www.example.com;
    root /var/www/myproject;
    index index.html;

    location / {
        try_files $uri $uri/ =404;
    }
}

This configuration tells Nginx to serve files from /var/www/myproject when someone visits your domain.

Step 9: Activate the Configuration and Test

Nginx stores available site configurations in /etc/nginx/sites-available/ but only uses those linked in /etc/nginx/sites-enabled/. Create a symbolic link:

sudo ln -s /etc/nginx/sites-available/myproject /etc/nginx/sites-enabled/

Test the configuration for errors:

sudo nginx -t

If successful, reload Nginx:

sudo systemctl reload nginx

Now, visit your domain in a browser. You should see your test page, confirming everything is working. The final step is securing your site with HTTPS using Let’s Encrypt, which we’ll cover in a follow-up guide.

With this setup complete, your domain is live, your server is responding, and your website is ready for visitors.