1016: Origin DNS error
In your Cloudflare DNS settings, what record exists for the hostname that's failing?
A CNAME pointing to another hostname
Cloudflare followed your CNAME to find the origin and the hostname it points at didn't resolve to any address. The record in Cloudflare is fine; the name it forwards to is the broken link — commonly a load balancer, PaaS hostname, or bucket endpoint that was renamed or torn down.
Check
Resolve the CNAME target yourself, from outside Cloudflare. An empty answer means the target genuinely doesn't resolve and the error is reproduced.
Fix
Point the CNAME at a hostname that resolves, or recreate the target record. If the target belongs to another provider — a load balancer, an app platform, an object store — confirm the resource still exists there and that its hostname hasn't changed; providers commonly issue a new hostname when a service is recreated. If the target is a name inside a domain you control, check that domain's nameservers are answering at all.
Verify
The second command should return at least one IP address. Then reload the site through Cloudflare and confirm the 1016 is gone.
No record at all, or I can't find one
Cloudflare is authoritative for the zone and has nothing to resolve for this hostname, so it has no origin to reach. This normally follows a record being deleted, renamed, or created on a different zone than the one serving the traffic.
Check
Confirm in Cloudflare DNS that no A, AAAA or CNAME record exists for the exact hostname — including whether it was created on a different zone, which is easy to do when several domains are on one account.
Fix
Create a proxied A, AAAA, or CNAME record pointing at your origin. Take care with the name field: entering the full hostname where only the subdomain label is expected produces a record for failing.example.com.example.com, which looks correct in a list but never matches.
Verify
The lookup should return a Cloudflare IP once the proxied record exists, and the site should load without the 1016.
An A or AAAA record with an IP address
1016 is about Cloudflare being unable to resolve the origin, and an A record supplies the address directly — so there is usually nothing left to resolve. Seeing it here most often means you are looking at a different record from the one serving the request: another record for the same name, a wildcard that takes precedence, a record on a different zone, or an edit that hasn't finished applying.
Check
Check for a second record with the same name, a wildcard record that could be matching first, and whether the zone you edited is the one actually serving the domain — compare its assigned nameservers against the domain's live nameservers.
Fix
Remove any duplicate or conflicting records so one A record remains for the hostname, and confirm the zone is active with Cloudflare's nameservers in place at the registrar. If the record was only just changed, allow it to apply and retry before treating it as a fault. If everything checks out and the 1016 persists, Cloudflare support can see which record the edge actually resolved, which is not visible from outside.
Verify
Confirm the nameservers returned are the Cloudflare pair assigned to your zone, and that the hostname resolves to a Cloudflare address.
Want to narrow it down interactively instead? Use the error lookup tool.