Email Setup Wizard

Google Workspace + OVHcloud

Set up Google Workspace email on OVHcloud

The records Google Workspace needs, written with the field names OVHcloud uses (Subdomain, Target, Value), in the order to add them.

  • 5 steps
  • 5 DNS records
  • Sources checked October 21, 2026

Before you start

  1. Have your Google Workspace account ready. Some values are unique to your account and come from the Google Admin console.
  2. Open DNS at OVHcloud: Sign in to the OVHcloud Control Panel (ovh.com/manager). Under View all my activity, select your domain name. Open the DNS zone tab.
  3. Keep both tabs open and add the records below one at a time.

Records to add

Copy each value with the button next to it. Rows marked “Copy from Google Admin console” are unique to your account.

Domain verification Proves you own the domain Type TXT Subdomain Leave empty Value Copy from Google Admin console Looks like: google-site-verification= followed by your unique code Priority n/a TTL Default
MX records Where incoming email goes Type MX Subdomain Leave empty Value smtp.google.com. Priority 1 TTL Default
SPF record Which servers may send as you Type TXT Subdomain Leave empty Value v=spf1 include:_spf.google.com ~all Priority n/a TTL Default
DKIM A signature on every message Type TXT Subdomain google._domainkey Value Copy from Google Admin console Priority n/a TTL Default
DMARC record What to do with fakes · recommended Type TXT Subdomain _dmarc Value v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com Priority n/a TTL Default

Step by step in OVHcloud

Verify your domain

Your email provider needs proof that you control this domain before it accepts email for it.

Type
TXT
Subdomain
Leave this field empty
Value
Copy it from Google Admin console (see below)

Where to find your value

In the Google Admin console go to Menu > Account > Domains > Manage domains, click Verify domain, then Get started. In the TXT record section, copy the Value, including google-site-verification=.

It looks like: google-site-verification= followed by your unique code

  • Leave the host blank or enter @.
  • Once Google has verified the domain, this TXT record can be safely removed. Removing it earlier makes verification fail.
  • It can take up to 72 hours for a new TXT record to be recognized.

In OVHcloud

  1. Select the Add an entry tile.
  2. In Extended records, choose TXT.
  3. Fill in Subdomain (empty for your bare domain) and Value.
  4. Select Next, then Confirm.

Point your MX records

MX records tell every other mail server where to deliver email for your domain. They must point to your provider and nowhere else.

Type
MX
Subdomain
Leave this field empty
Priority
1
Target
smtp.google.com.
  • Remove any other MX records. Email might not work correctly if old or incorrect MX records stay in place.
  • Some domain hosts need a trailing period: smtp.google.com.
  • Accounts that started before 2023 may use older values beginning with aspmx. Those are still supported, so there is no need to change working records.
  • For TTL, use your domain host's default.

In OVHcloud

  1. Select the Add an entry tile.
  2. In Mail records, choose MX.
  3. Leave Subdomain empty, enter the Priority and the Target (ending with a dot), and a TTL.
  4. Select Next, then Confirm.
  5. Delete older MX records with the trash icon in the Actions column.

Add the SPF record

SPF is a TXT record that lists the services allowed to send email from your domain, so receivers can spot forgeries.

Type
TXT
Subdomain
Leave this field empty
Value
v=spf1 include:_spf.google.com ~all
  • This is the record for domains that send email only through Google Workspace.
  • If other services also send email for your domain, list each one in the same record, for example: v=spf1 include:_spf.google.com include:amazonses.com ~all.
  • Google recommends ~all at the end of the record.

In OVHcloud

  1. Select the Add an entry tile.
  2. In Extended records, choose TXT.
  3. Fill in Subdomain (empty for your bare domain) and Value.
  4. Select Next, then Confirm.

Set up DKIM

DKIM publishes a public key so receivers can confirm your messages really came from you and were not changed on the way.

Type
TXT
Subdomain
google._domainkey
Value
Copy it from Google Admin console (see below)

Where to find your value

In the Google Admin console go to Menu > Apps > Google Workspace > Gmail and click Authenticate email. Select your domain, generate a new record (2048-bit if your domain host supports it, otherwise 1024-bit) and copy the TXT record value.

  • google is Google's default selector, so the host is google._domainkey.
  • Wait 24 to 72 hours after turning on Gmail before generating the key.
  • Some domain hosts limit TXT record length. If the 2048-bit key will not fit, generate a 1024-bit key instead.
  • After the record is published, go back to Authenticate email and turn on authentication for the domain.

In OVHcloud

  1. Select the Add an entry tile.
  2. In Extended records, choose TXT.
  3. Fill in Subdomain (empty for your bare domain) and Value.
  4. Select Next, then Confirm.

Add the DMARC record (recommended)

DMARC tells receivers what to do with mail that fails SPF and DKIM, and where to send reports about it.

Type
TXT
Subdomain
_dmarc
Value
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com
  • Start with p=none so nothing is blocked while you read the reports. Google suggests running it for about a week.
  • Replace the report address with a mailbox or group you actually check. Google advises against a personal inbox.
  • Then tighten gradually, for example v=DMARC1; p=quarantine; pct=5; rua=mailto:dmarc@{domain}, raising pct over time.
  • Set up SPF and DKIM first. Google recommends 48 hours of authentication before turning on DMARC.

In OVHcloud

  1. Select the Add an entry tile.
  2. In Extended records, choose TXT.
  3. Fill in Subdomain (empty for your bare domain) and Value.
  4. Select Next, then Confirm.

Check your setup

Once the records are saved, run a live check. We look up your domain in public DNS and tell you what is right, missing or wrong, with the fix in OVHcloud’s words.

We only read public DNS records. Nothing is stored.

Common mistakes with Google Workspace on OVHcloud

Leaving old MX records in place

Google says email might not work correctly if old or incorrect MX records stay. Remove every MX record except smtp.google.com.

Adding a second SPF record

A domain must have only one SPF record. If you already have one, add include:_spf.google.com to it instead of creating another.

Generating the DKIM key too soon

Google asks you to wait 24 to 72 hours after turning on Gmail before generating the DKIM key.

Publishing DKIM but not turning it on

Adding the TXT record is only half the job. Go back to Authenticate email in the Admin console and turn on authentication.

Deleting the verification record too early

Removing the google-site-verification record before Google confirms the domain makes verification fail.

OVHcloud: End targets with a dot

By default OVHcloud treats a target without a final dot as relative and adds your domain to the end. End MX and CNAME targets with a dot, for example mx1.example.com.

Visit Google Workspace Visit OVHcloud

Rather have someone do it for you?

Tell us your domain and we will add and verify every record for Google Workspace on OVHcloud, then send you the check results.

Request done-for-you setup

Google Workspace on OVHcloud: questions

Where do I add Google Workspace DNS records in OVHcloud?

Sign in to the OVHcloud Control Panel (ovh.com/manager). Under View all my activity, select your domain name. Open the DNS zone tab. Add each record there, one at a time.

What goes in the Subdomain field at OVHcloud?

Leave it empty for records on your bare domain, such as MX and SPF. For the others, enter only the part before your domain, for example google._domainkey. OVHcloud adds your domain automatically.

Do I need to delete my existing MX records at OVHcloud?

Remove any other MX records. Email might not work correctly if old or incorrect MX records stay in place. By default OVHcloud treats a target without a final dot as relative and adds your domain to the end. End MX and CNAME targets with a dot, for example mx1.example.com.

Where do I get my Google Workspace DKIM record?

In the Google Admin console go to Menu > Apps > Google Workspace > Gmail and click Authenticate email. Select your domain, generate a new record (2048-bit if your domain host supports it, otherwise 1024-bit) and copy the TXT record value.

How long until Google Workspace email works on OVHcloud?

New MX records can take up to 72 hours to be recognized.

Sources

Every value and step on this page comes from these official pages. Dashboards change, so if something doesn’t match what you see, tell us.

Google Workspace on other hosts

Other email providers on OVHcloud