Cloudflare Edge Errors
Cloudflare 1016 Origin DNS Error
Origin DNS Error — Cloudflare cannot resolve the origin server hostname in the zone configuration
What 1016 Means
The 1016 error on the Cloudflare Edge Errors indicates origin dns error — cloudflare cannot resolve the origin server hostname in the zone configuration. This typically occurs due to origin server hostname in cloudflare dns records points to a non-existent or unreachable address.
Unlike 1001 which refers to the visitor-facing hostname, 1016 specifically means Cloudflare cannot resolve the origin server it is supposed to proxy requests to.
Technical Background
Cloudflare stores the origin hostname and resolves it internally to forward requests. A 1016 means this internal resolution has failed, so Cloudflare cannot contact the origin.
DNS records for the origin in the Cloudflare dashboard must point to a reachable IP or resolvable hostname. Stale records left over from a migration are a common cause of persistent 1016 errors.
Common Causes
- Origin server hostname in Cloudflare DNS records points to a non-existent or unreachable address
- The origin domain's DNS records were deleted or expired
- Cloudflare Workers or Page Rules referencing a hostname that no longer resolves
Typical Scenarios
- Origin server migrated to a new provider without updating the Cloudflare DNS A record
- Origin hostname using a CNAME that points to a decommissioned load balancer
- Cloudflare Load Balancer pool member with an expired or typo hostname
What to Know
A 1016 is an origin configuration error distinct from a network connectivity failure. It means Cloudflare's internal DNS system cannot resolve the origin hostname it is configured to forward requests to. The visitor-facing domain is unrelated to this lookup.
Frequently Asked Questions
Common questions about Cloudflare 1016 error
1001 means Cloudflare cannot resolve the visitor-facing hostname. 1016 means Cloudflare cannot resolve the origin server hostname it is supposed to proxy the request to.