“Error 1016 Origin DNS error”
Cloudflare received the visit for your domain but couldn't work out where your actual server is. Your DNS record in Cloudflare points at a hostname (a CNAME) that doesn't resolve, or at an address that no longer exists. Cloudflare has nowhere to send the request, so it shows its own error page. Your server may be running fine; Cloudflare just can't find it.
Is your site showing it right now?
The free scan loads your page like a visitor and checks for this message, plus broken links, script errors and phone layout. It also walks your signup, booking or contact form, without sending anything.
Free, no signup. Usually done in about a minute.Why it happens
- A CNAME record points at a hostname that was deleted or renamed, such as an old host's server name or a decommissioned load balancer
- The hosting plan was cancelled or moved, and the old target hostname no longer exists
- A CNAME points at another Cloudflare-proxied domain in a different account (not allowed without Cloudflare for SaaS)
- A typo in the DNS record's target, or a record that was never created for www or the root
- Cloudflare Workers, Load Balancing or Spectrum has a stale origin configured
How to fix it
Look at the DNS record in Cloudflare
Cloudflare dashboard > your domain > DNS. Find the record for the failing name (the root and www are separate). If it's a CNAME, note the target; if it's an A record, note the IP.
Check that target resolves
Look up the CNAME target with a DNS lookup tool or dig. If it returns nothing, the target is gone: get the current server hostname or IP from your host and update the record. For an A record, confirm the IP is your current server.
Prefer an A record to the server's IP
If your host gives you an IP, point an A record at it (proxied, orange cloud) instead of a CNAME to the host's name. That avoids breakage when the host renames its servers.
Fix cross-account CNAMEs
If the target is another Cloudflare-proxied site you don't own, you can't CNAME to it from your zone. Point directly at the origin's IP or ask the other site's owner for the right target.
Wait a minute, then purge
Cloudflare picks up DNS changes within a minute or two. Purge Cloudflare's cache and load the site in a private window. The free scan above checks it from outside.
Questions
Is this my hosting company's fault?
Often the trigger is a change on their side (a server renamed, a plan ended), but the record that's wrong is in your Cloudflare DNS, so you can fix it without them once you know the right target.
How is 1016 different from 1001 or 1000?
They're all DNS problems between Cloudflare and your origin. 1016 is the clearest: the origin hostname your record points at doesn't resolve. The fix is the same: make the record point at a server that exists.
The site works when I pause Cloudflare.
Then your registrar-level DNS still has the right address and only the Cloudflare record is stale. Copy the working address into the Cloudflare record and unpause.
Can Page Canary tell me if this comes back?
Yes. Page Canary checks your key pages every day for this message and others like it, confirms it on a second check, and emails you with the fix. One site is free.