How is 1018 different from 1016 Origin DNS Error?

They break at different layers. 1016 is about your *origin*: Cloudflare has your zone loaded fine, but a DNS record inside it points at a hostname that won't resolve, so the edge can't find your backend. That's a record you fix. 1018 is about the *zone itself*: Cloudflare can't apply your domain's configuration at the data center at all. It's one step further out, and it's usually not a record you can edit your way out of.

I just moved my domain to Cloudflare and got 1018. Is it broken?

Probably not — this is the most benign cause. When a zone is newly activated, its configuration takes time to propagate to every edge data center. A request that hits a colo before the config lands there returns 1018. It typically clears on its own within a short window. If it's still failing hours later, or only some regions see it, treat it as a real zone problem, not propagation.

What is a 'ghost' or 'partner' zone and how does it cause 1018?

Many hosts and platforms put your domain on Cloudflare on your behalf through Cloudflare's partner API. If you later move the domain — or the partner's own DNS integration fails — the zone can be left half-registered: Cloudflare still thinks it serves the domain, but no working configuration exists behind it. That stranded state throws 1018. Fixing it usually means the original partner (or Cloudflare support) removing the ghost zone, not editing your own records.

Views: 8

Error 1018 Unable to Resolve (Cloudflare): Fix

Error 1018 means Cloudflare can't apply your zone's config at the edge — a recent activation or a ghost partner zone, not a record you fix. Free instant check, no sign-up.

Check your domain for this issue now

Free, no sign-up. Runs the exact check this guide describes and shows what to fix.

Problem

Cloudflare returns Error 1018: Unable to Resolve (older pages word it Could not find host). A request reaches a Cloudflare data center, but the edge can’t load or apply the configuration for your domain, so it has nothing to serve.

Symptoms

The Cloudflare-branded error page shows Error 1018 with a Ray ID.
It often appears right after you activate a domain on Cloudflare or move it between accounts or hosts.
It can be intermittent by region — some visitors see it, others don’t — which points at uneven edge propagation.
Your origin server is completely healthy; the failure is happening before Cloudflare ever tries to reach it.

What this error actually means

Most Cloudflare 1xxx errors are about the path from the edge to your server: a missing record, a firewalled origin, a dead backend. Error 1018 is different, and that difference is the whole diagnosis. It fires before Cloudflare gets anywhere near your origin — it means the edge tried to load your zone’s configuration and couldn’t apply it.

Per Cloudflare’s own documentation, this happens for three main reasons: a recently activated domain whose settings haven’t finished propagating to the edge; a domain created through a Cloudflare partner (a host or platform) whose DNS integration has failed; or, more generally, a request reaching a data center where your domain’s configuration can’t be applied. In every case the problem is the zone’s state on Cloudflare, not a value you typed into a DNS record.

That’s why 1018 is the rare Cloudflare error you often can’t fix by editing your DNS. A 1016 is yours to fix — the origin record is wrong. A 1001 is a resolution failure for the requested host. 1018 sits one layer out from both: the zone itself is in a state where Cloudflare can’t serve it.

Top 3 causes

Recent activation, config still propagating - The most common and most harmless. A newly activated zone needs its configuration pushed to every edge data center; requests that arrive early get 1018 and it clears as propagation completes. If it doesn’t clear within a few hours, it isn’t this.
A ghost or stranded partner zone - Your domain was placed on Cloudflare through a host or platform’s partner integration, and it’s now half-registered — Cloudflare believes it serves the domain but no working configuration sits behind it. This is common after migrating away from a website builder or managed host that had quietly enrolled you in Cloudflare.
A configuration that can’t be applied at the edge - A zone-level or account-level problem prevents Cloudflare from loading your settings at the data center handling the request. This is genuinely on Cloudflare’s side and typically needs their support to inspect.

Diagnose with DechoNet

DNS Lookup to check what your domain’s nameservers and records actually resolve to on the public internet. If the domain isn’t really pointed at Cloudflare’s nameservers, or resolves inconsistently, you’ve likely found a half-finished activation or a stranded zone rather than a live one.
HTTP Check to confirm the response is genuinely the Cloudflare 1018 page (capture the Ray ID) and not a different error being blamed on Cloudflare — and, after a fix, to confirm the site serves normally again.

Resolution checklist

If you just activated or moved the domain, wait out the propagation window before doing anything else — many 1018s clear on their own.
Confirm your domain’s nameservers actually point to the Cloudflare account you expect, using DNS Lookup. A mismatch means the zone isn’t live where you think it is.
If the domain was set up through a host, website builder, or other partner, contact that provider to remove or re-provision the zone — a ghost partner zone is theirs to clear, not something you fix in your own DNS panel.
Capture the Ray ID from the error page and a HAR file while reproducing it; you’ll need both for support.
If the domain is correctly on your own Cloudflare account and 1018 persists past propagation, open a Cloudflare support ticket with the Ray ID — this is the case that’s on their side.

When to escalate

Escalate to your host or platform if the domain reached Cloudflare through their integration; they own the partner zone and are the only ones who can remove a stranded one.
Escalate to Cloudflare support if the domain is correctly activated on your own account, nameservers point where they should, and 1018 still fires well past the propagation window — that’s an edge-side configuration failure you can’t resolve from the dashboard.