A business rebrands. The new name is chosen, the logo is in progress, and someone registers the new domain. Simple enough — just point it at the website, right?
Not quite. A domain name change involves a series of coordinated DNS updates, email configuration, domain verification, and redirect planning. Miss a step and your website goes down, your emails bounce, or your Google rankings disappear overnight.
Here’s what actually happens when a managed hosting provider handles a domain switchover for you.
It Starts With DNS Records
When a new domain is registered, the nameservers need to be pointed to your hosting provider. That’s the first step, and it’s usually done by whoever manages the domain registration.
But pointing nameservers is just the beginning. Your hosting provider then needs to configure several types of DNS records for the new domain:
TXT Records for Verification
Google, Microsoft, and other services need to verify that you own the domain before they’ll let you use it. This is done by adding a TXT record — a specific string of text — to your domain’s DNS. It’s invisible to visitors but proves ownership to the service requesting it.
If you use Google Workspace for email, Google Search Console for SEO, or Microsoft 365, each one may need its own verification record.
CNAME Records
CNAME records point a subdomain to another domain. These are commonly used for services like Google Workspace, where a custom subdomain needs to resolve to Google’s servers for email routing or domain verification.
MX Records for Email
MX (Mail Exchange) records tell the internet where to deliver email for your domain. If your business uses Google Workspace or Microsoft 365 for email, the MX records for the new domain need to point to the correct mail servers.
Get this wrong and emails sent to your new domain address simply won’t arrive. There’s no bounce message, no error — they just vanish into the void.
DKIM Records for Email Authentication
DKIM (DomainKeys Identified Mail) is an email authentication standard. It adds a digital signature to your outgoing emails so receiving mail servers can verify they actually came from your domain and haven’t been tampered with in transit.
Setting up DKIM involves adding a TXT record containing a public cryptographic key. Without it, emails from your new domain are more likely to be flagged as spam or rejected entirely.
The Redirect Plan
Changing your domain doesn’t mean abandoning the old one. If your business has been operating under the original domain for any length of time, people have bookmarked it, linked to it, and Google has indexed it. All of that SEO equity — built up over months or years — lives on the old domain.
A proper switchover keeps the old domain active as a redirect for at least 12 months. Every page on the old domain should forward visitors to the same page on the new domain. If the URL structure stays the same (just the domain changes), this is a straightforward server-level redirect. If page slugs are also changing, each old URL needs to be mapped to its new destination individually.
This isn’t optional if you care about search rankings. Google treats a domain change without proper redirects as a brand new website. Your existing rankings, backlinks, and search authority don’t transfer automatically — they follow the redirects.
The Coordination Problem
The tricky part of a domain switchover isn’t any single step. It’s that everything needs to happen in the right order, and multiple people are usually involved:
- The domain registrar (whoever registered the new domain) updates nameservers
- The hosting provider configures DNS records, sets up the new domain on the server, and implements redirects
- The email provider (often Google or Microsoft) needs verification records in place before email will work
- The website developer may need to update internal references, sitemaps, and analytics configuration
If the hosting provider adds the MX records before the domain registrar has pointed the nameservers, nothing happens. If the website switches to the new domain before email is configured, the business might miss enquiries during the gap.
A managed hosting provider coordinates these steps, communicates with the web designer or developer handling the project, and makes sure nothing falls through the cracks.
What This Looks Like in Practice
A typical domain switchover involves:
- Nameserver update — the new domain is pointed to the hosting provider
- DNS record setup — TXT verification records, CNAME records, MX records, and DKIM records are added as requested
- Testing — email delivery is confirmed, domain verification passes
- Website cutover — the site is updated to respond on the new domain
- Redirects — the old domain is configured to forward all traffic to the new one
- Monitoring — DNS propagation is checked, email delivery is verified, and any issues are resolved quickly
For the business owner, it should feel seamless. For the hosting provider, it’s a checklist of precise technical steps executed in the right sequence.
The Cost of Getting It Wrong
When a domain switchover is handled poorly, the consequences are immediate and visible:
- Email stops working. Clients and customers get bounce messages or, worse, no indication their email didn’t arrive.
- The website goes down. DNS misconfiguration can make your site unreachable for hours while changes propagate.
- Search rankings drop. Without proper redirects, Google sees your new domain as an unrelated website with no history.
- Security is compromised. Missing DKIM and SPF records mean your emails are more likely to be spoofed or marked as spam.
Why This Matters for Your Hosting Choice
Domain changes aren’t everyday events, but when they happen, you need a hosting provider who can handle the DNS side quickly and accurately. This is one of those services that’s invisible when it works and catastrophic when it doesn’t.
If your business is planning a rebrand, ask your hosting provider:
- "Can you manage DNS records for our new domain?"
- "Will you set up email authentication (DKIM, SPF, DMARC) for the new domain?"
- "Can you implement redirects from the old domain to the new one?"
- "How quickly can you turn around DNS changes when we’re ready to switch?"
The answers will tell you whether your hosting is truly managed or whether you’re about to spend a stressful week coordinating it yourself.
