The definition of “hosting” doesn't describe a particular service, but several services that offer different functions to a domain. Having a website and e-mails, as an illustration, are two individual services though in the general case they come together, so a lot of people see them as one single service. The truth is, every domain name has a couple of DNS records called A and MX, which show the server that manages each particular service - the first one is a numeric IP address, which defines where the website for the domain is loaded from, while the second one is an alphanumeric string, which shows the server that handles the e-mails for the domain. For instance, an A record can be and an MX record would be Each time you open a website or send an email, the global DNS servers are contacted to check the name servers that a Internet domain has and the traffic/message is first forwarded to that company. If you have custom records on their end, the Internet browser request or the e-mail will then be sent to the correct server. The concept behind working with separate records is that the two services use different web protocols and you could have your site hosted by one company and the emails by another.
Custom MX and A Records in Cloud Hosting
If you have a cloud plan through our company, you'll be able to see, set up and change any A or MX record for your domain names. Provided that a given domain has our Name Servers, you'll be able to modify certain records by using our Hepsia hosting CP and have your site or emails directed to any other company if you wish to use only one of our services. Our innovative tool will allow you to have a domain hosted here and a subdomain below it to be hosted somewhere else by changing only its A record - this will not affect the main Internet domain at all. If you decide to use the e-mail services of another provider and they want you to set up more than 2 MX records, you can easily do it with simply a few clicks within the DNS Records section of your Control Panel. Also you can set different latency for each MX record i.e. which one is going to have priority.