Any time you add a domain name as hosted in some account, you usually set a pair of Name Servers to point it to that specific service provider. On their end, three records are created automatically when the domain address is added - one A record and two MX records. The former is a numeric address, or IP address, which “tells” the domain name where its site is, while the other two are alphanumeric and they show the server that manages the emails for that specific Internet domain. The website and the email hosting are usually thought to be one thing, when they're in reality two different services. Having different records for them will permit you to have them with different providers if you want. As an illustration, some new service provider can have fantastic uptime for your site, but you might not want to switch your e-mails from your current host and by employing an A record to point the domain to the first and MX records to have the e-mails with the second, you can get the best of both companies. These records are checked whenever you want to open a website or send an e-mail - in either case, the company whose name servers are used for the domain will be contacted to retrieve the A and MX records and if you have set records different from their own, the correct web/mail server will then be contacted and you're going to see the needed website or your email will be delivered.

Custom MX and A Records in Cloud Hosting

If you have a cloud hosting account from our company and you want to move either your site or your emails to another company, it'll take you literally only two mouse clicks to do so. Our Hepsia CP offers an easy-to-use DNS Records tool, where all your domains and subdomains will be listed alphabetically and you will be able to see and modify the A and/or MX records for any of them. If you choose to use a different email provider and they ask you to create more MX records than the default two, it will not take more than a few mouse clicks either to add them. You could also set different latency for these records and the lower the latency, the higher the priority a particular MX record is going to have. The propagation of each record that you change or create isn't going to take more than several hours and if necessary, you will also be able to set the so-called Time-To-Live value, that reveals how long a record will stay active after it is changed or deleted.