How to Configure a Domain for Your Website

Buying a domain name (like yourbrand.com) is only the first step. To make your website accessible to visitors worldwide, you must link that human-friendly domain name to your RivinCloud VPS public IP address through the Domain Name System (DNS).

In this guide, we cover the exact steps required to point your domain to your server, manage DNS records, and verify propagation.

1. Choosing Where to Manage Your DNS

You can manage your domain's DNS records in one of two places:

1. Your Domain Registrar (e.g., Namecheap, GoDaddy, Google Domains / Squarespace).
2. A Dedicated DNS Provider / CDN (e.g., Cloudflare - recommended for DDoS mitigation and fast DNS propagation).

2. Step-by-Step DNS Record Configuration

To point your website to your RivinCloud VPS (let's assume your server IP is 192.0.2.50), add the following DNS records in your DNS management dashboard:

1. Root Domain (@) A Record

Maps your base domain (yourdomain.com) to your server's IPv4 address:

• Type: A
• Name / Host: @ (or leave blank depending on registrar)
• IPv4 Address / Value: 192.0.2.50
• TTL: Auto or 300 seconds (5 minutes)

2. Subdomain (www) Record

Ensures visitors typing www.yourdomain.com reach the same server:

• Type: CNAME (or A record)
• Name / Host: www
• Target / Value: yourdomain.com (or your IP 192.0.2.50)
• TTL: Auto or 300 seconds

3. IPv6 AAAA Record (Optional but Recommended)

If your RivinCloud VPS has an IPv6 address:

• Type: AAAA
• Name / Host: @
• IPv6 Address: 2001:db8::1

3. Verifying DNS Propagation from Your Terminal

DNS changes do not happen instantly worldwide; they take time to propagate across ISP resolvers. You can check the status of your domain using command-line DNS tools:

Using dig

dig +short A yourdomain.com

(If configured correctly, this outputs your server's public IP address).

Checking with nslookup

nslookup yourdomain.com

Checking Globally via Online Tools

You can also verify propagation across global geographic checkpoints using online services like dnschecker.org.

4. Connecting Domain in Your Web Server

Once DNS resolves to your IP, configure your web server (Nginx or Apache) to listen for the domain name:

# In /etc/nginx/sites-available/yourdomain.com
server {
    listen 80;
    server_name yourdomain.com www.yourdomain.com;
    root /var/www/yourdomain.com/html;
}

Then reload Nginx:

sudo nginx -t && sudo systemctl reload nginx

Common Mistakes

• Entering http:// in DNS records: DNS values only accept raw IP addresses (192.0.2.50) or hostnames (yourdomain.com), never URL protocols or paths.
• Setting excessively high TTL before migrating: If TTL is set to 86400 (24 hours), DNS changes will take a full day to reflect for existing visitors. Lower TTL to 300 seconds before making changes.

Troubleshooting

• Site loads old host or parking page: Your local DNS cache may be stale. Flush your local DNS cache:
  • Windows: ipconfig /flushdns
  • macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Best Practices

• Always configure both apex (@) and www records.
• Use Cloudflare for fast DNS resolution, free SSL, and proxy DDoS protection.

Frequently Asked Questions

What does TTL mean?

TTL (Time To Live) is the duration (in seconds) that intermediate DNS resolvers are allowed to cache a DNS answer before querying authoritative nameservers again.

Conclusion

Configuring a domain name is straightforward once you understand A and CNAME records. Point your domain to your RivinCloud VPS today and launch your project!