Custom Domain Not Working

Custom domain issues almost always fall into one of three categories: incorrect DNS records, DNS propagation delay, or SSL not yet provisioned. This guide walks through diagnosing each.

Step 1 — Confirm your DNS records are correct

In Settings → Domains, Sellrn shows the exact DNS records you need to add. The required records are:

Log in to your domain registrar (e.g. GoDaddy, Namecheap, Cloudflare, Google Domains) and verify these records match exactly. Common mistakes:

• Adding a trailing dot to the CNAME value.
• Setting the CNAME name to the full domain instead of just www.
• Leaving old A records pointing to a previous host.

Step 2 — Wait for DNS propagation

DNS changes take between 5 minutes and 48 hours to propagate worldwide. The most common reason a correctly configured domain "doesn't work" is that propagation isn't complete yet.

Check propagation status at dnschecker.org. Enter your domain and select CNAME. When most locations show green, propagation is complete.

Step 3 — Check SSL certificate status

Sellrn provisions an SSL certificate automatically once DNS is pointing correctly. This usually takes 5–10 minutes after DNS propagates. You can check the status in Settings → Domains:

• Pending — DNS is correct, SSL is being provisioned. Wait 10 minutes and refresh.
• Active — Everything is working. If you still see an error, clear your browser cache.
• Failed — DNS records are not resolving correctly. Re-check Step 1.

Step 4 — Disable Cloudflare proxy (if applicable)

If your domain uses Cloudflare, make sure the DNS records for your Sellrn domain are set to DNS only (grey cloud), not Proxied (orange cloud). Cloudflare's proxy can intercept SSL provisioning and break the connection.

Once Sellrn's SSL is active and the domain is working, you can re-enable Cloudflare proxying if desired.

Step 5 — Apex domain redirect

Many registrars do not support CNAME records on the root (apex) domain (e.g. yourdomain.com). If your registrar does not support an "ANAME" or "ALIAS" record for the root, set up a redirect rule so yourdomain.com redirects to www.yourdomain.com. Most registrars offer this as a free "URL redirect" or "domain forwarding" option.

Still not working?

Run a DNS lookup from your terminal to confirm what the domain resolves to:

dig www.yourdomain.com CNAME

If the ANSWER section shows stores.sellrn.com, DNS is correct and the issue is with SSL provisioning. Contact Sellrn support with your domain name and we will investigate on the server side.