A Mail Exchanger (MX) record in the DNS system specifies a mail server responsible for accepting email addresses on behalf of a domain.
The MX records associated with a domain assure that the email is properly routed via Simple Mail Transfer Protocol (SMTP).
If you haven't created a zone for your domain, then refer to this article.
You should already have the base records shown here: Click on the 'new record' link.
Alternatively, you can install the tools on a member server to run Exchange 2013 Active Directory preparation.
For Windows Server 2008 R2 (SP1 or later), in Power Shell run: For other Active Directory preparation scenarios, such as multiple forests or multiple domains, refer to this article on Tech Net.
Then I went to DNS Manager and clicked on Edit Zones under my domain name. Just hit the Quick Add button in the "A (host)" section and add these records...
In my case, I already had a www record there that was setup by default.
Namely, from what they say it's impossible to migrate to them without email downtime.
So even if you set up everything on Go Daddy's side, the email account's status will still show "Pending Setup: validating MX record" for quite a while, rejecting all incoming email.
After updating nameservers, the website will be accessible very quickly, but all email will be rejected with e.g.: "188.1_does_not_like_recipient./Remote_host_said:[email protected]/Giving_up_on_188.1./" It seems as though the account won't accept any email until it "receives" the correct MX records from a domain, and they say it can take up to 48 hours (which is especially absurd especially as they be both registrar and provider in this case). But the catch was - GD will be showing "Pending Setup: validating MX record" before you update nameservers for a domain, and afterwards as well.
I know from past experience that a correctly performed migration should never incur any downtime at all (providing you set everything up at the new provider, only then update domain's nameservers, and only in a few days cancel the old provider's account).
Apparently, their (email) account's setup is tied to MX records of domain's nameservers, making it impossible for a seamless transition.
Firstly we need to create a subdomain A Record called 'mail'. Again, if you are using an external mail agency, then skip this step.