Every registered domain name has at least two Name Server records which show where it is hosted i.e. by using these records you point your domain name to the servers of a particular website hosting provider. This way, you've got both your site and your emails handled by the same provider. On the lower level of the Domain Name System (DNS), on the other hand, there are lots of other records, for instance A and MX. The former shows which server handles the site for a given Internet domain and is always an IP address (123.123.123.123), while the latter indicates which server deals with the emails and is always an alphanumeric string (mx1.domain.com). As an illustration, whenever you enter a domain name in your web browser, your request is directed through the global DNS system to the provider whose NS records the domain address uses and from there you may be directed to the servers of a different company provided you have set an IP address of the latter as an A record for your domain address. Having different records for the site and the e-mails means that you could have your website and your e-mails with two different companies if you'd like.

Custom MX and A Records in Cloud Web Hosting

If you have a Linux cloud web hosting package from our company, you are going to be able to see, set up and change any A or MX record for your domains. Assuming that a specific Internet domain has our Name Servers, you are going to be able to to modify particular records via our Hepsia hosting CP and have your site or emails pointed to another provider if you wish to use only one of our services. Our leading-edge tool is going to enable 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 domain name the slightest bit. If you want to use the e-mail services of a different company and they want you to set up more than two MX records, you can easily do that with just a few clicks within the DNS Records section of your CP. You can also set different latency for each MX record i.e. which one is going to have priority.