Use Google Mail (Google Workspace) as your mail server
Point your domain’s MX records to Google so Gmail / Google Workspace handles mail while the domain stays on CR Servers DNS or hosting.
This guide is for a domain registered or hosted with CR Servers when the mailboxes live in Google Workspace / Google Mail, not in the mailbox quotas on our hosting. You keep DNS (or hosting) with us and send mail through Google.
Point mail at Google
- Create or verify the domain in Google Workspace (or Google’s mail setup for the product you bought).
- In the client area DNS zone (or at the registrar, if DNS is not on our nameservers), set the MX records Google publishes for that domain. Replace any MX that still pointed at our mail servers.
- Publish the TXT verification record Google asks for, if the console still needs to prove you control the domain.
- Update SPF so it includes Google’s current
include:value. Use the string Google documents today — do not copy an old include from a blog post. Our SPF article covers mail that still leaves from CR Servers hosting; a Google-only setup should follow Google’s SPF, not both as conflicting TXT records. - Wait for DNS TTL, then send a test message both ways (into Google and out to an external inbox).
Plan the cutover
When you remove our MX, mailboxes that still exist on CR Servers hosting for that domain stop receiving. Move or forward those addresses in Google first, then change MX.
Authentication after the move
For Google-originated mail, enable DKIM in Google’s wizard (not our hosting control panel) and publish the TXT record Google shows. Then add a DMARC TXT policy for the domain.
If you stay on our mail instead of Google, do not replace the MX. Use IMAP / POP3 setup and our DKIM howto for mail that still leaves from CR Servers hosting.