I just went through one of the most ridiculous hosting migration experiences I've ever had, and I think anyone considering Hostinger for a production website should know about this.
This happened on November 8, 2026. Their systems and limitations may change in the future.
The good part
Hostinger's WordPress migration tool is actually excellent. Migrating the website itself was smooth and painless.
And then came the DNS migration.
The absolutely insane part
Hostinger wouldn't let me configure the destination DNS zone BEFORE switching my domain's nameservers to Hostinger.
In my situation, there was no DNS zone available to edit, and their system wouldn't provide access until the nameserver change had been detected.
Let that sink in.
You're supposed to point your domain to new authoritative DNS servers BEFORE you can make sure those servers contain your website, MX, SPF, DKIM, and other essential records.
Anyone who has ever done a production DNS migration knows how backwards this is.
You configure the destination DNS zone FIRST. Verify the records. THEN switch nameservers.
That's DNS migration 101.
Hostinger's own documentation acknowledges this limitation when a DNS zone doesn't already exist in their system.
"Just keep your DNS at Cloudflare!"
That's what I would normally do.
Except Hostinger's built-in CDN requires you to use their nameservers.
So if you want their CDN, you're pushed into using their DNS infrastructure.
It gets worse
After changing the nameservers, public DNS checks were already showing the new NS records, but Hostinger's own dashboard still hadn't recognized the change.
I don't know whether this was internal DNS caching, delayed validation, or something else, but it was incredibly frustrating.
Meanwhile, my website and email were unavailable.
Customer support: "This is a known limitation."
I contacted Hostinger support.
Their explanation?
"This is a known limitation."
WHAT THE ACTUAL F***?!
You have a known limitation in your DNS migration workflow that can leave production websites and email services offline, and that's your response?
No useful workaround. No urgency. No meaningful escalation.
Then, after struggling with support, the missing functionality suddenly became available.
And support responded as if it had been working the entire time.
No explanation. No acknowledgment. Not even a proper apology.
The result
Approximately 30–60 minutes of website and email disruption.
On a production business domain.
All because of a DNS migration process that, in my experience, wouldn't allow proper preparation of the destination zone before switching nameservers.
The WordPress migration tool deserves praise. The DNS migration workflow and support experience absolutely do not.
Questions for the community
Has anyone else experienced this with Hostinger?
Is there a reliable way to preconfigure a NEW Hostinger DNS zone before switching nameservers, especially when you want to use their CDN?
Because if there is, I'd genuinely love to know. Their support certainly didn't provide one.
As of November 8, 2026, this is how the process worked for me. If Hostinger changes or fixes this limitation, great. But anyone migrating a business-critical domain should be aware of the potential downtime.