Domain Verification Failed - Common Solutions

Introduction

Domain verification is a critical step in setting up ServerTrack. If verification fails, your tracking won't work properly. This guide covers common causes of verification failures and how to resolve them.

Common Causes of Verification Failure

1. DNS Propagation Delay

Symptoms: DNS record exists but verification fails immediately after creation.

Solution: DNS changes can take time to propagate globally:

• Minimum wait: 1-5 minutes (most common)
• Average wait: 15-30 minutes
• Maximum wait: 24-48 hours (rare, usually due to high TTL values)

How to Check:

1. Use DNSChecker.org to check global DNS propagation
2. Enter your subdomain (e.g., data.yoursite.com)
3. Select "A" record type
4. Check multiple locations - they should all resolve to your ServerTrack IP

2. Incorrect DNS Record Configuration

Symptoms: Verification fails even after waiting for propagation.

Common Mistakes:

• Wrong record type: Using CNAME instead of A Record
• Wrong IP address: IP doesn't match ServerTrack dashboard
• Wrong subdomain: Record name doesn't match what you're verifying
• Extra characters: Trailing dots or spaces in DNS record

How to Fix:

1. Double-check the IP address in your ServerTrack dashboard
2. Verify the DNS record exactly matches:
   • Type: A (not CNAME, AAAA, or other)
   • Name: Your subdomain name (e.g., data for data.yoursite.com)
   • Value: Your ServerTrack IP address (e.g., 123.45.67.89)
3. Remove and recreate the DNS record if needed

3. Cloudflare Proxy Enabled (Most Common Issue)

Symptoms: Verification fails when using Cloudflare, or SSL certificate generation fails.

Problem: Cloudflare's proxy (orange cloud) intercepts DNS requests, preventing direct connection to ServerTrack servers.

Solution:

1. Log in to Cloudflare dashboard
2. Go to DNS → Records
3. Find your ServerTrack A Record
4. Click the orange cloud icon to turn it grey (DNS Only)
5. Wait 1-2 minutes for Cloudflare to update
6. Retry verification in ServerTrack

4. High TTL Value

Symptoms: DNS changes take very long to propagate (24+ hours).

Problem: High TTL (Time To Live) values cause DNS servers to cache records for extended periods.

Solution:

• Set TTL to 3600 (1 hour) or lower for initial setup
• After verification succeeds, you can increase TTL to 86400 (24 hours) for better performance

5. Local DNS Cache

Symptoms: DNS checkers show correct IP, but verification still fails.

Problem: Your local computer or DNS resolver has cached the old record.

Solution: Clear your DNS cache:

ipconfig /flushdns

sudo killall -HUP mDNSResponder

sudo systemd-resolve --flush-caches
# or
sudo /etc/init.d/nscd restart

Step-by-Step Troubleshooting Process

Step 1: Verify DNS Record Exists

1. Check your DNS provider's control panel
2. Confirm the A Record exists
3. Verify it's exactly:
   • Type: A
   • Name: Your subdomain (e.g., data)
   • Value: Your ServerTrack IP

Step 2: Check DNS Propagation

1. Go to DNSChecker.org
2. Enter your full subdomain (e.g., data.yoursite.com)
3. Select "A" record type
4. Click "Search"
5. Wait for results - check multiple locations
6. All should show your ServerTrack IP address

Step 3: Check Cloudflare Settings (If Applicable)

1. If using Cloudflare, ensure proxy is disabled (grey cloud)
2. Wait 1-2 minutes after changing
3. Re-check DNS propagation

Step 4: Retry Verification

1. Go back to ServerTrack dashboard
2. Navigate to Domain Configuration
3. Click "Verify Domain" again
4. Wait 30-60 seconds for verification to complete

Advanced Troubleshooting

Using Command Line Tools

Verify DNS resolution using command line:

nslookup data.yoursite.com

dig data.yoursite.com
# or
nslookup data.yoursite.com

Checking SSL Certificate

After DNS verification, ServerTrack automatically generates an SSL certificate. If verification succeeds but SSL fails:

• Wait 5-10 minutes for certificate generation
• Check that your domain resolves correctly
• Verify no firewall is blocking port 80/443
• Contact support if certificate generation fails repeatedly

Prevention Tips

• Set Low TTL Initially: Use TTL of 3600 (1 hour) during setup, increase later
• Double-Check Before Saving: Verify IP address and subdomain name before creating DNS record
• Use DNS Checker: Always verify propagation before attempting verification
• Cloudflare Users: Remember to disable proxy (grey cloud) for ServerTrack subdomain

When to Contact Support

Contact ServerTrack support if:

• DNS propagation is complete everywhere but verification still fails after 24 hours
• DNS record is correct but verification consistently fails
• SSL certificate generation fails after successful verification
• You're seeing error messages not covered in this guide

Summary

Most verification failures are resolved by:

1. Waiting for DNS propagation (15-30 minutes typically)
2. Ensuring Cloudflare proxy is disabled (grey cloud)
3. Verifying DNS record is correct (A Record, correct IP, correct subdomain)
4. Clearing local DNS cache

If verification still fails after following these steps, use DNSChecker.org to verify global DNS propagation and contact support with the results.