Every single registered domain has no less than two Name Server records which show where it is hosted i.e. by using these records you point your domain address to the servers of a specific website hosting company. That way, you've got both your website and your e-mails managed by the very 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 name and is always an IP address (123.123.123.123), while the latter indicates which server handles the e-mails and is always an alphanumeric string (mx1.domain.com). For instance, any time you enter a domain address in your browser, your request is forwarded through the global DNS system to the provider whose NS records the domain address uses and from there you may be forwarded to the servers of another provider in case you have set an IP address of the latter as an A record for your domain name. Having different records for the website and the emails suggests that you can have your site and your emails with two different companies if you wish.
Custom MX and A Records in Cloud Website Hosting
If you have a cloud website hosting service through us, you'll be able to view, create and modify any A or MX record for your domain names. So long as a specific Internet domain has our Name Servers, you're going to be able to modify particular records through our Hepsia hosting CP and have your site or emails pointed to any other company if you would like to use only one of our services. Our leading-edge tool is going to permit you to have a domain address hosted here and a subdomain below it to be hosted someplace else by changing only its A record - this will not affect the main domain the slightest bit. If you choose to use the e-mail services of another service provider and they want you to set up more than two MX records, you can easily do this with only a few mouse clicks through the DNS Records section of your CP. You can even set different latency for every single MX record i.e. which one is going to have priority.