Setting up a CNAME record for each of the domain addresses or subdomains that you have in the hosting account will permit you to direct it to a different domain/subdomain. The forwarded domain will lose all of its records - A, MX and so on, and will take the records of the domain address it is being directed to. In this light, you simply can't set up a CNAME record to direct your domain to a third-party company and maintain a functional e-mail service with the first hosting company. Additionally, it is essential to know that a CNAME record is always a string of words rather than a number as it is frequently confused with the A record of the Internet domain being forwarded. One of the main uses of a CNAME record is to forward a domain name that you own through one provider to the servers of some other provider when you have set up a website with the latter. By doing this, the website will appear under your own domain address, not under some subdomain provided by the third-party company.

CNAME Records in Web Hosting

Creating a CNAME record through our web hosting is very simple. Our in-house built Hepsia CP has a section committed to the DNS records of your domains, so you can set up a new CNAME record for any domain or subdomain hosted in your account in only a few easy steps. You'll find a video tutorial within the same section in which you can see the process first-hand. This feature gives you various options - if you build a company site on our end, as an illustration, the staff can use their emails with the company domain, not with the address of our mail server. If you wish to create an Internet site by using a different company which offers online web design services, you can easily redirect a domain hosted here and use it for the website. Last, but not least, in case you have a web-based store and you have a billing system for http://your-domain.com and/or an SSL certificate, you are able to create a CNAME record for the www subdomain and direct it to the main domain, so all your customers are going to be forwarded to a secure URL.

    • Our ID: 175441