Are you facing Cloudflare error 1016?
This guide will help you.
Cloudflare error 1016 occurs when Cloudflare is unable to send requests to the server because its origin IP cannot resolve the A or CNAME DNS record requested.
A 1016 indicates that the IP address you have in the Cloudflare DNS "A" record for your domain is incorrect.
Background Error 1016 / Error 530 means that Cloudflare is unable to send requests to your server because its origin IP cannot resolve the A or CNAME DNS record requested.
In this context, we shall look into methods to fix this Cloudflare error.
Nature of Cloudflare error 1016 ?
Sometimes the record to be specified in the DNS tab of the Cloudflare dashboard is not found or it is a CNAME record to an external domain that does not resolve.
Generally, this can happen if the host had an IP address change or the server is down/offline.
Before going into the steps for fixing this error we will see some of the causes.
What triggers Cloudflare error 1016 ?
1. The Cloudflare DNS configuration does not have an A DNS record that matches the origin IP address.
2. A CNAME record in Cloudflare DNS points to an external domain that cannot be resolved.
3. The origin hostnames (CNAMEs) in Cloudflare Load Balancer default, region, and fallback pools are unresolvable.
Methods to fix Cloudflare error 1016:
Some of the methods to fix this error are given below:
1. First we need to verify that Cloudflare DNS settings include an A record that points to a valid IP address. We can modify the existing A record or create a new one.
2. If the CNAME record is pointing to an external domain, we need to ensure that the target domain can be resolved by using command-line tools as well as third-party tools to check DNS resolution.
The following are two command-line tools:
dig +trace subdomain.example.com
The +trace option outputs detailed information when the DNS response fails:
dig subdomain.example.com @188.8.131.52
The @184.108.40.206 option returns results from Cloudflare’s public DNS resolver.
This allows us to confirm that public resolvers can receive a DNS response:
nslookup subdomain.example.com 47
nslookup subdomain.example.com 47 220.127.116.11