The definition of “hosting” doesn't describe one service, but a variety of services which provide numerous functions to a domain name. Having a site and e-mails, for example, are two separate services though in the general case they come together, so most of the people consider them as one single service. In reality, each and every domain has a number of DNS records called A and MX, which show the server that manages each specific service - the former is a numeric IP address, which defines where the site for the domain address is loaded from, while the second one is an alphanumeric string, which shows the server that handles the e-mails for the domain name. As an example, an A record can be 123.123.123.123 and an MX record would be mx1.domain.com. Every time you open a site or send an e-mail, 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. When you have custom records on their end, the web browser request or the email will then be sent to the correct server. The idea behind employing separate records is that the two services work with different web protocols and you could have your site hosted by one service provider and the e-mails by another.

Custom MX and A Records in Cloud Hosting

The Hepsia hosting Control Panel, that comes with each and every cloud hosting which we provide, will permit you to view, change and set up A and MX records for every domain or subdomain in your account. Using the DNS Records section, you'll be able to view a list of all hosts within the account from a to z with their related records, so any update won't take you more than a couple of mouse clicks. Setting up new records is as simple if, as an example, you would like to use the email services of a different service provider and they ask you to create more MX records than the default two. You can also set the priority for every MX record by setting different latency. To put it differently, when your e-mails are delivered, the sending server is going to contact the record with the smallest latency first and if the connection times out, it'll contact the next one. Through our state-of-the-art tool, you'll be able to handle the records of your domain addresses and subdomains easily even when you have no previous experience with such matters.