SteadyNode

Cloudflare · HTTP 530

Cloudflare Error 530: Origin DNS Error

Investigate Cloudflare 530 responses associated with Origin DNS Error 1016. Check the configured hostname, public DNS records, delegation, and target addresses.

Origin / Network Firewall

Decode a CDN or gateway error

Paste a captured HTTP response or enter a status and headers. Only the status and response headers are sent; common credential headers are filtered first.

Supports raw headers, full HTTP responses, JSON with status/statusCode and headers, cURL -v/-i response output, and HAR exports. HAR selects a server error first. cURL commands are never executed; request headers, response bodies, and common credential headers are excluded.

Diagnostic report

Error code / name

CF-530

Fault domain

Origin / Network Firewall

Why it happened

Cloudflare could not resolve or route to the configured origin hostname. Missing records, invalid CNAME targets, or broken DNS delegation can prevent the edge from selecting an origin.

Actionable fixes

  1. Check the origin hostname configured in the DNS record and proxy settings for spelling and stale targets.
  2. Verify public A, AAAA, and CNAME answers and confirm nameserver delegation at the registrar.
  3. Resolve CNAME chains to a publicly reachable address and avoid pointing the origin at a proxied loop.

Why this error happened

Cloudflare could not resolve or route to the configured origin hostname. Missing records, invalid CNAME targets, or broken DNS delegation can prevent the edge from selecting an origin.

Actionable fixes

  1. Check the origin hostname configured in the DNS record and proxy settings for spelling and stale targets.
  2. Verify public A, AAAA, and CNAME answers and confirm nameserver delegation at the registrar.
  3. Resolve CNAME chains to a publicly reachable address and avoid pointing the origin at a proxied loop.

Network failure point

Client -> Cloudflare Edge -> resolve origin.example.com -> no usable A/AAAA/CNAME -> X Origin

Verify origin directly via CLI

curl -sS -I -v --connect-timeout 5 --max-time 15 https://origin.example.com/health

Configuration fix

dns-zone.txtdns
api.example.com. 300 IN CNAME origin.example.net.
origin.example.net. 300 IN A ORIGIN_IPV4_ADDRESS

Catch this failure before it becomes an outage

SteadyNode checks endpoint reachability from multiple regions and flags DNS or routing changes that make an origin disappear from only part of the public network.

No credit card required.

Start for free

Frequently asked questions

Is Cloudflare 530 the same as DNS error 1016?

HTTP 530 is a status used by Cloudflare; Origin DNS Error 1016 is a common accompanying message when the configured origin cannot be resolved.

Can a DNS record loop trigger this error?

Yes. A CNAME chain that loops or points back through the same proxy can leave Cloudflare without a usable origin address.

More CDN and gateway error guides

Cloudflare

Vercel and Netlify

AWS CloudFront and ALB

Fastly

Heroku and Render

Nginx and Envoy