A 1016 Error (HTTP 530) means we could not resolve DNS to find your origin IP. When we can't find your origin server IP, we can't send requests to your server, so we return this error:
Most common causes are:
- You do not have a matching DNS record inside your Cloudflare DNS settings so we cannot resolve the origin
- Your DNS record is a CNAME to an external service which is returning a DNS failure
- You have a Load Balancer configured with Cloudflare, and the origin hostnames ("CNAMEs") within your default/region pools a and your fallback pool cannot be resolved via DNS. Cloudflare recommends using a fallback pool configured with an origin IP, as the fallback pool is the 'last resort' if all other pools are unavailable.
Troubleshooting Error 1016
- Check your Cloudflare DNS settings (e.g. http://www.cloudflare.com/a/dns/example.com ) for the DNS record that experienced the error - if it doesn't exist it must be created for your DNS record to operate on Cloudflare
- Confirm the value of this record, e.g. it will likely be a CNAME to something external to example.com for example something.anotherdomain.com
- Check the DNS resolution of the CNAME value using a tool like dig or nslookup or an online service. More details on this below.
Checking DNS resolution of an external record
There are some command line tools you can use to check DNS resolution, as well as some 3rd party online services that can help too.
dig +trace something.anotherdomain.com
dig something.anotherdomain.com @22.214.171.124
+trace contains detailed output on where the DNS response failed and can be useful when sharing with DNS providers for troubleshooting. The command containing
@126.96.36.199 will return results against Google's public DNS resolver, this is sometimes a useful comparison to ensure that public resolvers can receive a DNS response.
nslookup something.anotherdomain.com 188.8.131.52
The command containing
184.108.40.206 will return results against Google's public DNS resolver, this is sometimes a useful comparison to ensure that public resolvers can receive a DNS response.
There are online services such as whatsmydns.net above which will check resolution for a DNS record worldwide, and these are worth checking too.
If you see anything other than a valid IP address returned (e.g. you see a timeout, a
NOERROR response) then this is the likely source of your issue, and you'll need to contact the DNS provider for your CNAME in this case to resolve this.