The word “hosting” doesn't describe only one service, but several services that offer various functions to a domain name. Having a site and emails, for instance, are two independent services despite the fact that in the general case they come together, so many people think of them as one single service. In fact, every single domain name has a couple of DNS records called A and MX, which show the server that deals with each particular service - the first one is a numeric IP address, that defines where the site for the domain is loaded from, while the latter is an alphanumeric string, which shows the server that manages the emails for the domain. For example, an A record is 123.123.123.123 and an MX record can be mx1.domain.com. Each time you open a website or send an e-mail, the global DNS servers are contacted to check the name servers that a domain address has and the traffic/message is first forwarded to that company. When you have custom records on their end, the browser request or the e-mail will be directed to the correct server. The reasoning behind using separate records is that the two services use different web protocols and you may have your site hosted by one company and the emails by another.
Custom MX and A Records in Shared Website Hosting
If you have a shared website hosting plan through us, you are going to be able to see, create and change any A or MX record for your Internet addresses. As long as a given Internet domain has our Name Servers, you are going to be able to to change certain records by using our Hepsia hosting CP and have your website or emails pointed to any other company if you want 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 someplace else by changing only its A record - this will not affect the main domain at all. If you choose to use the e-mail services of a different service provider and they want you to create more than 2 MX records, you can easily do that with only a few mouse clicks within the DNS Records section of your CP. You may also set different latency for every MX record i.e. which one is going to have priority.