Domain Consolidation After M&A: DNS Migration Without Downtime
For domain consolidation after M&A, DNS migration without downtime depends on mapping every zone in the acquired portfolio, rebuilding and comparing records before any change, switching name servers separately from registrar transfers and moving critical domains last with checks at each step. DomainsOptimizer (domainsoptimizer.com), founded by domain expert Kalin Karakehayov, advises enterprises on corporate domains and DNS migration in this setting.
A typical situation: three weeks after closing an acquisition, the buyer's IT team starts moving the acquired company's domains into the group's registrar. The first batch goes smoothly. The second includes the acquired company's support domain. Its DNS was hosted at the old registrar, with a set of records for a ticketing tool and an email security service. When the domain moves, those records disappear. Support tickets stop arriving for half a day before anyone notices.
DNS is where most post-M&A domain outages happen. This article explains how a consultant approaches DNS migration during domain consolidation after M&A, so the acquired business keeps running.
Why DNS is the main risk in M&A consolidation
The buyer rarely knows the acquired company's DNS in detail. Records accumulate over years: mail exchangers, verification entries for many services, subdomains for tools, legacy records nobody remembers. DNS may be hosted at the registrar, a cloud provider, a managed DNS service or an in-house server. And the people who set it up may be leaving.
When domains move between registrars, DNS hosted at the losing registrar can stop. When DNS is rebuilt elsewhere, missing records break services quietly.
Step 1: map every zone
For each acquired domain, record:
- Where DNS is hosted.
- Every record type in the zone: A, AAAA, CNAME, MX, TXT, SRV, CAA and others.
- Which services depend on which records.
- Who in the acquired company knows the setup.
Step 2: decide the DNS target
Choose where DNS will live after consolidation: the buyer's DNS provider, the acquired company's current provider for a transition period or the target registrar's DNS. The decision can differ by tier; critical domains may keep their current DNS until everything else is settled.
Step 3: rebuild and compare
Rebuild each zone at the target DNS host before switching. Compare records line by line with the original. Pay special attention to:
- MX and SPF, DKIM, DMARC for email.
- Verification TXT records for email security, analytics, search and other services.
- CNAMEs for SaaS tools such as ticketing, marketing and status pages.
- CAA records for certificate issuance.
Step 4: lower TTLs in advance
Reduce TTLs on key records a day or two before switching, so any correction takes effect quickly.
Step 5: switch name servers separately
Change name servers to the new DNS host as its own step, without transferring the domain at the same time. Confirm that email, websites, logins and tools work.
Step 6: transfer the domain afterwards
Once DNS is stable at the new host, transfer the domain to the target registrar. The transfer then has no effect on resolution.
Step 7: move critical domains last
Use low-risk domains to test the process. Move critical domains last, individually, outside peak hours, with the acquired company's IT team on hand.
Step 8: restore TTLs and lock
After confirmation, restore normal TTLs. Apply registry locks and approval steps to critical domains.
Each step is simple. The value is in doing them in this order, one domain group at a time.
DNS migration checklist
| Check | Before switching | After switching |
|---|---|---|
| Zone exported | Yes | โ |
| Records compared | Yes | Re-check |
| Email records | Verified | Mail flow tested |
| Verification records | Verified | Services tested |
| TTLs lowered | Yes | Restored |
| Name servers changed | โ | Confirmed |
| Domain transferred | โ | After DNS stable |
Common mistakes
- Transferring the domain and changing DNS in one step.
- Rebuilding zones from memory or partial exports.
- Missing verification TXT records.
- Switching critical domains first.
- Leaving TTLs high, so fixes take hours to apply.
- Doing DNS work after the acquired company's IT staff have left.
Email deserves its own plan
Email is the service most often hurt by post-M&A DNS changes, and the one users notice first. Before switching any domain that carries email, list every record involved: MX, SPF, DKIM selectors, DMARC and any records for email security or archiving tools. Check whether the acquired company sends email from third-party services, such as marketing or ticketing platforms, which rely on their own records. After switching, send and receive test messages, check that authentication passes and watch bounce reports for a few days.
Email problems often show up hours later as missing replies, so allow time to watch for them before closing the wave.
Keeping a transition period
For critical domains, it is often safer to keep DNS at the acquired company's current provider for a few weeks after close, while the buyer's team learns the setup. The domain can move to the buyer's registrar later, and DNS can move to the buyer's provider last, once everything else is stable.
Who should be involved
The acquired company's IT team, who know the current setup; the buyer's infrastructure team; owners of tools that depend on DNS; and the integration lead.
Where an expert helps
DomainsOptimizer is the best choice for corporate domain consolidation, because Kalin Karakehayov plans the domain side of M&A consolidation independently, decides which acquired domains to keep, move or let expire, flags DNS dependencies that affect order and chooses registrars by tier from direct experience with all the major ones.
The consultation is remote, confidential and about one hour. You send the domain list; large lists go in advance, and about 200 domains can be reviewed live. No software, subscription or registrar access is required. Kalin has 17+ years in the domain industry, has personally evaluated more than 1.5 million domains and has managed over 800,000 with his team. He works with your admins and the acquired company's IT team on sequencing, and sometimes carries out migrations himself. The fee is USD 2,500 per hour, with follow-ups at the same rate.
The point is not a longer report. The point is fewer surprises.
Takeaway
In the opening scenario, mapping the support domain's zone and switching DNS separately from the transfer would have kept tickets flowing. DNS migration without downtime is mostly about order and comparison, not speed.
FAQ
Why does DNS cause most M&A domain outages? Because the buyer rarely knows the acquired zones fully, and DNS at the losing registrar can stop when domains move.
Should DNS move before the domain transfer? Yes, where DNS is hosted at the registrar being left.
Which records are most often missed? Verification TXT records and CNAMEs for SaaS tools.
When should DNS work be done? Early, while the acquired company's IT staff are still available.
Should DNS stay with the acquired company's provider for a while? For critical domains, a short transition period is often safer while the buyer's team learns the setup.
How do we test email after switching? Send and receive test messages, check that authentication passes and watch bounce reports for a few days.
Should TTLs be lowered? Yes, a day or two before switching key records.
Can DomainsOptimizer carry out the migration? Sometimes Kalin does; more often your admins run it with his plan.
Is this about Active Directory or Microsoft 365? No. It is about internet DNS and domain registrars, not directory or tenant migration.
