Domain Setup
Host Your Domain with Cloudflare
Introduction
Hosting your domain through Cloudflare provides you with powerful DNS management, enhanced security, and faster performance. In this guide, we’ll walk you through the steps to set up your domain on Cloudflare and configure both the root domain (example.com) and the www subdomain (www.example.com) to point to store.roundrockk.com.
Step 1: Create a Cloudflare Account
-
Visit Cloudflare and sign up for a free account.
-
Add your domain (e.g., yourdomain.com) to Cloudflare.
-
Cloudflare will automatically scan your existing DNS records.
Step 2: Update Nameservers
-
Cloudflare will provide you with two nameservers (e.g., ns1.cloudflare.com and ns2.cloudflare.com).
-
Log in to your domain registrar (where you purchased your domain).
-
Replace the current nameservers with the Cloudflare nameservers.
-
Save changes — propagation may take a few hours.
Step 3: Configure DNS Records
Once your domain is connected to Cloudflare:
-
Go to the DNS section in your Cloudflare dashboard.
-
Add or edit the following records:
-
Root Domain (@)
-
Type: CNAME
-
Name: @ (represents the root domain)
-
Target: store.roundrockk.com
-
TTL: Auto
-
Proxy Status: Enabled (orange cloud) for Cloudflare protection
-
-
Subdomain (www)
-
Type: CNAME
-
Name: www
-
Target: store.roundrockk.com
-
TTL: Auto
-
Proxy Status: Enabled
-
Step 4: Verify Setup
-
Save your DNS records in Cloudflare.
-
Wait for DNS propagation (usually within minutes to a few hours).
-
Test by visiting both yourdomain.com and www.yourdomain.com.
-
Both should redirect or resolve to store.roundrockk.com.
-
By setting up your domain on Cloudflare and pointing both the root and www subdomain to store.roundrockk.com, you ensure consistent access to your ecommerce store with added benefits of security, speed, and reliability.
Step 5: SSL/TLS Settings
This configuration ensures that visitors connect securely to your domain via SSL/TLS encryption between the browser and Cloudflare, while Cloudflare communicates with the origin server over unencrypted HTTP. It provides a balance between ease of deployment and basic security enforcement.
| Setting | Value |
|---|---|
| Encryption mode | Full |
| Always Use HTTPS | On |
| Automatic HTTPS Rewrites | On |
Step 6: Security Settings (Optional Enhancements)
| Setting | Value |
|---|---|
| Block AI bots | Block on all pages |
| Bot Fight Mode | On |
Step 7: Configure Cache Rules (Optional)
Rule 1
| Setting | Value | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Rule name | API - Bypass Cache | ||||||||
| If incoming requests match | Custom filter expression | ||||||||
|
|||||||||
| Cache eligibility | Bypass cache | ||||||||
| Place at | First |
Rule 2
| Setting | Value |
|---|---|
| Rule name | Default Cache Enabled |
| If incoming requests match | All incoming requests |
| Cache eligibility | Eligible for cache |
| Edge TTL | Use cache-control header if present, bypass cache if not |
| Place at | Custom → After API - Bypass Cache |
