ServerTrack.io

DNS Record Types Explained (A Record vs CNAME)

Last updated: January 30, 2026 • 4 min read

Understanding the difference between A Records and CNAME records, and why ServerTrack requires an A Record for your tracking domain.

Introduction

DNS (Domain Name System) records are essential for directing internet traffic. When setting up ServerTrack, you'll need to create an A Record to point your tracking subdomain to our servers. Understanding the difference between A Records and other record types (like CNAME) is crucial for proper setup.

What is DNS?

DNS is like a phone book for the internet. When someone types a domain name (like data.yoursite.com), DNS translates it to an IP address (like 123.45.67.89) so the browser knows where to send the request.

A Record vs CNAME Record

A Record (Address Record)

An A Record directly maps a domain name to an IPv4 address. This is what ServerTrack requires.

Example:

Type: A

Name: data

Value: 123.45.67.89

Result: data.yoursite.com → 123.45.67.89

Characteristics of A Records:

  • Points directly to an IP address
  • Faster resolution (one less DNS lookup)
  • Required by ServerTrack for custom domain setup
  • Works at the root domain level

CNAME Record (Canonical Name Record)

A CNAME Record creates an alias that points one domain name to another domain name (not an IP address).

Example:

Type: CNAME

Name: www

Value: yoursite.com

Result: www.yoursite.com → yoursite.com (then resolved to IP)

Characteristics of CNAME Records:

  • Points to another domain name (alias)
  • Requires an additional DNS lookup (slightly slower)
  • Cannot be used at the root domain level
  • Cannot be used with other record types for the same name

Why ServerTrack Requires an A Record

ServerTrack requires an A Record for several important reasons:

  • Direct IP Connection: Our servers need a direct IP connection to your subdomain for SSL certificate verification and proper routing
  • SSL Certificate Generation: Let's Encrypt (which we use for free SSL certificates) requires direct A Record resolution for domain validation
  • Performance: A Records are faster because they eliminate an extra DNS lookup step
  • Reliability: A Records provide more direct control over routing and reduce potential points of failure

Common DNS Misconceptions

Misconception 1: "CNAME is Easier to Manage"

Reality: While CNAME might seem easier if our IP changed, A Records are actually simpler for subdomains. Since we provide you with a stable IP address, A Records are the better choice.

Misconception 2: "I Can Use CNAME for Root Domain"

Reality: CNAME records cannot be used for root domains (e.g., yoursite.com). They can only be used for subdomains. A Records work for both root domains and subdomains.

Misconception 3: "A Records Can't Point to External IPs"

Reality: A Records can absolutely point to any IPv4 address, including external IPs like ServerTrack's servers. This is exactly what you need to do.

How to Create an A Record

The exact steps vary by DNS provider, but the general process is:

  • Log in to your DNS provider's control panel (GoDaddy, Namecheap, Cloudflare, etc.)
  • Navigate to DNS Management or DNS Settings
  • Find the option to add a new record
  • Select record type: A
  • Enter the subdomain name (e.g., data for data.yoursite.com)
  • Enter the IP address provided in your ServerTrack dashboard
  • Set TTL (Time To Live) - usually 3600 (1 hour) or Auto
  • Save the record

Understanding TTL (Time To Live)

TTL determines how long DNS servers cache your record before checking for updates.

  • Low TTL (300-3600 seconds): Changes propagate faster, but increases DNS queries
  • High TTL (86400+ seconds): Reduces DNS queries, but changes take longer to propagate
  • Recommended: Use 3600 (1 hour) for initial setup, then increase to 86400 (24 hours) once stable

DNS Provider Examples

Cloudflare

  • Go to your Cloudflare dashboard
  • Select your domain
  • Click "DNS" in the left sidebar
  • Click "Add record"
  • Type: A
  • Name: data (or your chosen subdomain)
  • IPv4 address: 123.45.67.89 (your ServerTrack IP)
  • Important: Make sure the cloud icon is Grey (DNS Only), not Orange (Proxied)
  • Click "Save"

GoDaddy

  • Log in to GoDaddy Domain Manager
  • Click "DNS" next to your domain
  • Click "Add" in the Records section
  • Type: A
  • Name: data
  • Value: 123.45.67.89
  • TTL: 1 Hour
  • Click "Save"

Namecheap

  • Log in to Namecheap
  • Go to Domain List → Manage
  • Click "Advanced DNS" tab
  • Click "Add New Record"
  • Type: A Record
  • Host: data
  • Value: 123.45.67.89
  • TTL: Automatic
  • Click the checkmark to save

Verifying Your DNS Record

After creating your A Record, verify it's working:

Using Command Line (Terminal/CMD)

# Windows (CMD)
nslookup data.yoursite.com

# Mac/Linux (Terminal)
dig data.yoursite.com
# or
nslookup data.yoursite.com

The output should show your ServerTrack IP address.

Using Online Tools

Troubleshooting

DNS Not Propagating

  • Wait: DNS changes can take up to 24-48 hours to propagate globally
  • Check TTL: Lower TTL values help propagation happen faster
  • Clear DNS Cache: Flush your local DNS cache:
    • Windows: ipconfig /flushdns
    • Mac: sudo killall -HUP mDNSResponder
    • Linux: sudo systemd-resolve --flush-caches

Wrong IP Address Resolving

  • Double-check the IP address in your ServerTrack dashboard
  • Verify the A Record value matches exactly
  • Check for typos in the subdomain name
  • Ensure you're checking the correct subdomain

Summary

For ServerTrack setup, always use an A Record pointing your tracking subdomain directly to our IP address. A Records are faster, more reliable, and required for SSL certificate generation. While CNAME records have their uses, they're not suitable for ServerTrack's requirements.

Once your A Record is created and verified, proceed to domain verification in your ServerTrack dashboard.

Was this article helpful?

Please log in to provide feedback on this article.