Creating a CNAME record for any of the domain addresses or subdomains you've got within a hosting account will permit you to direct it to a different domain/subdomain. The forwarded domain name will lose all its records - A, MX etc, and will take the records of the domain name it's being forwarded to. In this light, you simply can't create a CNAME record to redirect your domain name to a third-party company and retain a working e-mail service with the first provider. Also, it is important to note that a CNAME record is always a string of words and not a number as it's generally mistaken for the A record of the Internet domain being redirected. One of the primary uses of a CNAME record is to direct a domain that you own through one provider to the servers of some other provider assuming you have created a site with the latter. That way, the Internet site will appear under your own domain name, not under some subdomain provided by the third-party company.
CNAME Records in Shared Web Hosting
Setting up a CNAME record using our shared web hosting is extremely easy. Our in-house built Hepsia Control Panel features a section devoted to the DNS records of your domain addresses, so you can set up a new CNAME record for any domain or subdomain hosted within your account in a couple of easy steps. You'll find a video tutorial inside the same section in which you can see the process first-hand. This feature provides you with many possibilities - if you build a company site on our end, for instance, the staff can use their emails with the company domain, not with the address of our mail server. If you decide to create an Internet site by using a different company that offers online web design services, you can easily forward a domain hosted here and use it for the site. Last, but not least, if you have a web-based store and you have a billing system for http://your-domain.com and/or an SSL certificate, you'll be able to set up a CNAME record for the www subdomain and direct it to the main domain name, so all your customers are going to be forwarded to a secure URL.