How to Set Up a Domain Redirect in 3 Minutes (No Server Required)

Most domain-redirect tutorials jump straight into cPanel, .htaccess, or server access. That's overkill for a simple domain-to-domain redirect. All you need is DNS. Learn how to set it up in minutes.

For domain redirect fundamentals, see our complete guide to URL redirects.

Key Takeaways

• Domain redirects work at DNS level — no hosting or server access needed
• SSL certificates provision automatically before traffic arrives
• DNS propagation takes 5 minutes to 48 hours depending on ISP caching
• Use 301 for permanent redirects (domain migrations, rebrands), 302 for temporary
• Test both HTTP and HTTPS versions after setup

What You Need

Two things only:

1. A domain name registered at any registrar (GoDaddy, Namecheap, Cloudflare, anywhere)
2. A destination URL where you want traffic to go

That's it. Specifically, you DON'T need:

• Web hosting subscription
• Server access (cPanel, FTP, SSH)
• Coding knowledge (.htaccess, nginx configuration)
• SSL certificate management experience

This approach works because DNS based redirect services handle everything at the DNS level, eliminating the need for traditional web hosting infrastructure.

Skip the hosting bill. DNS-based redirects work at the infrastructure layer, so there's no server to configure, no .htaccess to edit, no certificate to manage.

The 3 Step Process

Step 1: Choose a DNS Redirect Service

DNS based redirect services handle redirects without requiring web hosting. They provision SSL certificates automatically and manage the redirect infrastructure for you.

Several DNS-based redirect services exist, including Cloudflare's Redirect Rules, AWS CloudFront, and specialized providers. Each offers different feature sets and pricing models. For this walkthrough, we'll use redirect.pizza, which offers a free tier for up to 5 domains with 250,000 hits per month and focuses specifically on DNS-level redirects without requiring web hosting infrastructure.

Sign up with an email address or OAuth provider (Google, GitHub, Apple). The registration process takes about 30 seconds.

Step 2: Configure Your Redirect

Once logged in, you'll configure two pieces of information:

Source domain: the old domain you want to redirect (example: olddomain.com)

Destination URL: where traffic should go (example: newdomain.com or newdomain.com/specific-page)

Redirect type: select 301 (permanent) or 302 (temporary). For most cases including domain migrations and rebrands, use 301.

The service validates your domains and begins automatic SSL certificate provisioning in the background. This happens immediately when you create the redirect, before any traffic arrives.

This step typically takes 1 to 2 minutes to complete.

In doubt about your redirect type? See our 10-Second Decision Framework.

SSL provisioning starts the moment you save. By the time DNS propagates, your certificate is already waiting.

Step 3: Update DNS Records

The final step is pointing your domain's DNS to the redirect service.

Log into your domain registrar (where you registered the domain). Find the DNS settings section. This location varies by registrar:

• GoDaddy: My Products → Domains → DNS → Manage DNS
• Namecheap: Domain List → Manage → Advanced DNS
• Cloudflare: DNS tab
• Others: Look for "DNS Management," "DNS Settings," or "Advanced DNS"

You'll need to add or update an A record:

• Record type: A
• Name: @ (or leave blank for root domain)
• Value: IP address provided by the redirect service
• TTL: Use default or 300 seconds

For subdomains like www.olddomain.com, you can use a CNAME record instead:

• Record type: CNAME
• Name: www
• Value: Target provided by redirect service
• TTL: Use default or 300 seconds

Save your changes. The redirect service will display the exact values you need to enter for your specific setup. And you're all set!

For more complex subdomain scenarios, see our Guide to Subdomain Redirects.

How Long Until It Works?

After updating DNS, changes begin propagating globally. The timeline depends on several factors:

DNS resolvers worldwide cache your old DNS records. Each resolver has a TTL (Time To Live) setting that controls how long it caches records before querying for updates. As these cached records expire, resolvers fetch your new DNS information and traffic gradually shifts to the new destination.

Typical propagation timeline:

• First visitors may see changes within 5 to 15 minutes
• Most traffic shifts within 2 to 6 hours
• Complete global propagation can take up to 48 hours

Some internet service providers ignore published TTL values and cache DNS records according to their own policies, which can extend propagation time beyond your control.

What's happening during this period: the redirect service has already provisioned an SSL certificate for your domain. When DNS propagation reaches a particular resolver, that resolver's users will immediately start hitting the redirect service, which serves a valid HTTPS redirect to your destination.

Once your DNS reaches a resolver, that resolver's users get a valid HTTPS redirect instantly. No waiting, no errors.

For a deeper explanation of DNS propagation and TTL behavior, see our complete guide to URL redirects.

How to Verify It's Working

Browser Test

Type your old domain directly into a browser address bar. It should redirect to your new destination. Check both HTTP and HTTPS versions:

http://olddomain.com → should redirect to destination
https://olddomain.com → should redirect to destination with no certificate errors

If you see a certificate error, wait 5 to 10 minutes. SSL certificate provisioning typically completes within minutes, but can occasionally take longer.

DNS Propagation Checker

Use whatsmydns.net or similar tools to check DNS propagation status globally:

1. Enter your domain name
2. Select "A" record type
3. Click search

The tool shows whether different global locations have picked up your new DNS records yet.

Command Line Test (Optional)

For technical users, command line tools provide detailed information:

Check DNS records:

dig olddomain.com

Look for the A record pointing to the redirect service IP.

Check redirect headers:

curl -I http://olddomain.com

You should see:

• HTTP status code 301 or 302
• Location header pointing to your destination URL

Troubleshooting Common Issues

Most redirect issues stem from DNS timing or certificate provisioning. For foundational concepts, see our complete guide to URL redirects.

You're Still Seeing The Old Site

Cause: Browser cache or DNS hasn't propagated to your location yet

Solution:

• Clear browser cache
• Test in incognito/private browsing mode
• Wait 15 to 30 minutes and test again
• Use whatsmydns.net to check if your location has received the DNS update

Certificate Error on HTTPS Shows Up

Cause: SSL certificate still provisioning

Solution: Wait 5 to 10 minutes. Automatic certificate provisioning via Let's Encrypt typically completes quickly, but can take up to 15 minutes in some cases. The certificate must be fully issued before HTTPS traffic works without warnings.

If the error persists after 30 minutes, verify that your DNS records are correctly configured and pointing to the redirect service.

For technical details on why HTTPS redirects fail without proper certificate provisioning, see Why HTTPS Redirects Break (And How DNS Fixes It).

DNS Changes Not Showing

Cause: Incorrect DNS record configuration or TTL delay.

Solution:

• Verify you added an A record (not AAAA or other types)
• Confirm the IP address matches what the redirect service provided
• Check that the record name is @ or blank for root domain
• If you just changed the DNS, wait for old TTL to expire

Use dig olddomain.com to see what DNS record is actually being returned for your domain.

Redirect Works But Goes to Wrong Destination

Cause: Typo in destination URL or incorrect path configuration.

Solution:

• Check destination URL for typos (missing https://, wrong domain, extra characters)
• Verify path forwarding settings if you're redirecting to a specific page
• Test the destination URL directly in a browser to confirm it works

Redirect Works for Some Users But Not Others

Cause: DNS propagation in progress, different geographic regions have received the DNS update at different times.

Solution:

• This is normal during the first 2 to 24 hours after changing DNS
• Users in some regions will see the redirect while others still reach the old destination
• No action needed—wait for global DNS propagation to complete
• Use whatsmydns.net to check which regions have received the update
• Gradually, all users worldwide will begin seeing the redirect as their local DNS resolvers refresh their cached records

When to Use This Method

This method works well for:

• Domain to domain redirects (olddomain.com → newdomain.com)
• Retired domains pointing to active sites
• Multiple old domains consolidating to one new domain
• Marketing campaign URLs needing permanent redirect
• Subdomain redirects (blog.old.com → new.com/blog). See also: Redirecting non-www to www

This method may not be ideal for:

• Complex URL pattern matching requiring server side logic
• Dynamic redirects based on user location, device, or other variables
• Page specific redirects requiring database lookups
• Redirects that need to modify query parameters or paths programmatically

Concerned about search rankings? See Are Redirects Bad for SEO?

For bulk domain migrations with hundreds or thousands of pages, see our Domain Migration Checklist for guidance.

Related Guides

• 301 or 302? 10-Second Decision Framework — Choose the right redirect type
• Why HTTPS Redirects Break — The SSL certificate problem explained
• Domain Migration Checklist — For bulk redirects and complex migrations

Ready to Redirect?

Redirect.pizza provides DNS level domain redirects with automatic SSL certificate provisioning. The free tier supports up to 5 domains with 250,000 hits per month. No hosting or server access required. Get started here.