About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Google will not treat the domain as yours until it finds the verification TXT record from the Admin console, and other people's mail will not arrive at Gmail until the domain's MX records name Google's mail host. The MX help page gives the Google Workspace MX record value smtp.google.com. Priority is 1. The name is blank or @. The same page says that if you started before 2023, "your domain might have different MX record values that start with "aspmx"", that those legacy values "are still supported", and "If your email is working, no changes are required."
The older hostnames are not printed, only the prefix "aspmx". If mail already works on those records, leave them. A published host that is neither smtp.google.com nor a working legacy value starting with "aspmx" is not the MX set Google describes.
What has to be true
Verification and MX are separate records. Add "a unique text (TXT) record" so that "no one else uses your domain with Google Workspace". Copy the value, including "google-site-verification=". The sample value is google-site-verification=abcdef123_456wx789yz. The name is blank or @. "The unique TXT record must stay in your domain's DNS settings until Google detects it and verifies ownership." Removing it early "will cause the verification to fail." "Once verified, the TXT record can be safely removed."
When you add Google's MX record, "Your email might not work correctly if you keep old or incorrect MX records." Some registrars want smtp.google.com. Recognition "can take up to 72 hours". "Before you can set up Gmail, you need to verify ownership for your domain or subdomain." The Admin console path is Menu, Account, Domains, Manage domains, which needs the Domain settings administrator privilege. If the registrar is not listed, select "My domain uses a different host."
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| The verification TXT is missing, mistyped, or was removed too early | The Admin console says the domain could not be verified | dig TXT and look for google-site-verification= |
| MX points at a former mail host | Mail never reaches Gmail, or still arrives at the old server | dig MX is not smtp.google.com and does not start with aspmx |
| Legacy MX is already working | Mail is delivered, and the hosts start with aspmx |
"If your email is working, no changes are required." |
| Extra MX records were left beside Google's | Old or incorrect MX records remain | More than smtp.google.com, or a second provider still listed |
| The domain is not verified, so Gmail activation will not proceed | Google's help says "Before you can set up Gmail, you need to verify ownership for your domain or subdomain." | The TXT value is not in DNS yet |
Prove the cause before changing anything
The form is dig @server name type. MX and TXT are query types. Save the replies from the nameserver that holds the zone, not only from a recursive resolver:
dig @ns1.example.net example.com TXT > /root/txt-example.com-2026-11-22.txt
dig @ns1.example.net example.com MX > /root/mx-example.com-2026-11-22.txt
In the saved MX reply, the hostname to compare is smtp.google.com. Ignore a trailing dot if the reply or the registrar prints one: some registrars require smtp.google.com. Priority on that record is 1. A hostname that starts with aspmx, with mail already flowing, is the legacy case where Google says no changes are required. Any other hostname does not match smtp.google.com.
In the TXT reply, look for the value you copied, including the prefix google-site-verification=. Copy the value exactly.
Fix
Ownership has to be verified before Gmail, so the TXT record comes first. Before either change, the two saved replies, /root/txt-example.com-2026-11-22.txt and /root/mx-example.com-2026-11-22.txt, hold the records as they stand now.
Risk: Adding the verification TXT publishes that token. Do not delete other TXT records while you add it. An SPF record is also TXT, and removing it changes who may send mail for the domain. Removing the verification TXT before Google verifies causes verification to fail.
In the Admin console, open Menu, Account, Domains, Manage domains. Choose Verify domain, then Get started, and copy the Value, including google-site-verification=. At the DNS host, add a TXT record. Leave the name blank or use @. Paste the value. Save. Wait until dig shows the record. Google allows up to 72 hours. Return to the same Admin console user, select "Come back here and confirm...", and click Confirm.
To undo the TXT change: if you have not verified yet and you want to stop, delete only the TXT record you added. Removing it before verification fails the check, which is what you want only when you are abandoning verification. After Confirm succeeds, the TXT record can be removed.
The MX change applies only when the saved reply is not smtp.google.com and is not a working legacy host that starts with aspmx.
Risk: Replacing MX records sends the domain's incoming mail to the host you publish. Google says to remove other MX records, and that old or incorrect ones can stop mail working. Recognition can take up to 72 hours. If mail already works on legacy aspmx records, do not make this change: "If your email is working, no changes are required."
Add one MX record: name blank or @, priority 1, value smtp.google.com (or smtp.google.com. if the registrar requires the trailing dot). Remove the other MX records.
To undo the MX change: put the MX records from /root/mx-example.com-2026-11-22.txt back, and remove the smtp.google.com record if it was not in that file. Mail follows the restored hosts after their TTL.
Activating Gmail is a separate change, made only after the domain is verified.
Risk: In Menu, Account, Domains, Manage domains, Activate Gmail starts Gmail set-up for the domain you choose. Google's page gives no reverse step for it, so check the domain name on screen before you click.
Click Activate Gmail and follow the steps on screen. There is no back-out step for this click.
Confirm the fix
dig example.com TXTshows the verification value until Google has verified. After that, the TXT record can be removed.- The Admin console reports the domain verified. If it does not, a message says the domain could not be verified.
dig example.com MXshowssmtp.google.comat priority 1, or the untouched legacy hosts that start withaspmx.- Activate Gmail has been clicked for that domain. MX recognition can still take up to 72 hours.
What to watch afterwards
- Leave working legacy MX records in place.
- Add the verification TXT. Do not replace the rest of the TXT set.
- A subdomain uses its own name in the host field, such as
supportforsupport.example.com.
Read next
Related articles you may want next.
- TroubleshootingGoogle Workspace SPF: the record must include include:_spf.google.comGoogle Workspace mail fails SPF. Publish one TXT record containing include:_spf.google.com, keep a single v=spf1 record, and recount lookups before you add senders.Read article
- TroubleshootingGoogle Workspace SMTP relay: 5.7.0 Email relay deniedGoogle Workspace SMTP relay returns 5.7.0 Email relay denied when the sender is not registered. Register the public IP or use SMTP authentication on smtp-relay.gmail.com.Read article
- HostingApplication Email Rejected or Junked After a Server Move: SPF, DKIM, DMARC and PTRApplication mail bouncing or junked after a migration? Read Authentication-Results, then fix SPF, DKIM, DMARC alignment, PTR and Microsoft 365 relay settings for the new path.Read article
Risks and limits
- Google's MX help prints the hostname
smtp.google.com. It describes older values only as starting with "aspmx", and it does not print those older hostnames. - Both help pages say up to 72 hours. A lookup at the authoritative server shows when the record is actually published.
- The console path is Menu, Account, Domains, Manage domains. It needs the Domain settings administrator privilege.
Sources
- Set up MX records for Google Workspace — Google Workspace Help, last updated 2026-11-10 UTC, accessed 22 November 2026
- Verify your domain with a TXT record — Google Workspace Help, last updated 2026-11-10 UTC, accessed 22 November 2026
- BIND 9.18.44 manual pages: dig — ISC, no date shown, accessed 22 November 2026
This article was originally published on .