The definition of “hosting” does not describe a particular service, but a set of services that provide a variety of functions to a domain name. Having a website and emails, for instance, are two independent services although in the general case they come together, so most of the people see them as one single service. Actually, every single domain name has a couple of DNS records called A and MX, which show the server that manages each particular service - the former is a numeric IP address, that specifies where the website for the domain is loaded from, while the latter is an alphanumeric string, which shows the server that deals with the emails for the domain. 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 website or send an email, the global DNS servers are contacted to check the name servers that a domain has and the traffic/message is first forwarded to that company. In case 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 using 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 emails by another.

Custom MX and A Records in Shared Website Hosting

The Hepsia hosting CP, that comes with each and every Linux shared website hosting package we offer, allows you to see, change and set up A and MX records for every 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 in alphabetical order with their corresponding records, so any update isn't going to take you more than a couple of clicks. Creating new records is as simple if, for instance, you wish to use the e-mail services of another service provider and they ask you to set up more MX records than the default two. You can also set the priority for each MX record by setting different latency. Quite simply, 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. With our innovative tool, you are going to be able to manage the records of your domains and subdomains effortlessly even though you may have no previous experience with such matters.