Community Tip - Fixing Error: 530 / Error: 1016 Origin DNS Error

Error
Try the suggestions in this Community Tip to help you fix “Error 530: Origin DNS Error”.

Background
Error 1016 / Error 530 indicates Cloudflare is unable to send requests to your server because its origin IP cannot resolve the A or CNAME DNS record requested. Even if Cloudflare’s Anycast address is resolving correctly, the record that should be specified in the DNS tab of your Cloudflare dashboard cannot be found or is a CNAME record to an external domain that cannot be resolved. When this happens, the browser will show a 1016 error, but the actual HTTP response code you’ll see is “Error 530: Origin DNS Error”.

Quick Fix Ideas

  1. You’re using Cloudflare Load Balancer and the origin host names (CNAMEs) in your default/region and fallback pools cannot be resolved via DNS. Use a fallback pool configured with an origin IP as a backup in case all other pools are unavailable.

  2. Your Cloudflare DNS configuration does not have an A DNS record that matches your origin IP address. Verify that your Cloudflare DNS settings include an A record that points to a valid IP address. You could edit an existing A record or create a new one. See Community Tip - Fixing No A, AAAA or CNAME record found / ERR NAME NOT RESOLVED errors for details on how to add DNS records.

  3. You have a CNAME DNS record pointing to an external domain that cannot be resolved. If your CNAME record is pointing to an external domain, ensure that the target domain can be resolved by using command line tools as well as third-party tools to check DNS resolution.

    dig

    dig subdomain.example.com
    dig +trace subdomain.example.com - The +trace option outputs detailed information when the DNS response fails. This information can be useful when working with DNS providers to troubleshoot the issue.
    dig subdomain.example.com @1.1.1.1 - The @1.1.1.1 option returns results from Cloudflare's public DNS resolver. This is useful in confirming that public resolvers can receive a DNS response.
    

    nslookup

    nslookup subdomain.example.com
    nslookup subdomain.example.com 1.1.1.1

    Try an online services, such as whatsmydns.net, to check for DNS resolution worldwide. Note that a response other than a valid IP address (e.g., timeout, SERVFAIL, NXDOMAIN or NOERROR) most likely points to the source of your issue. For resolution, contact the DNS provider for your CNAME.

Lite Reading

Background Resources
Knowledge Base
YouTube

Research The Issue
Community
Google

If You Need More Help
This community of other Cloudflare users may be able to assist you, if not, login to Cloudflare and then contact Cloudflare Support. When you contact support, make sure to include as much of this information as possible: time stamped log files from your origin server, RayID, dig results, nslookup results, domain name, error messages, screen shots, and/or HAR file(s).

Expert Comments Appreciated
This Community Tip will remain open for input from Community experts and those familiar with this issue. We really appreciate comments that start with words like: “The three things I always try”, or “Do this first” or “In my experience”.

This is a Cloudflare Community Tip, to review other tips click here.

Çevirmek…traduzir…翻译…traducir…Traduire…Übersetzen…:globe_with_meridians: Translate