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
| Error | Error 1016: Origin DNS error |
| Usually fixed by | The domain owner |
| Shown by | Cloudflare, instead of the site |
| Between | Cloudflare 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
- 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.
- Fix or replace the target, or point the record straight at the origin’s IP address.
- 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:
- Error 1016 — developers.cloudflare.com
- Error 530 — developers.cloudflare.com