Browse help topics

Domains & DNS

How to Manage DNS in Cloudflare

Add your domain to your own Cloudflare account. Check every imported record (especially email). Switch your nameservers to Cloudflare's two, and set SSL/TLS to Full (strict). The work takes about 30 minutes; if DNSSEC is on at your registrar, allow two extra days of waiting. If Cloudflare was set up through Blue Arctic, or you're not sure, open a support ticket first.

  • Updated
  • Last reviewed
  • Intermediate
  • About 30 minutes

Applies to: Cloudflare cPanel Blue Arctic Shared Web Hosting (cPanel) with your own Cloudflare account

On this page
  1. First, list your records
  2. Step 1: Add your domain to Cloudflare
  3. Step 2: Set the proxy status of each record
  4. Step 3: Change your nameservers
  5. Step 4: Choose the encryption mode
  6. Add, edit or delete a record
  7. How to tell it worked
  8. Troubleshooting
  9. Still need help?

Cloudflare is a separate company. It can answer DNS for your domain (the internet’s address book for domain names) and, if you choose, pass website visitors through its network. Your website and email stay at Blue Arctic.

Note

If Cloudflare was set up for you through Blue Arctic, or you’re not sure, open a support ticket before changing anything. Do the same if your site is on Managed WordPress or a VPS.

Note

Once your domain uses Cloudflare’s nameservers, DNS changes you make in cPanel no longer reach the internet. If you add a domain or subdomain in cPanel later, add its records in Cloudflare too.

First, list your records

  1. Check that your site opens at https:// with no “Not secure” warning. If it doesn’t, see How to Fix a “Not Secure” Warning first.
  2. Look up your domain at lookup.icann.org and write down its nameservers, so you can put them back. If they aren’t the ones we gave you, list your records at the company that runs your DNS, not in cPanel (skip item 4, and do items 5 and 6 there).
  3. In the same result, if Delegation Signed says Signed, DNSSEC (an extra security setting) is on. Turn it off at your registrar now (Step 3 says how), then wait a day or two before Step 3.
  4. In cPanel, open the Websites hub, click Manage next to your domain, and open the DNS tab (or the Zone Editor icon, then Manage, if you see that instead). Can’t find either? Open a support ticket.
  5. Write down or screenshot every record in the Zone Records table. Copy long values, such as a DKIM key, as text too.
  6. Note the value of the A record for your domain itself (a number like 203.0.113.10). Cloudflare’s A record must match it.

Step 1: Add your domain to Cloudflare

  1. Sign in to the Cloudflare dashboard, go to Domains and click Onboard a domain.
  2. Enter your domain without www (for example yourdomain.com). If asked how to add your records, choose the option that scans. Click Continue.
  3. Choose the Free plan.
  4. Open the DNS Records page. Compare Cloudflare’s list with the records you wrote down, and add any it missed (except NS and SOA records; Cloudflare sets its own).

Step 2: Set the proxy status of each record

A, AAAA and CNAME records have a Proxy status: Proxied (orange cloud) sends visitors through Cloudflare; DNS only (gray cloud) just gives out your server’s address.

  1. Set every record to DNS only for now.
  2. Your domain and www can become Proxied after Step 4. All others must stay DNS only: usually mail, ftp, autodiscover and autoconfig (if you have them) and any record a service asked you to add. Cloudflare’s proxy carries only website traffic, so email apps can’t connect to a Proxied name.

Step 3: Change your nameservers

Warning

Before you switch, check that every record you wrote down is in Cloudflare, especially your MX and mail records. After the switch, only Cloudflare’s records count. A missing record can stop your email or website.

Warning

If DNSSEC is on, turn it off before you change nameservers, or your domain can become unreachable. To turn it off, find DNSSEC in your domain’s settings at your registrar (some registrars call this removing the DS record). Then look up your domain again until Delegation Signed says Unsigned. Then wait at least 24 hours before you change the nameservers, and 48 hours if you can. No DNSSEC section in the lookup? Ask your registrar whether it’s on.

  1. Copy the two nameservers Cloudflare assigned you. They’re shown on your domain’s Overview page.
  2. At your registrar, replace the current nameservers with Cloudflare’s two. Type them exactly. Can’t find the setting? Ask your registrar.
  3. Wait. This can take up to 24 hours; Cloudflare emails you when your domain is Active.

Step 4: Choose the encryption mode

  1. In Cloudflare, open the SSL/TLS Overview page.
  2. If Automatic SSL/TLS is selected, choose Custom SSL/TLS instead.
  3. Choose Full (strict).
  4. Before you switch anything to Proxied, look at your MX record. If it points to your domain itself, or your mail record is a CNAME pointing to your domain, keep the domain record DNS only and open a support ticket: once it’s Proxied, email apps that use your domain name as their mail server can’t connect. Otherwise, you can switch your domain and www records to Proxied.

Warning

Don’t use Flexible. It sends traffic between Cloudflare and Blue Arctic unencrypted.

Add, edit or delete a record

Open your domain’s DNS Records page. To add a record, click Add record, choose the Type, fill in the name and value, set Proxy status and click Save. Leave TTL as it is. To change one, click Edit on it, then Save. To remove one, click Edit, then Delete, and Delete again.

How to tell it worked

Your domain shows Active in Cloudflare. Your site opens at https:// with no warning in a private browser window. You can send and receive email as before.

Troubleshooting

  • “Too many redirects”: the encryption mode is Flexible. Change it to Full (strict).
  • Cloudflare “Error 526” (invalid SSL certificate): Set the domain and www records back to DNS only and open a support ticket.
  • Email stopped arriving, or your email app can’t connect: check that your MX records were copied across, and that the mail record and any record your MX record points to are DNS only.
  • Still “Pending Nameserver Update” after a day: check at your registrar that both Cloudflare nameservers are saved exactly. See How Long DNS Changes Take.
  • Your website or email stopped working and you need it back now: in Cloudflare, set every record to DNS only and check the records against your list. Fixes there work within minutes. If that doesn’t help, put back the nameservers you wrote down at your registrar and open a support ticket. If you’ve turned DNSSEC on in Cloudflare, first remove the DS record at your registrar and wait as in Step 3.

Still need help?

Open a support ticket from the Client Portal at my.bluearctic.com. Include your domain, a screenshot of your Cloudflare DNS Records page, your SSL/TLS mode, the exact error and what you already tried. Never include your Cloudflare or cPanel password.

Was this article helpful?

Report outdated instructions or suggest an improvement
Type of report

Please do not include passwords or personal information.

Still need help?

Our support team can look into your account and walk you through it.