Cloudflare DNS问题求助：autobedrijfvugts.nl出现1016源站DNS错误

Hey there, sorry to hear you're stuck with the 1016 error on your site — let's break down the most common fixes for this issue, since it's usually tied to misconfigured DNS records or propagation delays.

Step 1: Validate Your Cloudflare DNS Records #

• First, test if the target of your CNAME records resolves correctly. Grab a terminal and run commands like dig your-cname-target-domain.com or nslookup your-cname-target-domain.com. If this returns no valid IP addresses, the problem isn't with Cloudflare — your origin's DNS is broken, which directly causes the 1016 error.
• Double-check the proxy status in Cloudflare's DNS dashboard:
  • Orange cloud: Cloudflare proxies traffic through its network (make sure your origin allows Cloudflare's IP ranges if you use this).
  • Gray cloud: Only DNS resolution (use this to test if the record works without proxying first). If gray cloud works but orange doesn't, your origin might be blocking Cloudflare.

Step 2: Confirm Nameserver Propagation #

Even if you updated your nameservers at your host, DNS propagation can sometimes take longer than expected (though 24 hours is unusual). Run dig NS autobedrijfvugts.nl to verify the active nameservers match the ones Cloudflare provided. If you still see your old host's nameservers, the switch hasn't fully propagated — you might need to follow up with your domain registrar to ensure the NS change was saved correctly.

Step 3: Check Origin DNS Configuration #

If your CNAME points to a subdomain from your hosting provider (e.g., autobedrijfvugts.yourhost.com), log into your host's dashboard and confirm that subdomain has a valid A record pointing to your origin server's IP. Some hosts disable DNS resolution for subdomains once you switch nameservers to a third party, so you may need to re-enable or reconfigure that.

Step 4: Flush Cloudflare's DNS Cache #

Sometimes Cloudflare holds onto stale DNS data. Try these steps:

1. Go to Cloudflare's DNS page for your domain.
2. Edit one of your problematic CNAME/A records, toggle the proxy status (orange ↔ gray), save it, then toggle it back. This forces Cloudflare to re-fetch the origin DNS.
3. You can also use Cloudflare's built-in DNS Checker (under Diagnostics) to see how your records resolve globally — this helps spot regional propagation issues.

Step 5: Follow Up With Your Hosting Provider #

It's possible your host has restricted DNS resolution for your origin domain after you switched nameservers to Cloudflare. Reach out to their support team and ask:

• Is the domain your CNAME points to still actively resolving?
• Have they applied any restrictions on DNS queries from Cloudflare's IPs?

If none of these steps fix the issue, feel free to share redacted versions of your CNAME/A records (e.g., hide any sensitive subdomains) — that will help narrow down the problem faster.

内容的提问来源于stack exchange，提问作者KiwiCoder