Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

301 redirect dns record – How we fix its errors?

by | Feb 17, 2021

301 redirect DNS record method is ideal if you want to redirect one website traffic to another permanently in the same server.

They are permanent redirects that can be done through DNS records. Moreover, this type of redirect is highly recommended for SEO ranking.

At Bobcares, we receive requests regarding 301 redirect creation and its errors as a part of our Server Management Services for web hosts and online service providers.

Today, let’s see how our Support Engineers create the 301 redirects and fix their issues.

 

How to create a 301 redirect DNS record?

Now, let’s see how we can create a 301 redirect by adding the DNS records.

We add the below DNS record to create a redirect from example1.com to example2.com.

example1.com. IN A x.x.x.x
www.example1.com IN CNAME example2.com.

 

Common errors related to 301 redirect DNS record

Now let’s see some of the common errors that are related to 301 redirects.

 

1. Incorrect DNS

For any website to load successfully, it should have correct DNS records. Sometimes, few customers do make some mistakes in updating the right DNS records.

Entering a wrong DNS record will lead to failure in loading a website in the browser.

So our Support Engineers initially check for the right DNS records and then update them accordingly. Updating the correct record will fix the website redirect issue.

Recently, one of our customers approached us telling us that the website redirect isn’t working well. When checked, we found that the A record of the domain was pointing to an IP whereas the CNAME record for www was pointing to another website. This redirect actually doesn’t work. Below is an example of how the record looked:

example.com. IN A x.x.x.x
www IN CNAME example2.com.

We updated the record with the right ones and they are as below.

example.com. IN A x.x.x.x
www.example.com IN CNAME example2.com.

This ensures that when the example.com website is called, it will be redirected to example2.com.

 

2. Implementing two redirect methods Omission of anyone redirect method

We can create 301 redirects either via DNS records or via the .htaccess file. However, we can follow only one method to create the redirect.

In case if both the methods are implemented then the website will throw an error “Too many Redirects”.

If the customer is using two methods to create the redirect then we must remove one among them.

We can simply delete the .htaccess file which contains the redirect rule or else we can only remove the redirect rule present in the .htaccess file.

By doing this, the redirect will initiate only from the DNS records and no redirect methods fluctuate.

[Still, experiencing issues with 301 redirect DNS record? We’ll help you in fixing it]

 

Conclusion

In short, we must create the redirects carefully, so that we don’t lose the traffic. 301 redirect DNS records are the best method that we can implement for achieving a good redirect. Today, we saw what the 301 redirect DNS record is and what are some of its common errors and fixes.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF