Direct Answer

To redirect a domain whose DNS is at Network Solutions, create the redirect in RedirHub, then in Network Solutions point the root domain to RedirHub with an A record, add the TXT verification record, and point www with a CNAME. RedirHub detects the change and issues the SSL certificate automatically.

Network Solutions' built-in Web Forwarding covers simple cases, but it is limited: HTTPS on the old domain may not work, and there are no path rules, analytics or bulk tools. RedirHub adds all of that while your domain and DNS stay at Network Solutions.

Before you start#

  • The DNS for your domain is managed at Network Solutions. If your domain uses another provider's nameservers, make the changes there instead (how to check).
  • A RedirHub account. The 14-day free trial is enough for this guide.
  • About 10 minutes, plus time for DNS to update.

Step 1: Create the redirect in RedirHub#

In the RedirHub dashboard, open Links, click Create and choose Domain Redirect. Enter your source domain and destination, choose the intended redirect type and path/query forwarding, then create the redirect. Follow Connect DNS for the required records.

RedirHub New redirect form with destination, method and Forwarded Options

The root domain covers www

You don't need to add www separately. A redirect for the root domain also covers www, including the same paths, as long as www points to RedirHub in DNS.

Need more detail on these options? See Setting Up URL Redirects and Redirect Methods Explained.

Step 2: Open Connect DNS in RedirHub#

Click Connect DNS in the notice that appears after you create the redirect, or open Hostnames and click Connect DNS next to the domain. Network Solutions doesn't support automatic setup yet, so RedirHub opens the Manual tab. It lists each record with a copy button, plus any old record you need to delete.

Always copy the exact values from your dashboard: abc123 stands for your own workspace ID, and Dedicated IP customers use their own IP. If the domain already has a rehd-verify= TXT record, replace it instead of adding a second one.
HostTypeValue
@ (root domain)A3.33.236.10
@ (root domain)TXTYour verification value, e.g. rehd-verify=abc123.rediredge.com
wwwCNAMEYour CNAME target, e.g. abc123.rediredge.com

Step 3: Update the DNS records at Network Solutions#

  1. Log in to Network Solutions, open Domain Names and select your domain.
  2. Open Advanced Tools. If Web Forwarding is set up, click Manage, delete the forward and save.
  3. Next to Advanced DNS Records, click Manage.
  4. Delete existing A, AAAA and CNAME records for @ and www. Keep MX and other TXT records.
  5. Add an A record: name @, value 3.33.236.10.
  6. Add a TXT record: name @, value from your dashboard.
  7. Add a CNAME record: name www, value from your dashboard, then save.

Only change A, AAAA and CNAME records for the root and www: your email (MX) and other TXT records keep working as before.

Step 4: Wait for Connected and HTTPS#

RedirHub checks the records automatically. Changes are often picked up within minutes but can take up to 24 hours, depending on the TTL of the old records. When the domain shows Connected, the redirect is live, and the SSL certificate status changes to Secured shortly after.

Step 5: Test the redirect#

Open your domain in a private browser window and check the homepage, a deeper page and the www version, over both http:// and https://. If something doesn't work yet, see Troubleshooting new redirects or how long DNS changes take.

Frequently asked questions

No. Your domain and DNS stay at Network Solutions. You only change the records for the root domain and www.

No. Delete the Web Forwarding entry before changing the DNS records, otherwise it keeps pointing the domain at Network Solutions' forwarding servers.

Yes. You only replace A, AAAA and CNAME records for the root domain and www. MX records and other TXT records, such as SPF, stay as they are.

No. The root domain redirect also covers www, as long as www points to RedirHub with the CNAME record. Add www separately only if it should go somewhere else.

Usually minutes, sometimes up to 24 hours while the old DNS records expire. RedirHub detects the change automatically and then issues the SSL certificate.

Related help

View All Articles