Put A Subdomain On A Different Server

Understanding Subdomain DNS Fundamentals

A subdomain is a prefix that exists under a main domain name. For example, in "api.example.com," "api" is the subdomain of example.com. Subdomains help organize and route traffic to specific services, such as API endpoints, developer portals, and staging environments.

DNS (Domain Name System) records are what make it possible for domain names to point you to specific web servers. Without the right records, traffic will get lost in the shuffle—DNS queries may fail, resulting in errors or routing to the wrong place entirely.

The Role of DNS in Subdomain Routing

When a user types "api.yourdomain.com" into their browser, the DNS system performs a lookup to determine where that request should be sent:

1. Recursive DNS Query: The user's device contacts a DNS resolver to find the IP address
2. Root Server Lookup: The resolver queries root servers to find the TLD (.com) nameservers
3. TLD Nameserver Query: The resolver queries the TLD nameservers for your domain's authoritative nameservers
4. Authoritative Nameserver Query: The resolver queries your domain's nameservers for the specific subdomain record
5. IP Resolution: The DNS record returns the IP address of your target server

Why Host Subdomains on Different Servers?

• Isolation and Security: Running your main website on one server and your API on another creates a security boundary
• Scalability: Different services often have different scaling requirements
• Technology Flexibility: Your main site might run on PHP/Apache while your API uses Node.js
• Reliability: Problems on one server don't automatically take down your entire online presence

For applications requiring scalable infrastructure design, proper subdomain routing is essential for maintaining clean architectural boundaries between services.

Step-by-Step: Configuring Your DNS Records

Step 1: Gather Your Target Server Information

For A records, you'll need:

• The static IPv4 address of your server (e.g., 203.0.113.42)
• Optionally, an IPv6 address if using dual-stack networking

For CNAME records, you'll need:

• The canonical domain name you'll be pointing to (e.g., my-api.herokuapp.com)

Server preparation checklist:

• Web server (nginx, Apache) is installed and configured
• Firewall rules allow incoming traffic on ports 80 (HTTP) and 443 (HTTPS)
• SSL certificate is installed
• Server responds correctly when accessed by IP address

Step 2: Create the Subdomain Record

For an A record:

1. Select "Add New Record"
2. Choose "A" as the record type
3. Enter your subdomain name (e.g., "api" for api.yourdomain.com)
4. Enter the target IPv4 address
5. Set TTL to 3600 seconds (1 hour)
6. Save the record

For a CNAME record:

1. Select "Add New Record"
2. Choose "CNAME" as the record type
3. Enter your subdomain name
4. Enter the canonical domain name without protocol
5. Set TTL to 3600 seconds
6. Save the record

Step 3: Configure Your Target Server

Nginx example:

server {
    listen 80;
    server_name api.yourdomain.com;
    root /var/www/api;
    index index.html;
    location / {
        try_files $uri $uri/ =404;
    }
}

Apache example:

<VirtualHost *:80>
    ServerName api.yourdomain.com
    DocumentRoot /var/www/api
</VirtualHost>

Step 4: Configure SSL/TLS

Use Certbot to obtain free Let's Encrypt certificates:

sudo certbot --nginx -d api.yourdomain.com

Proper server configuration is critical for both web development projects and API services. Ensuring your web server correctly handles subdomain requests prevents common routing issues that can impact user experience and search engine visibility.

Implementing AI automation for infrastructure management can help automate SSL certificate renewal and monitoring across multiple subdomains, reducing manual overhead and potential security gaps.

Sources

1. No-IP: How to Configure DNS Records for Subdomains
2. Namecheap: How to Create a CNAME Record