Free and Unlimited Web Hosting

Cloudflare shows "Error 1016: Origin DNS error"

Cloudflare shows "Error 1016: Origin DNS error"

When trying to enable Cloudflare on your domain name, you may see a page with an error like so:

Error 1016 Origin DNS Error

The most common cause for this error is that the "origin server" (which should be your InfinityFree hosting account) is also pointing to Cloudflare. When that happens, Cloudflare doesn't know where your site actually is, so you see this error.

Generally, this happens is because you enabled Cloudflare by changing your nameservers to Cloudflare's nameservers, but also enabled Cloudflare in your control panel. Both methods are fine methods to use Cloudflare, but you should never enable Cloudflare in your control panel if you are not using InfinityFree nameservers.

So now, you need to decide whether you want to use Cloudflare's nameservers or whether you want to switch back to InfinityFree's nameservers and use Cloudflare through the control panel.

Use Cloudflare with InfinityFree nameservers

This is the easiest method. To use Cloudflare with InfinityFree's nameservers, all you need to do is set your nameservers back to the nameservers from InfinityFree. You can use the following nameservers for that:

  • ns1.byet.org
  • ns2.byet.org
  • ns3.byet.org
  • ns4.byet.org
  • ns5.byet.org

After changing your nameservers, you can verify that Cloudflare is still enabled in your InfinityFree control panel. This way, the InfinityFree nameservers will make sure your visitors are properly sent through Cloudflare.

Use Cloudflare with Cloudflare nameservers

If you want to keep using Cloudflare's nameservers, that's fine too. But getting Cloudflare configured correctly is a bit more involved.

The first thing you need to do is go into your InfinityFree control panel and disable Cloudflare for your domain there. If you're using Cloudflare's nameservers, Cloudflare should be turned off in your control panel.

Fix your Cloudflare DNS records

If Cloudflare was already enabled in your control panel when Cloudflare scanned your DNS records, Cloudflare will probably have scanned broken DNS records for your domain. If that's the case, you need to make sure Cloudflare has correct DNS records for your domain.

You can try to fix the records manually by first deleting all DNS records currently in Cloudflare. Then, you'll want to add the following DNS records: - CNAME record with source @ and the target being your account's main domain. How to find your main domain. - CNAME record with source www and target @. - MX record with source @ and target mx.epizy.com (to receive email). - An additional CNAME record for every subdomain. So if you have a subdomain "blog", you need to add a CNAME record with source blog and target @.

Alternatively, you can let Cloudflare fix it for you by letting them rescan your DNS records. To do so, you can follow these steps: 1. Disable Cloudflare in your control panel. 2. Change your domain's nameservers back to the InfinityFree nameservers. 3. Remove your domain from Cloudflare. 4. Wait for at least 48 hours. 5. Add the domain to Cloudflare again and let Cloudflare scan the new DNS records.

Still have questions? Check our forum!