Cloudflare Edge Errors
Origin DNS Error
Reviewed for reference consistency: August 11, 2026
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.
Error 1016 is the origin-side counterpart to 1001. While 1001 means Cloudflare cannot resolve the hostname the visitor requested, 1016 means Cloudflare cannot resolve the hostname it is configured to proxy requests to -- the origin server hostname stored in Cloudflare DNS configuration. This distinction matters: 1001 points to a visitor-facing DNS issue, while 1016 points to a configuration issue in the Cloudflare dashboard.
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
- A company migrates their origin server to a new provider but the Cloudflare DNS record still references the old origin hostname which no longer resolves
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.
Verify the origin hostname in your Cloudflare DNS settings. The A or CNAME record pointing to your origin server must resolve to a valid, reachable address. Common causes include the origin hostname being deleted, expired, or containing a typo.
Yes. If a Cloudflare Worker makes a subrequest to a hostname that cannot be resolved, the Worker may trigger a 1016. Check the fetch URL in your Worker code to ensure it uses a resolvable hostname.
Related Error Codes
Related Errors From Other Categories
Similar error codes documented across different platforms and systems
Process Killed — the process was terminated by a SIGKILL signal
Signal 11 (SIGSEGV) memory fault or Errno 11 (EAGAIN / EWOULDBLOCK) resource unavailable
Exit code 139 — a segmentation fault (SIGSEGV, signal 11) killed the process
Input/output error EIO — a read or write operation could not complete