This page will serve as a guide to setting up Google Apps on your domain and account.
Important note: Google Apps doesn't allow .tk domains.
Configuring Your MX Records
The steps below explain how to create MX records for a domain managed using cPanel.
To create MX records using cPanel:
- Log in to cPanel.
To log in, go to https://your-domain-name/cpanel replacing your-domain-name with the full name of your domain.
- From the Mail section of the page, select MX Entry.
- In the Email Routing box, select Remote Mail Exchanger and click Change.
- Add an MX record for the primary email server in the Destination text box.
The primary email server for Google Apps is the first server in the table of Google Apps email servers. Enter the fully qualified server name, such as ASPMX.L.GOOGLE.COM.
- Set the priority for the MX record.
MX records with a lower number have higher priority than MX records with a higher number. To use the new email server as the primary server, give it the lowest possible priority number (0).
- Click Add New Record.
- To add MX records for the additional servers, repeat steps 4 to 6 for those servers.
Give backup servers a lower priority than the primary email server.
Delete any existing MX records, or lower their priority.
- For now, we recommend that you keep all existing MX records, but lower their priority. Later, once you have tested your service and confirmed mail flow, you can delete these records to ensure that mail flows through the new mail server(s).
To delete an MX record or change its priority, click the Delete or Edit link in the row of the MX records table.
We recommend that you create a Sender Policy Framework (SPF) record for your domain. An SPF record is a type of Domain Name Service (DNS) record that identifies which mail servers are permitted to send email on behalf of your domain.
The purpose of an SPF record is to prevent spammers from sending messages with forged From addresses at your domain. Recipients can refer to the SPF record to determine whether a message purporting to be from your domain comes from an authorized mail server.
For example, suppose that your domain example.com uses Gmail. You create an SPF record that identifies the Google Apps mail servers as the authorized mail servers for your domain. When a recipient's mail server receives a message from email@example.com, it can check the SPF record for example.com to determine whether it is a valid message. If the message comes from a server other than the Google Apps mail servers listed in the SPF record, the recipient's mail server can reject it as spam.
If your domain does not have an SPF record, some recipient domains may reject messages from your users because they cannot validate that the messages come from an authorized mail server.
To create an SPF record for a domain:
- Log in to cPanel.
- Go to Email Authentication.
- Enable SPF (If not enabled already)
- Go to Additional Ip blocks for your domains (IP4) and the only thing in there should be:
- Go to Include List (INCLUDE) and the only thing in there should be:
- Check: All Entry (ALL)
- Check: Overwrite Existing Entries
- Click Update
- Above Advanced Settings the raw SPF should look exactly like:
Your current raw SPF record is : v=spf1 a mx ip4:126.96.36.199 include:_spf.google.com -all
Keep in mind that changes to DNS records may take up to 48 hours to propagate throughout the Internet. If you have difficulty creating an SPF record, post on the Forums.
A CNAME record is what you need to setup if you want to access one of your Google Apps via your domain name. For example you would need to setup a domain name to access your email from http://email.your-domiain.com .
To setup your CNAME:
- Log in to cPanel
- Go to Simple DNS Zone Editor
- Select your domain and go down to Add an CNAME Record
- Under Name put whatever you want to use to go to one of your google apps (Example: Put in email to access your email via http://email.your-domiain.com )
Note: putting mail in this field is restricted by the system.
- Under CNAME put:
- Click Add CNAME Record
Your CNAME record is now configured to point to Google. Keep in mind that changes to your DNS settings may take up to 48 hours to propagate throughout the Internet.