Domain not working

When you add your own domain to a site, the console checks it for you and says what’s wrong in plain words. This page explains each status and message on the site’s Domains tab, and what to do.

We check every minute at first, then less often. Select Check again to look straight away.

What each status means

Status	What it means
Waiting for DNS	We can’t see the right record yet. The message under it says what we found.
Getting the certificate	Your DNS is right. We’re getting the HTTPS certificate ready, which usually takes a few minutes.
Live	Visitors can reach your site at the domain.
Not working	It was live, but visitors can’t reach it there any more.
Not checked any more	We stopped checking after 7 days without the right record.

We email you when a domain goes live, if it’s still waiting after a day, if it stops working, and when we stop checking it.

The record isn’t there yet

We can’t find the record for www.example.com yet.

Add the record the console shows at your DNS provider (usually where you bought the domain):

Type: CNAME
Name: www (or the subdomain you added). Some providers want the full name, such as www.example.com.
Target: domains.cloudzyro.app

If the console knows your DNS provider, it names it and links to its own help page. If you’ve just added the record, give it a few minutes.

The record points somewhere else

www.example.com points to something-else.com, not to domains.cloudzyro.app.

There’s already a record for that name, often left from a previous host or a parking page. Edit it, or delete it and add the CNAME above. You can’t have a CNAME and another record (such as an A record) on the same name.

The record is in place but not everywhere yet

Your record is in place. It’s still reaching the rest of the internet, which usually takes a few minutes.

Nothing to do: we’ll keep checking. DNS changes usually work in 5 to 15 minutes, but can take a few hours with some providers. A message saying your DNS looks right and we’re waiting for Cloudflare to confirm it also just needs a few minutes.

Bare domains (example.com)

A bare domain is one without www in front. There are two ways to use one.

Forward it to www (works with any provider). Add www.example.com to the site, then at your DNS provider add an A record for the bare domain (@) pointing to 173.234.137.167. Visitors who type example.com are sent to https://www.example.com on the same page, with a certificate set up automatically.

Use the bare domain itself. Add example.com to the site. This needs a provider that can point a bare domain at another service, usually called a CNAME, ALIAS, ANAME or flattened record on the domain itself. Cloudflare, Namecheap, Porkbun, Squarespace Domains, DNSimple, DNS Made Easy, easyDNS, Gandi and DreamHost can.

Some providers, including GoDaddy, IONOS, Hostinger, DigitalOcean, Amazon Route 53 and Azure DNS, can’t. If yours is one of them, the console tells you, and you can either use www with the forward above, or move your DNS to a provider that can, such as Cloudflare, which is free. See How to move your DNS to Cloudflare.

Cloudflare: the record is Proxied

Your record is set to Proxied in Cloudflare. Switch it to DNS only, the grey cloud.

If your DNS is at Cloudflare, records are Proxied (orange cloud) by default. Edit the record in Cloudflare and switch it to DNS only (grey cloud). We’ll pick it up within a few minutes. Your site still gets Cloudflare’s protection through us.

A CAA record blocks the certificate

A CAA record on your domain stops us getting a certificate.

A CAA record lists which certificate authorities may issue certificates for your domain. If your domain has one, it must allow all three of these, or you can remove the CAA record:

letsencrypt.org
pki.goog
ssl.com

For example, add a CAA record with the value 0 issue "letsencrypt.org", and the same for the other two.

Stuck on Getting the certificate

This usually takes a few minutes. If it’s still there after half an hour, select Check again, and if nothing changes, contact us.

Moving a site that’s already live at this domain

If the domain already serves a live site elsewhere, open Moving a site that’s already live at this domain? on the domain’s card. Add the TXT records it shows first, wait until the status says Getting the certificate, then change the CNAME. Visitors won’t see a gap.

The domain stopped working

www.example.com isn’t pointing at Cloudzyro any more, so visitors can’t reach your site there.

Someone or something changed the record, often a DNS provider change, a domain renewal or an expired domain. Put the CNAME back as shown on the card. If the message says the problem is on our side, we’ve been alerted and are working on it.

Not checked any more

After 7 days without the right record, we stop checking. Add the record, then select Check again.

Slow pages

Your site took too long to answer.

The domain works, but a page took more than 100 seconds, so Cloudflare, which sits in front of every Cloudzyro site, showed visitors an error. Make slow work, such as big imports, reports or long AI calls, run in the background, answer the request straight away, and show the result when it’s ready.

Domains bought with Cloudzyro

If you bought the domain in Domains, choose your site as what it’s for on the domain’s page, and we set the records for you. See Choose what a domain is for.

Web Hosting domains

For a domain used with Web Hosting, point its nameservers to ns1.cloudzyroserver.com and ns2.cloudzyroserver.com, or add an A record to the server address 23.106.58.166. Records are then managed in cPanel’s Zone Editor. Nameserver changes usually reach everyone within a few hours, and occasionally take up to a day or two. See Nameservers and DNS.

Still stuck?

Email support@cloudzyro.com with the domain name, or use Get help in the console, and we’ll walk you through it.