Reading Time: 8 minutes

Full Cloudflare Website Integration

In this article, we will discuss how to set up our domain in a full Cloudflare configuration. This will allow us to take full advantage of their many DNS features, increased speed, Railgun options, and other amazing features that full domain integration allows. 

It should be noted that these instructions do not require you to interact with your Cloudflare account directly. Liquid Web Support works with Cloudflare via your Manage account interface to implement many of these changes. Unfortunately, support cannot directly access external providers, so any changes that need to be made outside the Manage interface will need to be addressed by you or your team. This being said, we find the benefits of a full Cloudflare domain setup to be well worth the effort of some minor DNS modifications.

Liquid Web Manage Dashboard

Let’s get started. Log in to your Liquid Web manage account at https://manage.liquidweb.com and go the Domain's navigation menu in the left menu. Once there, click on the Cloudflare tab. 

In the Cloudflare tab, click on the “Add Website” button.

CF.add.website.button

Next, we will enter our domain name in the box at the top and then select the radio button in the bottom section “Make Cloudflare my DNS provider (Full).”

CF.make.cf.my.dns.provider

Next, select the plan you would like to use at the bottom and then click “Activate Service.” Shortly, a new domain will appear in your account. You will see this screen once it has completed. 

CF.add.a.website

Now, click “Go to Dashboard” and then we can see the domain, and note its pending status.

CFfull.cf.example.pending

This screen will also show you the nameservers that will be assigned to our domain, but these nameservers will vary for different users so the ones you see here may not match the ones you have assigned to you. 

CF.nameservers

Cloudflare Dashboard

Next, we click the three dots on the right side of our new domain name screen, and then select “Cloudflare Dashboard.”

CF.dashboard.topright.menu

This will take us to the Cloudflare site where we will need to log in to access our account. Now, we need to locate our domain name and it will still show pending, but we can still click on it. 

CF.pending.nameserver.update

Next, we will be taken to a screen where we can complete our nameserver setup, but before we do, we need to click on the DNS Icon as we need to add our DNS records. 

CF.dns.icon

Adding DNS Records

Now, we will need to add all of our DNS records for the domain. This information will vary by domain, but at a minimum, you will need to add an A record that points to your Liquid Web server IP and a www.domain.tld cname record. 

CF.add.dns.records
CF.add.dns.records
Note:
If this is a new domain, or you are currently using Liquid Web nameservers, we can create a new DNS zone file entry in your Liquid Web manage account, as described here, or we can use one we have already set up and then use the export feature as described in the link. Once you have the zone file downloaded, go back to your Cloudflare account DNS Icon for your domain. Then click Advanced.
CF.dns.advanced.icon

From here, select the zone file to upload and leave the defaults in place.

CF.include.dns.records2

Next, click upload. You may get an error stating that some records failed to upload, so we need double-check to make sure the records are correct, but most of the information should be imported. Make sure to remove any NS records that are imported by clicking on the X to the right of them and confirming that choice.

CF.confirm.dns.records2

Once you have confirmed that all your DNS records look correct, we can remove the proxying option as we do not want interruptions in our service (as will be explained in the SSL section below.) 

Proxy Status

To remove Proxying for your records, click on the Proxied Cloud.

CF.proxy.status

Next, it will turn to DNS Only.

CF.proxy.status2

Once these settings are all adjusted to “DNS Only”, we can move on.
Note: when we are at the “DNS Only” setting, no traffic is passing through Cloudflare’s CDN network yet.

CF.dns.records

Change Nameservers

Now we are ready to change our nameserver information to the ones provided to us by Cloudflare on the overview page. Cloudflare provides clear directions to accomplish this.

CF.complete.ns.setup

We will have to wait until propagation takes place after changing our nameservers for our domain. Tip: A good way to check on the progress of propagation is to review your domain name at https://www.whatsmydns.net/.

Once the propagation of your new nameserver has taken place, we should verify that our site loads correctly. At this point, our DNS is running through the Cloudflare service, but the other DNS records like MX, cname and other records should still be pointing at your server.

SSL Setup

Next, let’s take a look at our SSL setup. In the Cloudflare main menu, click on the SSL/TLS icon.

CF.ssl.setup

We can now select any of the four options available here with "Flexible" being the most lenient if you want SSL support, Full, or Full (Strict) being most stringent, as it indicates. Generally, Full is a good option here, or if needed, Flexible will work also. If there are issues with Flexible, we can switch back over to Full. 

CF.ssl.tls.mode

Cloudflare will issue a universal SSL to cover our domains, but sometimes, this can take time after we change our nameserver information. We want to try to avoid proxying our traffic until we confirm that the universal certificate has been issued as we may see insecure warnings if it has not been completed. To confirm this change, click on the “Edge Certificates” tab under the SSL/TLS button.

CF.ssl.edge.cert

The first box is Edge Certificates, and in this area, we want to see a certificate present for our domain. If we do not see this certificate, we will have to wait until we do see the certificate to enable proxying.

CF.ssl.edge.cert2

When there is a certificate in place, it will look like this.

CF.ssl.edge.cert3
Note:
An alternative could be to use Let’s Encrypt for our full certificate, as explained in this article.

Enable DNS

Once we see that certificate in place, (which might take a little while) we are now ready to proxy traffic through Cloudflare, so you get all the benefits of the service. Let’s finish these final few settings. In your Cloudflare account go back to the DNS tab

CF.dns.icon2

and click on the “DNS only” clouds

CF.dns.only.icon

to toggle them back to “Proxied.”

CF.proxy.icon

Success! 

Now we have set up our site to run on Cloudflare and have our traffic proxied through them.

Bonus

Cloudflare has some other great features as well. There are two which stand out that we should consider employing. The first of which is Railgun.  

Railgun

The Railgun service helps cache content and improves the overall speed of our site. We also provide this service as part of the Liquid Web Cloudflare plan. If you do not have our Cloudflare service, the cost to utilize this service would be close to $200/month for a similar plan from Cloudflare. Enabling this service is very easy. Simply log in to your Cloudflare account in manage and click on the Speed Button, 

CF.railgun.icon

then the Optimization tab, 

CF.optimization

and then scroll down to the Railgun heading. Here we will see the Liquid Web Central and Liquid Web Staging areas. For this selection, we are only concerned with the Liquid Web Central Option.

CF.railgun.manage.options

To enable it, toggle the off button to the on position,

CF.railgun.manage.options2

Then click the Test button. We will want to ensure we see a Success message after the test runs.

CF.railgun.manage.options3

Now, let's check our site to ensure it is working as expected. In rare cases, there could be issues with Railgun, but generally, enabling this service will make your website faster. That's it! Railgun is enabled.

BOT Fight Mode

This feature helps to stop malicious bots from weighing your server down and is an excellent option to stop most of them. To enable this setting in your Cloudflare account, go to the Firewall button

CF.bot.fight.mode

and then click the settings tab on the right. 

CF.bot.fight.mode2

You will see the Bot Fight Mode box, which needs to be toggled to the on position. Now we are fighting back against the malicious bots.

CF.bot.fight.mode3

Try It Now!

Utilizing Cloudflare is an excellent way to optimize any site in multiple ways. Would you like to give it a try?

Give us a call at 800.580.4985, or open a chat or ticket with us to speak with one of our knowledgeable system administrators or Experienced Linux technicians to learn how you can take advantage of this system today!

Avatar for Dayne Larsen

About the Author: Dayne Larsen

Dayne was born into IT and remembers taking notes as a kid on old mainframe punch cards his mom brought home. With a degree in Technology Education from Montana State University, he enjoys being a helpful human to clients and loves to empower people to tackle challenges. He has worn many hats in his day, from a stay-at-home Dad, to a freelance web designer, LEGO company Merchandiser and even an antique store owner. In his free time you will find him fly fishing, snowboarding, working on his 66' Mustang, home improving, or enjoying his family.

Latest Articles

In-place CentOS 7 upgrades

Read Article

How to use kill commands in Linux

Read Article

Change cPanel password from WebHost Manager (WHM)

Read Article

Change cPanel password from WebHost Manager (WHM)

Read Article

Change the root password in WebHost Manager (WHM)

Read Article