Introduction

A Cloudflare origin DNS error means Cloudflare cannot resolve the hostname it needs to contact behind the proxy. The public site may still point to Cloudflare correctly, but Cloudflare itself does not know where the origin server lives, so requests fail before they ever reach your application.

Symptoms

  • Cloudflare shows an origin DNS error page
  • The site loads intermittently after recent DNS changes
  • One hostname fails while another hostname on the same zone still works
  • DNS tools show missing, stale, or incorrect origin records
  • The error appears after moving the site to a new server or provider

Common Causes

  • The origin A record points to the wrong server IP
  • A required origin hostname was deleted or renamed
  • A CNAME chain points to an invalid target
  • DNS propagation is incomplete after a migration
  • Cloudflare proxy settings were changed before origin DNS was fully updated

Step-by-Step Fix

  1. Identify the exact hostname Cloudflare is trying to reach, such as origin.example.com or the main apex record.
  2. Review the authoritative DNS records at your DNS provider, not only what appears in local cache or third-party tools.
  3. Confirm that the A or CNAME record points to the active server handling the site today.
  4. If you recently migrated hosting, compare the current server IP with the old one and remove stale targets.
  5. Check that any CNAME targets still resolve correctly and do not end in a broken chain.
  6. In Cloudflare DNS, verify the record name, content, and proxy status match the intended setup.
  7. If needed, temporarily gray-cloud the record during testing so you can confirm the origin responds directly.
  8. After correcting DNS, wait for propagation where necessary and test again from multiple resolvers.
  9. Once traffic is stable, re-enable the preferred proxy setting and document the final origin record values.