Opens in a new tab

Cloudflare error 1016: Origin DNS error

Cloudflare knows the site but cannot find the server behind it: the DNS record that tells Cloudflare where your origin is — an A record, or a CNAME to another name — is missing or points at a name that does not resolve.

Error 1016: Origin DNS error
ErrorError 1016: Origin DNS error
Usually fixed byThe domain owner
Shown byCloudflare, instead of the site
BetweenCloudflare and your origin’s DNS — not the visitor

Look up the domain’s DNS

Look up the record Cloudflare uses for the origin — the A record, or the CNAME and its target.

What it means

For a proxied record, Cloudflare connects to your origin at the address the record gives. With a CNAME to a name outside Cloudflare, it must resolve that name first. Error 1016 means it could not find any address to connect to.

Why it happens

  • No A record with the origin’s IP address for the name.
  • A CNAME to an external name that does not resolve — a deleted load balancer, an expired hosting name, a typo.
  • Load Balancer pool origins given as CNAMEs that do not resolve.
  • A Worker fetch() to a name that exists only at the external DNS, not on the Cloudflare zone.

How to fix it

  1. Check the record for the name in Cloudflare’s DNS settings: an A record must hold a valid IP; a CNAME’s target must resolve — check it with the lookup above.
  2. Fix or replace the target, or point the record straight at the origin’s IP address.
  3. For a load balancer, add a fallback pool with an origin given by IP address.

Sources

Error text and meaning checked on 25 September 2026 against these official sources:

Know the moment your domain stops resolving

Add your domain and we check its DNS on a schedule — nameservers, DNSSEC, records and registration — and email you when something breaks or changes. Free for your first domain.

Create a free account