The word “hosting” does not describe a particular service, but several services which offer different functions to a domain name. Having a website and e-mails, as an example, are two independent services although in the general case they come together, so most of the people consider them as one single service. In fact, every domain name has a couple of DNS records called A and MX, which show the server that manages each specific service - the first one is a numeric IP address, that identifies where the site for the domain address is loaded from, while the latter is an alphanumeric string, which shows the server that deals with the e-mails for the domain name. For example, an A record can be 123.123.123.123 and an MX record would be mx1.domain.com. Every 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 directed to that company. If you have custom records on their end, the Internet browser request or the email will then be forwarded to the correct server. The idea behind employing separate records is that the two services employ different web protocols and you could have your website hosted by one company and the e-mails by another.
Custom MX and A Records in Shared Hosting
The Hepsia hosting CP, that comes with each and every Linux shared hosting package which we provide, will enable you to see, modify and set up A and MX records for any domain name or subdomain inside your account. Using the DNS Records section, you're going to be able to view a list of all hosts inside the account from a to z with their corresponding records, so any update will not take you more than a couple of clicks. Setting up new records is equally easy if, for example, you want to use the e-mail services of a different service provider and they ask you to set up more MX records than the default two. You can even set the priority for each MX record by setting different latency. To put it differently, when your emails are delivered, the sending server is going to contact the record with the smallest latency first and in case the connection times out, it's going to contact the next one. Through our sophisticated tool, you are going to be able to manage the records of your domains and subdomains with ease even if you have no previous experience with such matters.