Origin DNS Error
What 530 Means
The 530 error on the Cloudflare Edge-Errors indicates origin dns error. This typically occurs due to a cname record pointing to a deleted external service.
A 530 error indicates that Cloudflare successfully received the client's request but catastrophically failed to resolve the actual origin hostname via DNS internally.
Technical Background
Usually accompanied by a 1000-series error block, 530 represents a fundamental breakdown in mapping the request to a physical backend.
If Cloudflare's internal DNS cannot translate the origin target into an IP address, routing is strictly impossible.
Common Causes
- A CNAME record pointing to a deleted external service
- An unresolvable hostname set as an origin pool target
- Local DNS resolvers failing completely inside the edge cluster
Typical Scenarios
- A domain is aliased (CNAME) to a Heroku app, but the Heroku app was fully deleted.
- A load balancer pool utilizes hostnames that cannot be resolved publicly.
What to Know
Verify that any CNAME targets in your DNS dashboard currently exist and resolve to valid IP addresses externally.
Frequently Asked Questions
Common questions about Cloudflare 530 error
It means the DNS target assigned to your domain no longer exists or cannot be translated into a valid IP address.