Creating MX Records for Google Apps through the Cloud Control Panel


In this article we discuss adding Google Apps MX records to a domain managed via the New Cloud Control Panel.

DNS

If you haven't already, be sure you verify your domain with Google Apps through their administrative interface.

Once Google has successfully verified the domain the next step will be to add Google’s MX records to the domain's information in the DNS section of the New Cloud Control Panel.

MX

Google Apps provides five MX records to be added to the domain DNS settings.  You can find the latest MX record values on the Google Apps web site.

Once you have the MX records in-hand you'll want to add the records in the New Cloud Control Panel.

If you need help finding the screen to add a record to a domain we have an article with more details for our New Cloud Control Panel.

Once we're on the "Add DNS Record" screen we should be able to fill in the necessary information for each record. Let's have a look at the interface in the new control panel:

As in the example above, you'll need to select "MX Record" as the record type to create a Mail Exchanger record for inbound email. Start with the first record on Google's list, which at the time of this writing is ASPX.L.GOOGLE.COM, and assign the priority Google recommends for that record (the number listed before the domain name on Google's table of MX entries).

Don't include a period at the end of the mailserver domain when you enter it. The system will add that for you behind the scenes if it's required.

Once you're done entering the first MX record repeat the process for the other four MX records.

Check and Test

Now that the MX records have been stored within the DNS settings for your domain, the changes should propagate after the time specified in the TTL has passed. You can test your changes with a DNS checker or using a Terminal to run the dig command.

You can install and use dig by following the instructions in this article.  To use dig to just check the MX records for the domain you can run the command:

dig -t MX greprest.com

The results should look something like:

;; QUESTION SECTION:
;greprest.com.INMX

;; ANSWER SECTION:
greprest.com.300INMX5 alt2.aspmx.l.google.com.
greprest.com.300INMX10 aspmx2.googlemail.com.
greprest.com.300INMX10 aspmx3.googlemail.com.
greprest.com.300INMX1 aspmx.l.google.com.
greprest.com.300INMX5 alt1.aspmx.l.google.com.

Now that we can see the MX records have propagated correctly we can run an email test.

Send an email through the Google Apps webmail interface to an email address you can access on a different domain, then reply to it. If the email to your domain gets back to Google Apps you'll know the DNS changes worked.

Summary

Google Apps allows for email service using your own domain for free, which can be useful when deciding whether to host email with an email hosting provider or run your own email environment.

This process is relatively simple to follow and can take up to around 10 minutes to complete, making it an easy way to get email up and running when you’re in a hurry.



Was this content helpful?




© 2014 Rackspace US, Inc.

Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License


See license specifics and DISCLAIMER