You can use a NameUK .co.uk domain with Google Workspace without moving the registration to another provider. Prepare the Google Workspace account and required mailboxes, verify the domain, review the email records at the active DNS host and activate Gmail. NameUK has a Google Workspace preset for domains using our managed nameservers. Existing email needs a migration plan before changing its MX records.
Before you begin
- Prepare the Google Workspace account and all required receiving addresses.
- Identify the active DNS host and save the existing records before editing.
- Verify ownership with the account-specific value supplied by Google.
- Review MX and SPF conflicts before applying the NameUK preset.
- Activate Gmail, configure authentication and test website and email separately.
1. Prepare the mailbox service before routing messages
A domain registration gives you the name for its selected term; it does not create Google Workspace users or inboxes. Set up the Workspace service and decide who needs an independent mailbox, an alias or another supported receiving arrangement. Confirm the required addresses before directing incoming mail away from any existing provider.
Keep a secure administrator contact you can already access. If you are setting up the domain’s first mail service, an address on that unconfigured domain cannot be your only working contact route. Record who controls the registrar account and the mail administrator account, and protect both through their supported sign-in controls.
2. Identify where DNS changes take effect
Open the domain’s own page in the NameUK dashboard and check its nameservers. The DNS controls apply when NameUK managed nameservers are active. If the domain uses an external DNS host, make the changes at that host instead. Adding records to an inactive zone will not connect the mailboxes people are trying to reach.
Save a DNS snapshot or other reliable record of the current settings. Identify website records, existing mail routing and authentication values before making a proposal. Connecting a new email service does not normally require moving the website or changing nameservers; avoid combining separate changes unless you have a complete migration plan.
3. Treat verification, delivery and authentication separately
Google can ask for a unique TXT value to establish control of the domain. Copy the complete value from your own administrator account and complete the verification there after publishing it. That verification step does not itself create a receiving mailbox or prove that outgoing mail is authenticated.
Use the following checklist to keep the tasks separate. It describes the purpose of each part, not a replacement for the account-specific instructions or a reason to delete existing records. Other legitimate verification TXT records may still be needed.
On a narrow screen, swipe to read every column.
| Task | Purpose | Confirm separately |
|---|---|---|
| Domain verification | Shows control to the service | Google accepts your account’s verification value |
| MX routing and activation | Directs incoming messages | Gmail is active and intended addresses receive mail |
| SPF and DKIM | Supports sender authentication | Legitimate sending services are included and signing is active |
| Mailbox migration | Preserves older messages | Required history is available in the intended account |
4. Review the NameUK Google Workspace preset
In the DNS section, choose “Connect a website or email provider”, select the email option and then Google Workspace. The current preset proposes Google’s standard new-connection MX record and a Google-only SPF policy. You can supply the Google verification value and the public DKIM record name and value when those are available. Review the proposed rows before applying them.
The preset uses smtp.google.com with MX priority 1. Google still supports older aspmx-based configurations, so a working older setup is not automatically wrong. Compare the proposal with your own instructions and existing zone. Do not replace records just to make them look like another account’s screenshot.
NameUK stops the preset when existing mail routing or SPF conflicts require a decision. It does not automatically migrate old mail or combine several senders into one policy. If that happens, retain the current records and ask for a reviewed change plan. Keep website A, AAAA and CNAME records and unrelated TXT records intact.
5. Complete sending authentication and plan any migration
SPF should describe all authorised senders in a single policy for the relevant name. If website forms, invoices or a newsletter service also send mail, the Google-only starter value may not describe your whole setup. Do not add a second SPF policy beside the first or remove a legitimate sender without checking its role.
For DKIM, publish the public record supplied by Google and complete the activation in Google Admin. The public DNS value is different from a private signing key or an account password. Follow the current provider guidance for DKIM and a suitable DMARC rollout; a record being saved is not proof that every outgoing message is signed and aligned correctly.
Consider a hypothetical two-person studio moving email while its portfolio stays with the same website host. It prepares both users and needed aliases, arranges the message-history migration and agrees a time to switch mail routing. It keeps the old service available while checking the transition, and leaves website records unchanged. Merely changing MX does not copy the old inboxes.
Sources: IETF: Sender Policy Framework ↗ · IETF: DomainKeys Identified Mail ↗
6. Test receiving, replying and the existing website
Return to Google Admin to complete the required domain checks and Gmail activation. Test a message from an independent external mailbox to each important receiving address, then send a reply. Check aliases or shared arrangements explicitly rather than assuming that a working personal inbox proves every business address is ready.
Inspect the provider’s authentication results for outgoing messages and check that your website still loads at its usual address. DNS caches can retain previous answers for a time, but a visible wrong value should be corrected through the agreed plan rather than dismissed as a waiting problem. If a result is unclear, note the time, affected address and error without sharing passwords or private keys.
- The domain is verified and Gmail is active.
- Expected users and aliases receive external messages.
- Replies use the intended address and authentication works.
- Old messages needed by the team are accessible.
- The website and other domain-connected services still work.
7. Keep the domain renewal separate from Workspace
Register .co.uk for £9.99 for one year, with annual renewal currently £9.99. Or choose a new three-year .co.uk registration for £25.99. Check the selected name and term before payment. Future renewal prices can change.
NameUK’s current .co.uk registration and renewal amounts appear below. The initial three-year domain offer does not include three years of Google Workspace, mail storage or migration work. Keep the domain expiry and the mailbox subscription’s payment schedule as separate responsibilities, and compare the current service costs before committing.
For buyers wanting a standalone UK domain, visible annual renewal pricing and DNS controls for an independently chosen email provider, we recommend considering NameUK. This is our own recommendation for those needs, not an independent ranking of email services. Choose the mailbox plan for the people and features you actually need, and retain the registration for as long as those addresses matter.
This is NameUK’s own setup guide, checked against Google’s current administrator instructions and our existing DNS preset. Use the values issued to your account. Illustrations are conceptual; the worked example is hypothetical. No affiliation or endorsement is implied.
Further readingIETF: Sender Policy Framework ↗IETF: DomainKeys Identified Mail ↗Extension rules and provider processes can change. Check the current registrar instructions before a registration, transfer or renewal.
Low-cost registration. Affordable UK renewals.
Register .co.uk for £9.99 for one year, with annual renewal currently £9.99. Or choose a new three-year .co.uk registration for £25.99. Check the selected name and term before payment. Future renewal prices can change.