Redirecting Root Domain with Cloudflare

Wed, 28 Aug 2024 00:00:00 +0000

You know the old saying, “It’s always DNS”? Well, it’s true. And the more you dabble in the wonderful world of web management, the more you realize just how much your digital kingdom rests on those little DNS settings. Whether you’re managing a massive web empire or just tinkering with your personal site, knowing how to tame your network infrastructure is like having the keys to the castle. So let’s get into it and setup a redirect at the root level domain together!

Example Scenarios

Redirecting a root domain using Cloudflare is a common practice in various scenarios, especially when managing web traffic, branding, or SEO. Here are some scenarios where someone might need to do this:

1. Branding and Consistency

Redirecting Non-www to www: Because we all want to look sharp and consistent, right? You might want all traffic to go to instead of . This helps ensure that users always see the same version of your site, like having all your socks match—because mismatched URLs are just as bad as mismatched socks.
Redirecting www to Non-www: Or maybe you’re a minimalist and prefer the sleek, no-frills as your primary URL. In that case, you’ll be redirecting everything from to . Just like ditching that unnecessary “www” clutter.

2. Domain Consolidation

Merging Multiple Domains: Got a handful of domains (e.g., , )? It’s like trying to herd cats. Consolidate them by redirecting all traffic to a single domain ( ), so everything points in the same direction. It’s domain feng shui.
Rebranding: Changing your domain from to ? Redirect the old root domain to the new one to keep all your loyal visitors (and your SEO rankings) in tow. Think of it like forwarding your mail after moving to a fancy new digital address.

3. SEO and Duplicate Content

Avoiding Duplicate Content: Google frowns upon duplicate content like a librarian shushing a noisy visitor. To avoid penalties, you’ll want to redirect all traffic to a single canonical URL (e.g., redirects to ). Because let’s be honest, duplicate content is just unnecessary noise.
Maintaining SEO Rankings: Migrating to a new domain? Redirect the old root domain to the new one, and watch as your hard-earned SEO rankings follow you to your shiny new home. It’s like changing the address on your business card but with way more techy jargon involved.

4. Traffic Management

Temporary Redirects During Maintenance: Sometimes your website needs a little TLC. Set up a temporary redirect to a maintenance page ( ) so your visitors know you haven’t vanished into the digital abyss.
Redirecting to a Regional or Language-Specific Site: Got a global audience? Redirect users from the root domain to region-specific sites ( to for U.S. visitors). It’s like rolling out the red carpet, tailored to each visitor.

5. Domain Migration

Moving to a New TLD: Making the leap from .com to .dev? Redirect the old domain ( ) to the new one ( ), and keep everyone on the right track. Think of it as leaving breadcrumbs for your visitors to follow.
Transition from a Development or Staging Environment: Your site is graduating from staging ( ) to production! Redirect the root domain to ensure all traffic flows to your up-to-date masterpiece.

6. Preventing Domain Squatting

Protecting a Brand: Own multiple variations of your domain to protect your brand? Redirect those variations to the main site to prevent confusion and keep domain squatters at bay. Because nobody likes a digital trespasser.

7. Simple URL Forwarding

Redirecting to a Social Media Profile: Not quite ready for a full website? Redirect your root domain to a social media profile ( to ). It’s like handing out your business card, but online.
Redirecting to a Third-Party Service: If your domain is just a gateway to another service (e.g., a blog hosted on Medium or a store on Shopify), redirect it there ( to ). Because who said you need to build everything from scratch?

8. Dealing with Expired Services

Redirecting After Expiring or Discontinuing a Service: If a service or site is no more, its root domain can be redirected to another service or a page explaining the change. It’s like leaving a “We’ve Moved” sign up for your digital neighbors.

Step-by-Step Guide to Redirect a Root Domain Using Cloudflare

Alright, enough scenarios. Let’s get down to business and set up that redirect!

1. Log in to Cloudflare

First things first, log in to your .

2. Select Your Domain

From your list of domains, click on the one you want to redirect.

3. Set Up DNS Records

To make sure traffic to flows smoothly through Cloudflare, set up these DNS records:

Root Domain A Record ( ):
- Type: A
- Name: @
- IPv4 Address: 192.0.2.1 (Just a placeholder, doesn’t actually matter)
- TTL: Auto
- Proxy status: Proxied (Orange Cloud)
www Subdomain A Record ( ):
- Type: A
- Name: www
- IPv4 Address: Same as above (192.0.2.1)
- TTL: Auto
- Proxy status: Proxied (Orange Cloud)

Pro Tip: Prefer a CNAME? No problem. Use this instead:

CNAME Record for Root Domain:
- Type: CNAME
- Name: @
- Target:
- TTL: Auto
- Proxy status: Proxied (Orange Cloud)

4. Create a Page Rule for the Redirect

Now for the fun part: setting up the Page Rule to actually do the redirecting.

In your domain’s dashboard, head over to Page Rules.
Click Create Page Rule.
In the “If the URL matches” field, enter (This little wildcard * will capture everything after the root domain).
Under “Then the settings are”, select Forwarding URL.
Choose your redirect type:
- 301 - Permanent Redirect: This is your “Forever” option.
- 302 - Temporary Redirect: Just temporary? Use this.
In the “Enter destination URL” field, type the URL you want to send folks to, like
1. The $1 is the bit that keeps all your existing links like example.com/some/path working. In short it keeps your old paths intact.
Click Save and Deploy.

5. Test the Redirect

Now’s the moment of truth. Go to in your browser and make sure you land at or wherever you’ve decided to send your traffic. If it works, give yourself a high-five—you’ve just mastered DNS redirection like a pro.

To redirect both and example.com to newdomain.com, you need to create a separate page rule for each address.

Summary Example Configuration

Here’s a quick recap of what you’ve just done:

DNS Settings:
- A Record: @ → 192.0.2.1 (Proxied)
- A Record: www → 192.0.2.1 (Proxied)
Page Rule:
- URL Pattern:
- Setting: Forwarding URL → (301 - Permanent Redirect)

Congrats! By following these steps, you’ve ensured that your root domain is successfully redirected using Cloudflare’s DNS and Page Rules features. Go forth and redirect with confidence—because when it comes to DNS, you’re now in the driver’s seat!

Key Takeaways

You can redirect a root domain with Cloudflare using Page Rules (or DNS with a CNAME at the root, since root-level CNAMEs aren’t always supported)
Set up an A record for @ pointing to a placeholder IP, enable proxy (orange cloud), then create a Page Rule to forward the URL to your target domain
The $1 placeholder in the forwarding URL preserves the original path—so /about becomes example.com/about instead of dropping to the root
You need separate rules for each domain. If you’re redirecting example.com and www.example.com to the same place, create two rules with each source domain
Cloudflare’s pricing determines rule counts: Free tier gets 3 Page Rules, Pro gets 20, Business gets unlimited

— another Cloudflare integration, this time for routing traffic through tunnels
— infrastructure that benefits from proper DNS and domain management

Website - Websites | Derek Armstrong — Software Engineer · AI · Infrastructure