Google Workspace MX setup (Generic steps)

Modified on Thu, 08 Sep 2022 at 02:01 PM

Note: If people already have email with your domain (such as user@your-company.com), create their user accounts in the Google Admin console before you set up your MX records. That way, they’ll continue to receive email.

 

  1. Sign in to your domain's account at your domain host.      

    Need help? Contact your domain host’s Support team. Domain hosts are experts with MX records, and setup is a common task.

  2. Go to the section where you can update your domain’s MX records. It might be called something like "DNS Management," “Mail Settings,” or "Advanced Settings."
  3. Delete any existing MX records.
          If you can’t delete the existing records, change their priority number to 20 or higher.
  4. Add new MX records for the Google mail servers.      

    If your domain host limits the number of MX records, just add the first 2 records in this table.

          Values for Google Workspace MX records                                                                                                                                                                                                                                                                                                                                                       
    Name/Host/AliasTime to Live (TTL*)Record TypePriorityValue/Answer/Destination
    @ or leave blank3600MX1ASPMX.L.GOOGLE.COM
    @ or leave blank3600MX5ALT1.ASPMX.L.GOOGLE.COM
    @ or leave blank3600MX5ALT2.ASPMX.L.GOOGLE.COM
    @ or leave blank3600MX10ALT3.ASPMX.L.GOOGLE.COM
    @ or leave blank3600MX10ALT4.ASPMX.L.GOOGLE.COM
         

    Notes: Some domain hosts use different labels for the name and value fields. Some hosts require a trailing period at the end of the server name.

  5. Save your changes.      

  6.         

    Skip this step if you already verified your domain by another method (such as TXT or CNAME record).

    If you need to verify your domain:

    1. In the Admin console, scroll to the Get your verification code section and click the Copy button.

      The MX records table is shown and a red circle highlights the Copy button next to the MX verification record.
    2. Paste the value in the Value/Answer/Destination/Target column.
    3. Make sure the record's priority is set to Low or to 15 or greater.
    Note: If your registrar rejects the verification code, try deleting the period at the end of .com.
           
  7. Open the setup tool in the Admin console.

         

    A red circle highlights the "Activate." option in the Gmail section.

  • In the Gmail section, click Activate

    

  • Verify that you've created all existing email addresses and are ready for Gmail to start receiving all email for your domain. Click Continue.

    

  • On the next page,  scroll to the bottom of the page and click Activate Gmail.

         

    A red circle highlights the Activate Gmail button on the bottom right of the MX records table.

  1. Typically, you can send and receive messages at your new Google Workspace email address in less than 6 hours. However, it may take 48–72 hours before you receive email at your new address. It’s no fun to wait, but the time for MX records to take effect depends on your domain host. We have no control over this. In the meantime, you can get your email messages at your old email client. 

To start using Gmail

  1. Sign in to admin.google.com with your Google Workspace user name and password. 
  2. In the top right corner, click the App Launcher "" and then Mail "".

Set up Gmail security

We recommend you enable email authentication and security methods for Gmail.

Best practices for email authentication

We recommend you always set up these email authentication methods for your domain:

  • SPF lets servers verify that messages appearing to come from a particular domain are sent from servers authorized by the domain owner.
  • DKIM adds a digital signature to every message. This lets receiving servers verify that messages aren't forged, and weren't changed during transit.
  • DMARC enforces SPF and DKIM authentication, and lets admins get reports about message authentication and delivery.
For detailed steps, go to Help prevent spoofing, phishing, and spam.

 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article