Error 1016 indicates that Cloudflare could not resolve the DNS for the origin server. This is the Cloudflare-specific error that accompanies the HTTP 530 status code. It usually means the domain's DNS records in Cloudflare are missing, the CNAME target does not resolve, or there is a misconfiguration in the origin hostname. This error prevents Cloudflare from even attempting to connect to the origin because it does not know where to send the request.
The A, AAAA, or CNAME record for the domain or subdomain has been deleted or was never created in Cloudflare's DNS settings.
The CNAME record points to a hostname that no longer exists or does not have any A/AAAA records of its own.
The domain was migrated to a new hosting provider but the DNS records in Cloudflare still point to the old provider's now-defunct hostname.
Log into the Cloudflare dashboard, go to DNS settings, and verify that records exist for the hostname returning the error.
Check DNS RecordsIf using a CNAME record, check that the target hostname resolves to a valid IP address.
dig +short your-origin-hostname.provider.com
Create an A record pointing to your origin server's IP, or fix the CNAME to point to a valid target hostname.
After making DNS changes, verify propagation is complete across global resolvers.
Check PropagationA 530 error is returned alongside a 1016 error when Cloudflare cannot resolve the origin server's DNS.
Cloudflare cannot reach the origin server because DNS resolution failed or the origin IP is unreachable.
Cloudflare's DNS could not resolve the requested hostname.