Every single registered domain has no less than 2 Name Server records which show where it's hosted i.e. by using these records you point your domain address to the servers of a certain website hosting provider. In this way, you have got both your website and your e-mails handled by the same provider. On the lower level of the Domain Name System (DNS), nevertheless, there is a variety of other records, for instance A and MX. The former shows which server manages the website for a given domain and is always an IP address (123.123.123.123), while the latter indicates which server manages the emails and is always an alphanumeric string (mx1.domain.com). For instance, whenever you enter a domain in your Internet browser, your request is directed through the global DNS system to the provider whose NS records the domain uses and from there you could be directed to the servers of another provider in case you have set an IP address of the latter as an A record for your domain. Having different records for the website and the e-mails means you can have your website and your e-mails with 2 different providers if you would like.
Custom MX and A Records in Cloud Web Hosting
If you have a Linux cloud web hosting through us, you will be able to see, set up and modify any A or MX record for your Internet addresses. So long as a specific domain name has our Name Servers, you will be able to change certain records by using our Hepsia hosting Control Panel and have your website or emails directed to any other provider if you would like to use only one of our services. Our leading-edge tool will even permit you to have a domain address hosted here and a subdomain below it to be hosted elsewhere by modifying only its A record - this will not affect the main Internet domain the slightest bit. If you choose to use the e-mail services of a different service provider and they want you to create more than two MX records, you can easily do it with just a few clicks through the DNS Records section of your Control Panel. Also you can set different latency for each MX record i.e. which one will have priority.