1. Home
  2. Docs
  3. CDN
  4. Getting Started
  5. Setting up your DNS with CloudFlare

Setting up your DNS with CloudFlare

CloudFlare offers you the opportunity to set up your DNS using your root (apex) domain, your subdomain, or both.

If you’d like to set up your DNS using the root domain or both the root and the subdomain, check out the following section called ‘Adding the Root Domain’. 

If you prefer to only use your subdomain, move directly to the next section called ‘Adding the Subdomain’.

NOTE: If your WordPress blogs are on multiple domains, you need to add all the domains to the my.QUIC.cloud dashboard. My domains -> Settings -> Domain Alias. Each domain needs to be set up for the DNS.

You can also check out our video guide CloudFlare DNS – Domain Set Up for QUIC.cloud.

 

Adding the Root Domain

1. Take a screenshot of your current configurations. Keep this as a reference in case things go wrong, so you have something to go back to.

2. Adjust your TTL (time to live) value to the smallest time period possible (if not already). You need to wait until the time period of the old TTL value has passed before you can use QUIC.cloud. After the old value expires, every record should be updated to the new value. Example: The previous value was 1 hour, so you change it to 2 minutes. If it is 3pm when you change the value to 2 minutes, you must wait an entire hour (until 4pm) to be sure that all the records now use the 2 minute value.

3. Create a new A record pointing to your IP. You can name it any domain name you’d like. It will serve as a back-up record in case you need to switch QUIC.cloud off. Example: origin.quiccloud.blog.

4. (Optional) If you wish to use both the root domain and a subdomain (for instance, quiccloud.blog (@) and www.quiccloud.blog), create a CNAME record pointing the subdomain (www.quiccloud.blog) to your root domain (@). If you already had an A name record for your subdomain, you must delete it first.
You can create a CNAME record by clicking +Add Record and choosing CNAME as the type, adding your subdomain as the name, @ as the target and make the proxy status DNS Only. In our example, the net result is that www.quiccloud.blog targets the same server as quiccloud.blog.

5. Delete your A record for your root domain (@) and create a CNAME record for it instead, pointing to the subdomain you created in step 3.

Deleting the root domain record: On your DNS Management page for the zone, click Edit next to the record you need to remove, and then click Delete in the bottom left corner.

Creating a CNAME Record: You can create a CNAME record by clicking +Add Record and choosing CNAME as the type, adding your root domain (@) as name, and the subdomain (created in step 3) as target. Make the proxy status DNS Only.

6. Check your DNS and site to make sure it is still working properly.  Check out our FAQs for some ways to test.

NOTE: So far, QUIC.cloud is not involved in your process. If there are any issues at this point it is likely due to your DNS configurations.

7. Next, edit your root domain’s (@) CNAME’s target.  Point it to the domain name given to you in your my.QUIC.cloud dashboard.

NOTE: The target domain name you receive from my.QUIC.cloud will be a variant of either tier1.quic.cloud (as shown in the screenshot above) or tier1.quicns.com.

8. Make sure that your site is still accessible as is. Here are some ways to test.

Tip: Ensure that the cloud is set to "Grey" (this means you are not actually using Cloudflare for anything other than the DNS).

NOTE: At this point you are using QUIC.cloud in your process. If there are issues, it may be a QUIC.cloud issue. 

After performing the above steps your site should still be accessible. Nothing should have changed.

If it is not accessible, review your DNS configurations and run through the steps again. Check if your TTL for the old configuration has expired. Make sure that the correct amount of time has elapsed.

If you’d like to bypass QUIC.cloud in the future, you only need to change your CNAME record for your root domain to point to the A record you created with the random domain (discussed here as origin.quiccloud.blog).

 

Adding the Subdomain

1. Take a screenshot of your current configurations. Keep this as a reference in case things go wrong, so you have something to go back to.

2. Adjust your TTL (time to live) value to the smallest time period possible (if not already). You need to wait until the time period of the old TTL value has passed before you can use QUIC.cloud. After the old value expires, every record should be updated to the new value. Example: The previous value was 1 hour, so you change it to 2 minutes. If it is 3pm when you change the value to 2 minutes, you must wait an entire hour (until 4pm) to be sure that all the records now use the 2 minute value.

3. You must create a CNAME record for your subdomain. If you already have an A record for the subdomain, you must delete it first.

Deleting the subdomain record: On your DNS Management page for the zone, click Edit next to the record you need to remove, and then click Delete in the bottom left corner.Creating a CNAME Record: You can create a CNAME record by clicking +Add Record and choosing CNAME as the type, adding your subdomain as the name, and your root domain as the target. Make the proxy status DNS Only.

4. Check your DNS & site to make sure it is still working properly.  Check out our FAQs for some ways to test.

NOTE: So far, QUIC.cloud is not involved in your process. If there are any issues at this point it is likely due to your DNS configurations.

5. Next, edit your subdomain’s CNAME’s target.  Point it to the domain name given to you in your my.QUIC.cloud dashboard.

NOTE: The target domain name you receive from my.QUIC.cloud will be a variant of either tier1.quic.cloud (as shown in the screenshot above) or tier1.quicns.com.

6. Then, make sure that your site is still accessible as is. Here are some ways to test.

Tip Ensure that the cloud is set to "Grey" (this means you are not actually using Cloudflare for anything other than the DNS).

NOTE: At this point you are using QUIC.cloud in your process. If there are issues, it may be a QUIC.cloud issue. 

After performing the above steps your site should still be accessible. Nothing should have changed.

If it is not accessible, review your DNS configurations and run through the steps again. Check if your TTL for the old configuration has expired. Make sure that the correct amount of time has elapsed.

 

NEXT STEP TO GET STARTED:

Enable the CDN

Was this article helpful to you? Yes 1 No

How can we help?