Error 1016
Error 1016 Origin DNS Error Error
What This Error Means
Error 1016 Origin DNS Error occurs when Cloudflare attempts to connect to your origin server but cannot resolve its IP address via DNS. Essentially, Cloudflare has the address you told it to visit, but that address leads nowhere or doesn't exist in the global directory. This typically happens when a CNAME record points to an unresolvable target or when the origin server's DNS records are missing entirely.
Common Causes
- The CNAME record in Cloudflare points to a target domain that does not exist or has no A records.
- The root domain (apex) is missing an A record pointing to the server IP.
- A Cloudflare Tunnel (cloudflared) is configured but the tunnel is down, deleted, or misconfigured.
- DNS propagation delays after changing hosting providers or nameservers.
- The origin server's DNS provider is experiencing an outage.
- A typo in the DNS target value (e.g., pointing to `lb.example.com` instead of `lb-prod.example.com`).
- The target of a CNAME record is itself a CNAME that fails to resolve (chaining issues).
How to Fix It (For Users)
- 1 Refresh the page after a few minutes, as the issue might be a temporary DNS glitch.
- 2 Clear your browser cache and flush your local DNS to ensure you aren't seeing a stale error.
- 3 If the site recently moved, wait for DNS changes to propagate (up to 48 hours).
- 4 Contact the site owner if the error persists, as this is a server-side configuration issue.
For Site Owners / Developers
- Log in to the Cloudflare Dashboard and check your DNS records tab immediately.
- Verify that your CNAME records point to a valid, existing domain that resolves to an IP.
- If using a CNAME for the root domain, ensure CNAME Flattening is enabled or add a fallback A record.
- Use `dig +short target-domain.com` or `nslookup target-domain.com` to verify the target resolves.
- If using Cloudflare Tunnel, check the tunnel status in the Zero Trust dashboard or run `cloudflared tunnel list` on your server.
- Ensure your origin server's IP address hasn't changed if you are using A records.
- Check for typos in your DNS records; a single missing character can cause this error.
- If you recently updated DNS, use a global propagation checker to see if the changes have spread.
- Review your Cloudflare Load Balancer pools to ensure the origin monitors are healthy.
When It Is NOT Your Fault
If the DNS provider for the origin server is down or experiencing a global outage.
Check if this outage affects everyone globally
This error often indicates a wider problem. Use our tool to verify if the site is down for everyone.
Check Website Status →Recommended Tool to Prevent This Error
Fix DNS resolution issues and protect your site from DDoS attacks with Cloudflare.