Cloudflare Error 1016: Origin DNS Error

How to fix it

Try these in order — the most common fix is first.

1. 1. Fix the DNS record

   Copy steps
   1. Open DNS > Records
   2. Check the A record points to a valid IP and the CNAME target resolves with a lookup tool
   Did this fix it? Yes No

2. 2. Load Balancers

   1. Add a fallback pool that uses an origin IP
   Did this fix it? Yes No

3. 3. SSL for SaaS

   Copy steps
   1. Wait until the custom hostname status is active
   2. Create a DNS record for the fallback origin and set it
   Did this fix it? Yes No

Symptoms

'Error 1016 Origin DNS error' on a proxied hostname.

Why it happens

• Missing A record for the origin
• CNAME pointing to a domain that does not resolve
• Load Balancer pool with unresolved CNAME origins
• Incomplete SSL for SaaS custom hostname setup

This guide also covers

• cloudflare error 1016
• origin dns error cloudflare

Other Cloudflare errors

• Cloudflare Error 521: Web Server Is Down
• Cloudflare Error 522: Connection Timed Out
• Cloudflare Error 524: A Timeout Occurred
• Cloudflare Error 525: SSL Handshake Failed
• Cloudflare Error 526: Invalid SSL Certificate
• Cloudflare Error 520: Web Server Returned an Unknown Error
• Cloudflare Error 1020: Access Denied
• Cloudflare Error 1015: You Are Being Rate Limited