To use an address such as [email protected] in Gmail, set it up through Google Workspace: verify that you control the domain, point its mail-delivery DNS record (MX) to Google, then activate Gmail. After incoming mail works, configure SPF, DKIM, and DMARC so receiving services can authenticate messages sent from your domain.
What you need before you start
- A Google account that can administer Google Workspace.
- Login access to the company or registrar that manages your domain’s DNS records. DNS controls may be separate from the website builder where you made your creator site.
- A list of every service that will send email using your domain: Google Workspace, newsletter tools, website contact forms, and other automations. SPF must account for all authorized senders.
- A note of your current MX records and any existing email provider. Replacing mail routing can interrupt an existing mailbox if you do not plan the change.
Google Workspace is Google’s documented route for using Gmail with a custom domain. Google says adding the domain-verification record takes about 10 minutes, but that is an estimate, not a guarantee for every DNS provider. Verification itself does not affect your existing email or website. Google’s domain verification instructions explain the process.
Set up Gmail for your domain
1. Verify domain ownership
- Sign up for Google Workspace and follow its domain setup flow.
- When asked to verify the domain, choose the provided verification method and copy the record values Google gives you.
- Sign in to the service managing your DNS, add the verification record exactly as shown, and return to Workspace to complete verification.
DNS provider interfaces use different labels and layouts. Follow the instructions for your provider, and do not substitute a mail-routing record for the separate verification record. See Google’s DNS basics if you need to distinguish record types.
2. Point incoming mail to Google
An MX record tells other mail systems where to deliver messages for your domain. Google’s current Workspace instructions specify this MX record:
#1 Best Overall
| DNS field | Value |
|---|---|
| Host or name | Blank or @ for the root domain, depending on your DNS provider |
| Type | MX |
| Priority | 1 |
| Destination or value | smtp.google.com |
| TTL | Your provider’s default or 1, as Google specifies |
Use the format your DNS provider expects. If you are moving from another email service, first identify any existing MX records and plan for the change; remove old or incorrect MX entries when replacing them with Google’s records. Then activate Gmail in the Google Admin console. Google says new MX records can take up to 72 hours to be recognized. Follow Google’s MX setup instructions.
3. Test incoming and outgoing mail
- Send a message from an outside email account to your new address, such as
[email protected]. - Reply from the new address and check that the recipient sees your custom-domain address, not a personal Gmail address.
- If either direction fails, confirm that domain verification is complete, the MX record is spelled and placed correctly, and no conflicting MX records remain.
To see which MX records are publicly visible, Google points administrators to the Admin Toolbox Dig tool through its MX troubleshooting guidance. Check the published DNS records before changing settings again.
Rank #2
Authenticate messages you send
Receiving mail and authenticating mail you send are separate parts of setup. Google recommends SPF, DKIM, and DMARC. They help receiving services check whether messages using your domain are authorized; they do not guarantee inbox placement.
SPF: list authorized senders
SPF is a DNS TXT record that identifies services allowed to send email for your domain. If Google Workspace is your only sender, Google’s example value is:
v=spf1 include:_spf.google.com ~all
If a newsletter platform, website contact form, or another service also sends as your domain, include that sender according to its setup instructions. Do not publish multiple SPF records for the same domain. Google says SPF can take up to 48 hours to start working. See Google’s SPF setup instructions.
DKIM: sign outgoing messages
DKIM adds a signature to outgoing messages. Receiving systems can check that signature against a public key published in your DNS. In Google Workspace, generate the DKIM key in the Admin console, publish the TXT record Google provides at your DNS host, then turn on and verify DKIM in the Admin console.
Rank #4
- Choose a 2048-bit key if your DNS provider supports it; Google allows a 1024-bit key if it does not.
- After Gmail is enabled, you may need to wait 24–72 hours before Workspace lets you generate the key.
Use the exact selector and TXT value generated for your account. Google’s DKIM instructions cover key generation and verification.
DMARC: publish a policy for your domain
DMARC builds on SPF and DKIM and tells receiving systems how to handle messages that fail authentication checks. Google recommends configuring it. Choose a policy appropriate to your sending setup and make sure your legitimate senders are accounted for before enforcing a stricter policy; a misconfigured policy can affect valid mail.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Google’s sender requirements, which began February 1, 2024, require senders sending more than 5,000 messages per day to Gmail to configure SPF, DKIM, and DMARC. The high-volume rules also include alignment requirements for direct mail and one-click unsubscribe for marketing or subscribed mail. That threshold is not a reason for smaller senders to ignore authentication. Consult Google’s current email sender guidelines for the requirements that apply to your sending pattern.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot common setup problems
Mail still goes to the old provider or does not arrive
- Check the published MX record. Confirm the host, destination, and priority match Google’s instructions and that the record applies to the root domain.
- Look for old or conflicting MX entries. A prior email host’s records can send mail elsewhere; remove obsolete records as part of a planned migration.
- Allow for DNS recognition. Google says new MX records can take up to 72 hours to be recognized.
- Confirm Gmail is activated. Adding DNS records and activating Gmail in the Admin console are distinct steps.
Messages you send fail authentication or land in spam
- Make sure SPF authorizes every service sending for your domain and that there is only one SPF record.
- Check that the DKIM TXT record is published exactly as generated and that DKIM has been turned on and verified in Workspace.
- Review DMARC alignment and policy against your actual senders. A legitimate newsletter or website service omitted from SPF or DKIM can fail checks.
- Allow the stated propagation time: Google says SPF can take up to 48 hours to start working, and DKIM key generation may require a 24–72-hour wait after Gmail activation.
The DNS screen does not match Google’s examples
Providers may call the same fields “name,” “host,” “points to,” or “destination,” and may represent the root domain as a blank field or @. Use your provider’s guidance for its interface while preserving the exact record type and values Google supplies.
Or let it run in the cloud
If your creator site also has a YouTube channel that needs to keep prerecorded videos live around the clock, StreamNeo is a separate service for that task—not an email or website-hosting service. Upload a recording or build a playlist, add your YouTube stream key once, and go live. StreamNeo loops the uploaded video from the cloud, so nothing has to stay on at home. It streams the uploaded file as made, up to 4K 60fps, at one price per slot; it automatically recovers if YouTube drops the stream. The first day is free with no card. Monthly pricing is $9.99 per month. Learn more at StreamNeo, or start the free day.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
