Docs › Troubleshooting

DNS Not Connecting

Your custom domain shows “Not Connected” after adding DNS records. Here’s how to diagnose and fix the issue.

Symptoms

Common Causes & Solutions

DNS Propagation Delay

DNS changes take time to propagate globally. Wait 15-30 minutes for initial propagation. Full propagation can take up to 48 hours. Check status periodically.

Incorrect Record Values

Step 1: Check your getsimpleup.ca settings

Go to your domain settings and copy the exact values shown.

Step 2: Verify in your DNS provider

Confirm CNAME points to cname.getsimpleup.ca (no trailing dot) and TXT value matches exactly.

Step 3: Save and wait

Save changes and wait 15-30 minutes before checking again.

Conflicting DNS Records

CNAME records cannot coexist with A or AAAA records on the same subdomain. Check for existing records and delete any A or AAAA records for that subdomain. Keep only the CNAME record.

Wrong Subdomain Name

Enter just the subdomain name: app not app.yourdomain.com. Some providers auto-append the domain. Check that the “Name” field matches exactly what getsimpleup.ca shows.

Cloudflare Proxy Enabled

Cloudflare’s proxy can interfere with verification.

Step 1: Open Cloudflare DNS settings

Find your CNAME record in the DNS management panel.

Step 2: Disable proxy

Click the orange cloud icon to turn it gray (DNS only mode).

Step 3: Wait and verify

Wait for propagation, then check status in getsimpleup.ca. You can re-enable the proxy after verification if needed.

DNS Provider Caching

Old records may be cached. Clear your local DNS cache:

Mac:

sudo dscacheutil -flushcache

Windows:

ipconfig /flushdns

Try checking from a different network or device.

Verification Tools

Check your DNS externally using whatsmydns.net:

  1. Enter full subdomain (app.yourdomain.com)
  2. Select CNAME record type
  3. Verify it shows cname.getsimpleup.ca globally

Or use terminal:

dig app.yourdomain.com CNAME

Still Not Working?

If DNS won’t connect after 48 hours, contact support with: