How do I connect my domain to Google Workspace?
Add Google's verification code as a TXT record on the DNS tab, click Google Workspace under Quick setup on the Email tab for the MX and SPF records, then add the DKIM key on the DNS tab once Google has made it. Each value comes from the Google Admin console.
Publisert 15. november 2026
Les denne på norskThree steps, in the order Google asks for them. First, prove the domain is yours: add Google's verification code as a TXT record on the domain's DNS tab. Then send your mail to Google: on the Email tab, click Google Workspace under Quick setup, which puts in Google's MX record (smtp.google.com, priority 1), removes the other MX records and adds Google to your SPF record. Last, sign your mail: once Google has made your DKIM key, add it as a TXT record on google._domainkey on the DNS tab. We have no link to your Google account, so you copy each value from the Google Admin console and confirm each step there.
Before you start
- A Google Workspace account with your domain added, and access to the Google Admin console. For DKIM, Google says you must be a super administrator.
- The domain uses our nameservers, ns1.sedes.no to ns4.sedes.no. If it does not, the Email and DNS tabs say at the top: "This domain uses other nameservers than ours. Records you save here have no effect until the domain uses our nameservers. You can change them under Nameservers." Until then, the records belong wherever the domain's DNS is run now.
- You are the holder (the person or organisation the domain is registered to), or an administrator of the organisation that holds it. Anyone else is turned away at Apply and needs the holder to make the change.
- Mail already arrives somewhere else? Google's advice is to create your users in the Google Admin console before you change the MX record, and to make the change when little mail is coming in.
1. Prove the domain is yours (the TXT record)
If Google is already showing you a value starting with google-site-verification=, copy it and skip ahead to the Sedes part below.
In the Google Admin console, go to Menu > Account > Domains > Manage domains, click Verify domain, then Get started. If Sedes is not in Google's list of registrars, choose My domain uses a different host. Copy the TXT value, including google-site-verification=.
In your Sedes account:
- Log in at app.sedes.no, open Domains and click the domain.
- Open the DNS tab and click New record. The new row starts as type A with an empty host.
- Set Host to
@(the domain itself), Type toTXT, and paste Google's value into Data, without quotation marks. Leave TTL as it is. - Click Save 1 change. Review changes lists the record under Added. Click Apply 1 change.
Nothing changes in your DNS until you click Apply; Save only shows you the changes. From here on we call the buttons just Save and Apply.
Back in Google, click Come back here and confirm..., then Confirm.
The saved record is listed under Advanced, not Simple. It must stay until Google has verified the domain; removing it earlier makes the verification fail. Once the domain is verified, Google says the record can be safely removed.
Google then offers Activate Gmail. In Google's order the MX record comes first, so leave that click for the end of step 2.
2. Send your mail to Google (MX and SPF)
- On the domain's page, open the Email tab.
- On the Quick setup row, click Google Workspace. A new MX row appears:
@, priority 1,smtp.google.com.. Other MX rows on@are struck through; you can bring each back until you save. Quick setup adds the SPF record too, but this table lists only MX records, so you first see it in Review changes. - Click Save. On a domain with no mail records yet, it reads Save 2 changes.
- In Review changes, check that MX and SPF are under Added and any old MX rows under Removed. An SPF record the domain already had shows twice: its old value under Removed, its new one under Added. Click Apply.
Quick setup does only this: MX and SPF.
Back in Google: if the tab from step 1 is still offering Activate Gmail, click it there. Otherwise go to Menu > Account > Domains > Manage domains and click Activate Gmail for the domain.
3. Sign the mail you send (DKIM)
Not on day one. Google says you must wait 24 to 72 hours after turning on Gmail before you can get your DKIM key; earlier, you may get an error that the DKIM record was not created.
In the Google Admin console, go to Menu > Apps > Google Workspace > Gmail, click Authenticate email and select the domain. Click Generate New Record, choose 2048 as the key length, keep the prefix (selector) as google, as Google recommends, and click Generate. Copy the TXT record value, a long string starting with v=DKIM1; k=rsa; p=. Do not click Start authentication yet; Google says not to.
In your Sedes account, open the DNS tab and click New record. Set Host to google._domainkey, without your domain after it, Type to TXT, and paste the whole value into Data, exactly as Google shows it. Save, then Apply.
Back in Google, open Authenticate email, select the domain and click Start authentication. When it works, the status reads "Authenticating email with DKIM". The console may show "You must update the DNS records for this domain" for up to 48 hours; with the key added, Google says you can ignore it in the meantime.
To test it, send a message to someone on Gmail or Google Workspace (Google says a message to yourself can't show it), open it with More > Show original and look for DKIM=pass.
DMARC (optional)
A TXT record on _dmarc, added on the DNS tab. Google's advice is to wait until SPF and DKIM have authenticated your mail for at least 48 hours, and to start with p=none.
The records
… stands for the code or key Google gives you.
| Step | Host | Type | Prio | Data | Who adds it |
|---|---|---|---|---|---|
| Verify | @ | TXT | google-site-verification=… | You, DNS tab | |
| Receive mail | @ | MX | 1 | smtp.google.com. | Quick setup |
| SPF | @ | TXT | v=spf1 include:_spf.google.com ~all, or Google's include added to your existing SPF | Quick setup | |
| DKIM | google._domainkey | TXT | v=DKIM1; k=rsa; p=… | You, DNS tab | |
| DMARC (optional) | _dmarc | TXT | for example v=DMARC1; p=none | You, DNS tab |
- TTL: leave it at 3600, the app's default. Google's MX page says to use the registrar's default or enter 1, but we don't accept a TTL below 60.
- One SPF record: Google's rule is one per domain, listing every service that sends mail for you. Quick setup keeps the senders already in yours and merges two SPF records into one. The DNS tab does not warn you about a second one added by hand.
- smtp.google.com or aspmx? A domain that started on Google Workspace before 2023 may use Google's older
aspmxMX records. Google says that if your mail works, no change is needed, and that any account can usesmtp.google.com. Quick setup replaces the older records with it.
Will I lose email when I switch?
Not if the domain has no email yet: a domain newly registered with us has no mail records, so there is nothing to lose or remove.
If mail already arrives somewhere else, Google says it keeps going to your previous provider until the new MX record is active, so for a while some can still land there. Mail already in the old mailbox stays there: changing DNS does not move it.
How long does it take?
Our nameservers answer with the new records as soon as you click Apply. DNS servers that cached an older answer catch up after that; the DNS propagation panel on the DNS tab shows what they answer now.
At Google, in Google's own words:
- Verification: "It can take up to 72 hours for the new TXT records to be recognized." Once the record is active, "it can take up to one hour for us to confirm you added the record, but it usually happens quickly."
- MX: "It can take up to 72 hours for the new MX records to be recognized."
- SPF: "It can take up to 48 hours for SPF authentication to start working."
- DKIM: "it can take up to 48 hours for DKIM authentication to start working."
When it doesn't work
Google can't find the TXT record
On the DNS tab, under Advanced, check that a TXT record on @ holds the whole google-site-verification=… value, and that the Nameservers tab lists ns1.sedes.no to ns4.sedes.no. Allow Google's 72 hours, then click Confirm again. If verification still fails and the record is there, email hei@sedes.no with the domain name.
Google won't accept the MX record, or Gmail won't activate
Google activates Gmail only once the domain is verified (step 1); if it isn't yet, see "Google can't find the TXT record" above.
On the Email tab, the only MX row on @ should be smtp.google.com.; Google says mail might not work correctly with old MX records kept. Delete any other row with its ✕, then Save and Apply. Check the Nameservers tab as above, and the DNS propagation panel on the DNS tab. Allow Google's 72 hours, then try Activate Gmail again. Still failing? Email hei@sedes.no with the domain name.
Mail still arrives at the old provider
Either an old MX row is still there (check the Email tab as above), or the change has not reached everyone yet (see Will I lose email when I switch?). If Google's row is the only one and mail still goes astray after Google's 72 hours, email hei@sedes.no with the domain name.
Mail you send lands in spam, or Google says SPF is wrong
On the DNS tab, under Advanced, there should be exactly one TXT record on @ starting with v=spf1, and it should contain include:_spf.google.com. If there are two, or Google's include is missing, click Google Workspace under Quick setup on the Email tab again, then Save and Apply. If it still fails after Google's 48 hours, email hei@sedes.no with Google's error message.
DKIM isn't working
If Google still reports a problem after 48 hours, or Start authentication does not take: on the DNS tab, under Advanced, check that google._domainkey holds the whole value, exactly as Google gave it. Google's Admin Toolbox Dig shows what the internet sees: look up the TXT record for google._domainkey.yourdomain.no. Google says the key may come back in two parts, which is fine if every character is there, in the right order. Then click Start authentication again. If the value is there and Google still reports it missing or broken, email hei@sedes.no with the domain name.
Apply is refused
The message reads "Only the domain’s holder can save changes. If the holder is an organisation, an administrator of that organisation can do it." Ask the holder, or an administrator of the organisation that holds the domain, to make the change. If you are the holder and still see it, email hei@sedes.no.
If the app says it could not save the changes, and that happens again when you try, email hei@sedes.no.
How this actually works
The domain is the address; the mailbox is at Google. Four records connect them. The verification TXT proves to Google that you control the domain. MX tells other mail servers to deliver your mail to Google. SPF says Google's servers may send mail for your domain. DKIM signs what you send, so receivers can check it came from you.
All four live in your domain's DNS, which we run on ns1.sedes.no to ns4.sedes.no. Google only reads them, which is why each step ends back in the Google Admin console, where Google checks for itself.
More on MX priority: What is an MX record, and what does the priority number do? Record types, TTL and propagation: Your domain's DNS settings, explained. Another email provider: How do I get email on my domain?
Sources: Google Workspace help on verifying a domain, MX records, SPF and DKIM, read 15 November 2026.