Skip to content
  • Services
  • Pricing
  • Enterprise
  • Technology
  • Company
    • Support
  • BOOK DEMO
  • Login
Menu
  • Services
  • Pricing
  • Enterprise
  • Technology
  • Company
    • Support
  • BOOK DEMO
  • Login
DNS Made Easy Blog

How to Redirect from One Domain to Another

Home  /  Blog  /  How to Redirect from One Domain to Another

Redirects are a simple tool, but tricky to manage. I like to think of them like the person of interest boards you see in crime shows that connect peoples’ headshots to one another with a red string.

The more connections you create, the more difficult it becomes to manage, and harder to remember it begins and ends. 

The same can be said for redirects… which is why you should only use a redirect when it’s absolutely necessary. The last thing you want to do is create a redirect loop or increase your load times because of too many redirects. 

How Redirects Work

Most modern websites use redirects. For example, if you go to our homepage, there are a handful of redirects being used to funnel traffic to the right version of our homepage.

  1. HTTP to HTTPS redirect
  2. www. to the “naked” version of dnsmadeeasy.com
  3. All possible subdomains to dnsmadeeasy.com (with the exception of a few we reserve for our help site and blog)

These redirects are considered “internal” and operate on the same FQDN (Fully Qualified Domain Name), dnsmadeeasy.com. You can create them using simple CNAME records that point one hostname to another or on your web server using 301 redirects. 

But what if you want to redirect one domain to another? 

HTTP Redirection Records

For any redirects that point outside of your FQDN, you need to use a special kind of DNS record called an HTTP Redirection record.

These records are actually an A record that points to a dedicated web server containing the 301 redirect to the external FQDN. 

How an HTTP Redirection Record Works

All you have to do is create two HTTP redirection records. 

Psst! If you have any existing root records, you will need to delete them prior to creating your HTTP redirection records.

  1. Leave the name field blank (this is the root) and point it to the full URL of the destination domain. 
  2. For the second record, name is * (wild card) and point it to the full URL of the destination domain. 

You can learn how to create HTTP redirection records on our help site. 

Want to read more? Check out this blog on HTTP redirects and why HTTPS redirects are so #$%-ing hard. 


Also published on Medium.

Share on Facebook Share on Twitter Share on LinkedIn

About Author

DNSME Team

DNS Made Easy is a subsidiary of Tiggee LLC, and is a world leader in providing global IP Anycast enterprise DNS services.

Facebook Twitter Google+ LinkedIn

Related Posts

  • DNS Provider 2022

    DNS Made Easy – 2022 Preview and 2021 Review

    December 16, 2021
  • Top DNS Servers 2022

    Top DNS Servers 2022

    December 8, 2021
  • dns performance test - ecommerce providers

    Top 6 DNS Solutions for ECommerce Sites

    November 22, 2021

Recent Posts

  • DNS Provider 2022
    DNS Made Easy – 2022 Preview and 2021 Review December 16, 2021
  • Top DNS Servers 2022
    Top DNS Servers 2022 December 8, 2021
  • Tiggee Acquires PerfOps
    Tiggee LLC Announces Acquisition of PerfOps Data Suite December 2, 2021
  • dns performance test - ecommerce providers
    Top 6 DNS Solutions for ECommerce Sites November 22, 2021
All Rights Reserved DNS Made Easy 2019 | Privacy Policy | sales@dnsmadeeasy.com