Zarla Help Center

My custom domain isn't connecting

Domain connections fail for a small number of predictable reasons. Work through this list in order — it resolves almost every case.


Got your domain with a website on the original Zarla? It doesn't connect by itself, and there are no settings for you to change: see Your domain from the original Zarla.


Your domain shows an error page and one record is missing


If the Domains page says your domain already points at Zarla but can't find its TXT ownership record, add that record: waiting won't add it for you. Zarla can only secure your domain (the lock icon, HTTPS) once that record proves the domain is yours, so until then visitors to your domain see an error page.


  1. Go to Site settings → Domain → Finish setting up → and copy the TXT record's value. It starts with zarla-verify=.
  2. At your domain company, add a TXT record named @ with that value, then save. Some companies want the name box left empty instead of @. If yours keeps all of a name's TXT values in one record (Amazon Route 53 does), add the value as a new line in that record, in quotation marks.

It usually connects within an hour, and a record you've just added can take a little while to show up on the Domains page. If the page says your TXT record is there but isn't quite right, change that record's value instead of adding a second one.


1. Wait it out (most common)


Domain settings take time to spread across the internet. It's usually minutes, but can take up to 48 hours — especially if the domain was pointing somewhere else before. If you updated the settings recently, give it time and check again.


If the Domains page shows a warning under one of your records, saying what it found and what to change, make that change first (section 3 covers the usual leftovers). Waiting alone won't fix a record that's still wrong, but once you've made the change, the warning can take a while to clear while it spreads.


2. Check the settings match exactly


  1. Go to Site settings → Domain → Finish setting up →.
  2. Compare the settings Zarla asks for against what's saved at your domain company (GoDaddy, Namecheap, etc.).
  3. The usual culprits:
    • A typo, or an extra record left over from the old website
    • Editing the wrong domain (easy to do if you own several)
    • Saving the record in the wrong place — it must be at whichever company controls your domain's settings

3. Look for a conflicting old setup


If your domain used to point at another website builder or host, old records can fight with the new ones. Delete the records the old provider added (their names usually make the origin obvious) and keep only what Zarla asks for.


Two leftovers are easy to miss:


  • Domain forwarding or parking at your domain company adds records of its own, and some companies won't let you delete them while it's on. Turn forwarding or parking off for the domain first, then check Zarla's records are still there.
  • An AAAA record (an IPv6 address) on your domain gets in the way too. Zarla doesn't use one, so delete it.

Until they're gone, some visitors land on a different website and Zarla can't secure your domain (the lock icon, HTTPS).


Using Cloudflare? With the orange cloud (Proxied) on, lookups show Cloudflare's own addresses instead of Zarla's, often IPv6 ones too. Don't delete anything for those: set Zarla's records to DNS only (the grey cloud) instead. Connect a Cloudflare domain shows where.


4. Domain bought through Zarla?


Then there are no connection settings for you to manage — connection is automatic. If it's not working after an hour, contact support. (Records other services ask for, like Google Workspace email, go under Domains → Domain records.)


Still stuck?


Contact support with your domain name and where you bought it. Domain settings trip up plenty of technical people too — we'll happily walk through it with you or check the records from our side.


Related


Was this article helpful?