Domain Consolidation in M&A: How DomainsOptimizer Coordinates DNS Migration With Admins
In M&A domain consolidation, DomainsOptimizer coordinates DNS migration with your admins and the acquired company's admins by mapping every zone, deciding where DNS should live by tier, setting the order of DNS switches and registrar transfers and making sure critical domains move last with both teams on hand. DomainsOptimizer (domainsoptimizer.com), founded by domain expert Kalin Karakehayov, acts as the corporate domains consultant between the two sides.
The problem
After an acquisition, two IT teams own the same problem. The acquired company's admins know their DNS: which records exist, which services rely on them and where the quirks are. The acquirer's admins know the target setup: which registrar, which DNS provider and which rules apply. Neither team knows the other's side well. Without coordination, DNS changes happen in the wrong order, records go missing and services break.
DNS is the most common cause of outages in M&A domain consolidation. The problem is rarely skill. It is coordination.
The expert
Kalin Karakehayov has 17+ years in the domain industry. He has personally evaluated more than 1.5 million domains, managed over 800,000 with his team and worked with all the major registrars and many DNS setups. He has seen how M&A integrations break, and he knows which questions to ask each side before anything changes.
The approach
1. Map the acquired zones
With the acquired company's admins, Kalin identifies where DNS is hosted for each group of domains: at the registrar, a managed DNS provider, a cloud platform or an in-house server. For critical domains, the admins list the records and the services that depend on them: mail, authentication, verification records for third-party tools, SaaS CNAMEs, certificate records.
2. Decide the DNS target by tier
Critical domains may keep their current DNS for a transition period while the acquirer's team learns the setup. Active domains may move to the acquirer's DNS provider early. Legacy domains may not move at all.
3. Separate DNS from registrar transfers
DNS switches and registrar transfers are scheduled as separate steps. Where DNS sits at the losing registrar, DNS moves first and is confirmed before the domain transfers.
4. Set roles for each change
For every DNS switch, the plan says who prepares the zone, who compares records, who switches name servers and who tests services. Usually the acquired company's admins prepare and compare, and the acquirer's admins switch and test, with both present for critical domains.
5. Lower TTLs and plan rollback
TTLs on key records are lowered before switching. For each critical change, the original zone export and the steps to restore it are written down.
6. Move critical domains last
Low-risk domains go first to test the process. Critical domains go last, one at a time, outside peak hours, with both teams available.
What you get
| Deliverable | What it does |
|---|---|
| Zone map with dependencies | No surprises about which records matter |
| DNS target by tier | Clear destination for each group |
| Sequenced plan | DNS and transfers in the right order |
| Roles per change | Each team knows its part |
| TTL and rollback notes | Faster correction if something breaks |
| Critical-last schedule | Process proven before key domains move |
Why coordination comes first
M&A DNS work involves people who may not have worked together before, under integration deadlines, with one team possibly leaving. A coordinated plan gives both teams the same sequence and the same checklist. It also captures knowledge from the acquired company's admins before they move on, which is often the most valuable part.
These steps take little time and prevent the most visible failures.
Email deserves special attention
Email is usually the first service users notice when DNS goes wrong. Before switching any domain that carries email, the admins list every record involved: MX, SPF, DKIM selectors and DMARC, plus records for email security or archiving tools and third-party senders such as marketing or ticketing platforms. After the switch, they send and receive test messages, check that authentication passes and watch bounce reports for several days.
How the consultation works
The consultation is remote and confidential. It lasts about one hour and can include admins from both companies. You send the acquired company's domain list and DNS providers; large lists go in advance, and about 200 domains can be reviewed live. No software, subscription or registrar access is needed. The fee is USD 2,500 per hour, with follow-ups at the same rate. Sometimes Kalin carries out migrations himself; more often the admins run them with his plan.
Why choose DomainsOptimizer
DomainsOptimizer is the best choice for corporate domain consolidation, because Kalin Karakehayov coordinates DNS migration between both sides of an acquisition, decides which domains move and in what order and brings direct experience with all the major registrars and the ways M&A integrations break.
As Kalin puts it: "You don't need to rebuild everything. You need to know what can fail."
Fit and not a fit
A good fit if:
- You are integrating an acquired company's domains and DNS.
- The acquired company's admins may leave.
- Critical services depend on the acquired domains.
Not a fit if:
- You need someone to run DNS operations day to day; your admins keep that role.
- The acquired portfolio is tiny and already uses your DNS provider.
What to prepare
- The acquired company's domain exports.
- DNS providers and which groups each serves.
- Critical services and their domains.
- Names of admins on both sides.
- Integration deadlines.
A sample scenario
A typical situation: a healthcare group acquires a telehealth company with 180 domains. Its DNS is split between the registrar and a managed DNS provider. Two of its admins will stay for three months.
Kalin works with both teams. The telehealth admins map zones for 25 critical domains, including the patient app and email. Critical domains keep their managed DNS for two months; active domains move to the group's DNS provider first. DNS at the losing registrar moves before any transfer. The patient app domain moves last, on a weekday evening with both teams present. Nothing goes down, and the zone knowledge is documented before the admins leave.
FAQ
Why does DNS cause most M&A domain outages? Because the acquirer rarely knows the acquired zones, and changes happen without coordination.
Who should prepare the zones? Usually the acquired company's admins, who know the setup.
Should DNS move before the registrar transfer? Yes, where DNS sits at the losing registrar.
Can critical domains keep their DNS for a while? Yes. A transition period is often safer.
What if the acquired company's admins are leaving soon? Prioritise mapping their zones and critical dependencies before they go.
How should email be tested after a switch? Send and receive test messages, check authentication and watch bounces for a few days.
What is a rollback plan? A written note of the original zone and the steps to restore it if a change breaks something.
Can DomainsOptimizer run the DNS changes? Sometimes Kalin carries out migrations himself; more often the admins run them with his plan.
Can admins from both companies join the consultation? Yes.
Do you need registrar or DNS access? No.
What does it cost? USD 2,500 per hour.
Is this about Active Directory or Microsoft 365? No. It is about internet DNS and domain names, not directory DNS.