When clients are ready to set up their email:
When messages like this come in, it is important to get them the information as soon as possible! This is priority #1 for support. We are providing them with this service, so when they are ready, we need to get them up and running immediately.
So first thing you should do is pull up their website in MCP and see if they have been approved!
If they have been approved, we have this lovely macro in zendesk that will provide them with the pertinent information. Edit the message so it is relevant to what they ask specifically, and send that message over to them!
If they haven’t been approved, slack Victoria or Lida asking if they are approved.
It’s also very important to understand how Name Servers and MX records work, you can find this information in the Miscellaneous section.
To add in mx records via MCP, go to:
MCP > Choose Their Site > go to the Server Settings tab
Scroll down to Dns Records and select the Email they have chosen.
Here are the options:
- No Email Records (set as default)
- 1and1 (don't think anyone has this one)
- rackspace (don't do this anymore..pretty sure)
- godaddy (yes)
- google (yes)
- godaddyExchange (really rare)
So, the main two that are used from this list are godaddy (the regular one) and Google (now called G-Suite)
(If the client wants office 365, you will need to go into AWS and add them in manually. Scroll down to see the most common mx records to add in AWS)
Click Save! Then find their site in MCP again, check the box, and select Syncdns from the drop down menu and click Go. It will take a few moments to process. Wait for it to finish and send them an email saying you set their MX records and that they should test it out, sending and receiving email. We have a macro in Zendesk for this too.
Types of (common) MX records
Before we begin, here are examples of records that should never be added:
A * 162.209.66.24 1 Hour Edit
A @ 162.209.66.24 600 seconds Edit
CNAME ftp @ 1 Hour Edit
CNAME www @ 1 Hour Edit
- Godaddy
If you are not able to sync in MCP, here are the MX records you can add to aws for the following (Bold = Name):
Tables can't be imported directly. Please insert an image of your table which can be found here.
CNAME RECORDS:
mail ghs.google.com
TXT RECORD:
"v=spf1 include:_spf.google.com ~all"
Tables can't be imported directly. Please insert an image of your table which can be found here.
(this one has many DNS records to add)
SRV RECORDS:
_sipfederationtls._tcp 100 1 5061 sipfed.online.lync.com
_sip._tls 100 1 443 sipdir.online.lync.com
CNAME RECORDS:
autodiscover autodiscover.outlook.com
sip sipdir.online.lync.com
lyncdiscover webdir.online.lync.com
email email.secureserver.net
msoid clientconfig.microsoftonline-p.net
enterpriseregistration enterpriseregistration.windows.net
enterpriseenrollment enterpriseenrollment-s.manage.microsoft.com
MX RECORD
0 huntsvillehomenetwork-com.mail.protection.outlook.com
(you would change huntsvillehomenetwork to the domain name of the site)
TXT RECORD
"v=spf1 include:spf.protection.outlook.com -all"
There should also be another TXT record for verifying.
(this one has many DNS records to add)
SRV RECORDS:
_sipfederationtls._tcp 100 1 5061 sipfed.online.lync.com
_sip._tls 100 1 443 sipdir.online.lync.com
CNAME RECORDS:
autodiscover autodiscover.outlook.com
sip sipdir.online.lync.com
lyncdiscover webdir.online.lync.com
MX RECORD
0 huntsvillehomenetwork-com.mail.protection.outlook.com
(you would change huntsvillehomenetwork to the domain name of the site)
TXT RECORD
"v=spf1 include:spf.protection.outlook.com -all"
There should also be another TXT record for verifying.
- Type: MX | Host: @ | Points to: mx1.privateemail.com | Priority: 10 | Leave the default value in the TTL field
- Type: MX | Host: @ | Points to: mx2.privateemail.com | Priority: 10 | Leave the default value in the TTL field
- Type: TXT | Host: @ | TXT Value: v=spf1 include:spf.privateemail.com ~all | Leave the default value in the TTLfield.
- Type: CNAME | Host: mail | Points to: privateemail.com | TTL: default
- Type: CNAME | Host: autoconfig | Points to: privateemail.com | TTL: default
- Type: CNAME | Host: autodiscover | Points to: privateemail.com | TTL: default
Notes: If someone sends you dns records that have the "@", it means that the record doesn't need a name (don't add the @ either).
Sometimes users will give us incomplete MX records, or not provide all of the information.
In the case of e-mails working previously or on other domains we can look to the history of a domain's nameservers using this tool: http://whoisrequest.com/history/
From here, you'll be using the dig command in your Terminal on that nameserver you just viewed the history of.
An example of its use is:
"dig @oldnameservers.com example.com mx"
Internet magic!