The definition of “hosting” doesn't describe a particular 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 even though in the general case they come together, so most people consider them as one single service. Actually, each domain has a number of DNS records called A and MX, which show the server that deals with each specific service - the first one is a numeric IP address, that identifies where the site for the domain is loaded from, while the second one is an alphanumeric string, which shows the server that deals with the emails for the domain name. For instance, an A record can be and an MX record is Whenever 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 directed to that company. If you have custom records on their end, the web browser request or the e-mail will then be sent to the correct server. The reasoning behind employing separate records is that the two services work with different web protocols and you can have your website hosted by one service provider and the emails by another.
Custom MX and A Records in Cloud Website Hosting
The Hepsia hosting Control Panel, that comes with each and every Linux cloud website hosting we provide, will permit you to view, change and create A and MX records for each domain name or subdomain inside your account. Using the DNS Records section, you are going to be able to see a list of all hosts within the account in alphabetical order with their related records, so any update is not going to take you more than a couple of clicks. Creating new records is just as simple if, as an illustration, you would like to use the e-mail services of another service provider and they ask you to create more MX records than the default 2. Additionally you can set the priority for every single MX record by setting different latency. To put it differently, when your emails are delivered, the sending server will contact the record with the smallest latency first and if the connection times out, it'll contact the next one. Using our state-of-the-art tool, you are going to be able to manage the records of your domains and subdomains effortlessly even though you may have no prior experience with such matters.