Can you use two email providers on one .co.uk domain?

1. First decide what two providers should do

There are several different requests hidden inside this question. You might want some staff on one service and others on another. You might want the same person to receive a copy in two inboxes during a migration. Or you may only need an extra address that lands in an existing mailbox. Those arrangements need different controls.

Write down the outcome in plain language before buying licences. Include shared addresses such as accounts and enquiries, who replies, and whether old messages need moving. If everyone can use one service with suitable aliases or shared mailboxes, a second provider may add administration without solving a real problem.

2. MX priority does not assign a provider to each person

MX records identify receiving mail servers for a domain. Their numerical preference helps senders choose which server to try; lower numbers are preferred. They do not contain a list saying which employee belongs at which provider. Equal preferences do not create a deliberate employee-by-employee split either.

Suppose the preferred service does not recognise a particular recipient. Do not assume the sender will then deliver that person’s message to your other provider. A rejection is different from a temporary connection failure. Follow a supported routing design rather than relying on a second MX entry as a catch-all for missing accounts.

Sources: IETF RFC 5321: MX selection and mail delivery ↗

3. Different staff need a supported routing arrangement

With a supported split-delivery design, one system receives incoming mail first. Its rules deliver to recipients held there and route the appropriate other recipients to the second system. The exact method depends on the products and plans, and both sides need to agree how addresses and unknown recipients are handled.

Ask the email administrators who owns the entry point, which recipients are local, which are routed onward and what prevents a delivery loop. Also check messages sent between your own colleagues: internal mail can follow different processing from an outside message. DNS cannot configure these mailbox-server rules on its own.

4. Work through a small recipient map first

For a hypothetical three-person team, two people might stay on the existing system while a third moves to a new suite. Record that intended destination for each address, then include shared mailboxes, aliases and groups. Ask both providers to confirm the supported design before changing the public receiving records.

If the actual goal is two copies of each message, the plan is different. Dual delivery needs an explicit copy or onward-delivery arrangement, with decisions about replies, sent mail and retention. Receiving a copy does not synchronise folders, calendars or previously stored messages. A second login is not evidence that a migration has finished.

Swipe sideways to compare the email arrangements.

5. Receiving and sending need separate checks

A working incoming route does not automatically authorise both services to send as your domain. Obtain each active sender’s current authentication instructions and review them together. Keep one valid SPF policy for each applicable hostname; publishing two separate SPF policies at the same name causes an invalid result rather than combining the permissions.

Copy any required DKIM records carefully and check the provider’s verification result. Preserve unrelated email and website records. For a complex split setup, use a qualified mail administrator to review authentication and forwarding behaviour. NameUK’s DNS controls publish the supported records you enter; they do not create mailbox routing or guarantee message delivery.

Sources: IETF RFC 7208: one selected SPF policy ↗

6. Use a test matrix before closing the old account

Send from an independent external mailbox to a person on each service and to every important shared address. Test both directions between colleagues on the two systems. Reply externally from each service and check the visible sending identity, received headers and spam placement. Include a misspelled recipient so you understand the intended rejection or catch-all behaviour.

Save message references and any bounce details. Confirm there is no loop, duplicate surprise or missing shared-mailbox reply. Allow for cached DNS during a planned change, keep the previous working settings and agree a rollback with the administrators. Historical email, contacts and calendars need their own migration checks; new messages arriving correctly do not prove old data is safe.

7. Buy the domain for flexibility, then price the mail plan

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.

You can keep a .co.uk registered at NameUK while using a separate email provider. When NameUK’s managed nameservers are active, edit the supported DNS records from your domain page. If your authoritative DNS is elsewhere, publish them there. Adding MX records or a preset is a DNS action; it does not purchase licences or enable split delivery inside either service.

Compare domain registration and annual renewal separately from mailbox subscriptions and migration work. The new three-year domain offer covers registration time, not email hosting. This is NameUK’s own recommendation for buyers who want visible ongoing domain costs and DNS control while choosing their email services independently. Prefer the simpler mail arrangement when it meets the team’s needs.