Every single registered domain name has at least two Name Server records that show where it's hosted i.e. by using these records you point your Internet domain to the servers of a specific hosting provider. This way, you have both your website and your emails handled by the exact same company. On the lower level of the Domain Name System (DNS), nevertheless, there are a number of other records, such as A and MX. The former reveals which server handles the site for a given domain and is always an IP address (123.123.123.123), while the second one indicates which server handles the emails and is always an alphanumeric string (mx1.domain.com). For instance, when you type a domain address in your web browser, your request is forwarded through the global DNS system to the company whose NS records the domain name uses and from there you may be sent to the servers of a different company provided you have set an IP address of the latter as an A record for your domain name. Having separate records for the website and the e-mails means that you could have your website and your emails with two different providers if you wish.

Custom MX and A Records in Cloud Website Hosting

If you have a cloud website hosting plan from our company, you are going to be able to view, create and modify any A or MX record for your domain names. So long as a particular domain name has our Name Servers, you're going to be able to change particular records via our Hepsia hosting CP and have your website or emails pointed to another company if you would like to use only one of our services. Our state-of-the-art tool will permit you to have a domain address hosted here and a subdomain below it to be hosted somewhere else by modifying only its A record - this will not affect the main Internet domain at all. If you decide to use the email services of another provider and they want you to set up more than 2 MX records, you can easily do it with simply a couple of mouse clicks through the DNS Records section of your Control Panel. Also you can set different latency for every MX record i.e. which one is going to have priority.