Connect Google Workspace
Verify your domain, route email to Gmail, and authenticate outgoing mail without disturbing your website.
Open your domain’s DNS
- Sign in to your SaaSTech Servers Domain Portfolio External · opens new tab ↗.
- Select the individual domain to open its Domain Settings page.
- Select DNS.
Need help signing in? Find your username or password External · opens new tab ↗.
Confirm the account and back up DNS
Sign in to the Google Admin console as an administrator. Complete the DNS backup guide before adding or replacing records.Open Google AdminExternal · opens new tab ↗Back Up Your DNSSaaSTech guide →
Verify domain ownership
In Account → Domains → Manage domains, start verification. Add the unique TXT value Google provides (usually beginning google-site-verification=), then return to Google and select Verify. Verification itself does not change your website or email.Google domain verification helpExternal · opens new tab ↗Add a TXT record in SaaSTech DNSExternal · opens new tab ↗
Prepare every mailbox
Create users, aliases, groups, and routing rules before changing MX. Confirm that every address currently receiving mail has a destination in Google Workspace.
Route mail to Google
In DNS, remove old or incorrect MX records only when the mail cutover is approved. Add the current Google MX record shown below, save it, then activate Gmail in the Admin console.Google MX setup helpExternal · opens new tab ↗Add an MX record in SaaSTech DNSExternal · opens new tab ↗
Authenticate outgoing mail
Publish one SPF record that includes every legitimate sender. Generate DKIM in Apps → Google Workspace → Gmail → Authenticate email, publish Google’s unique TXT key, then start authentication. Add DMARC after SPF and DKIM are passing.Google SPF helpExternal · opens new tab ↗Google DKIM helpExternal · opens new tab ↗Add a TXT record in SaaSTech DNSExternal · opens new tab ↗
Test and monitor
Send mail to and from an external account, inspect message authentication results, confirm aliases and groups, and monitor through the previous TTL period. DNS recognition can take time, so avoid repeated edits.Check mail records with MXToolboxExternal · opens new tab ↗
MX record for new setups
| Type | Host | Priority | Destination | TTL |
|---|---|---|---|---|
| MX | @ or blank | 1 | smtp.google.com | Provider default |
Some DNS providers require a trailing period. Older working Google Workspace accounts may use legacy ASPMX records; Google says they remain supported, so do not replace a working configuration merely to modernize it.
One record only
v=spf1 include:_spf.google.com ~allUse this only when Google is the sole sender. Merge other legitimate senders into the existing SPF record; never create a second SPF record.
Official SPF guide ↗Unique to your domain
google._domainkeyCopy the full host and value generated in your Admin console. After publishing, return to Google and start authentication.
Official DKIM guide ↗