Hostinger DNS Propagation Guide 2026: How Long Changes Take & What to Do
DNS propagation after changes in Hostinger hPanel takes 1-4 hours for most records and up to 24 hours for nameserver changes. The delay exists because global DNS resolvers cache records based on TTL values. Use DNSChecker.org to monitor propagation progress in real time across global servers.
Why DNS Changes Don't Take Effect Immediately
When you update a DNS record in Hostinger hPanel, the change is stored immediately on Hostinger's nameservers. However, the global internet uses a distributed caching system — thousands of recursive DNS resolvers (at ISPs, Google, Cloudflare, etc.) have your old records cached based on their TTL (Time to Live) setting.
Until those caches expire and resolvers fetch fresh records from Hostinger's nameservers, different users around the world may see different versions of your DNS. This is called the propagation period — it's not a bug, it's how DNS works by design.
Expected Propagation Times for Different DNS Changes
A Record changes: 1-4 hours (depends on existing TTL)
CNAME changes: 1-4 hours
MX record changes: 1-4 hours (email may be delayed during transition)
TXT record additions: 15 minutes - 1 hour (usually fastest)
Nameserver changes: 12-24 hours (sometimes up to 48 hours)
The TTL value of the record you're changing determines minimum propagation time — a record with TTL=86400 (1 day) takes up to 24 hours to expire from caches, even if you make the change now.
How to Speed Up DNS Propagation
Lower your TTL before making DNS changes. At least 24 hours before a planned DNS change, update the TTL for affected records to 300 seconds (5 minutes). This means cached records expire quickly after your change, and propagation completes in 5-15 minutes instead of hours.
After propagation completes and you've confirmed everything is working, return TTL to a reasonable value (3600 - 86400 seconds) to reduce DNS query load.
For nameserver changes (the slowest propagation), this TTL trick has limited effect — registrar-level nameserver data has its own caching rules managed by root nameservers.
Tools to Check DNS Propagation Progress
DNSChecker.org: Check how a specific DNS record (A, MX, TXT) appears from 100+ global DNS servers. See which regions have your new record vs old record in real time.
WhatsmyDNS.net: Similar to DNSChecker with a clean interface and world map visualization of propagation progress.
nslookup (Terminal): Run nslookup yourdomain.com 8.8.8.8 to check what Google's DNS sees. Compare to nslookup yourdomain.com 1.1.1.1 (Cloudflare DNS) to see if different resolvers have different records.
Hostinger hPanel: The DNS Zone Editor shows your current records as stored on Hostinger's nameservers — always up to date, not affected by propagation delays.
Frequently Asked Questions
How long does DNS propagation take on Hostinger?
A, CNAME, and MX record changes propagate in 1-4 hours. Nameserver changes take 12-24 hours. You can lower TTL to 300 seconds before changes to speed up propagation to 5-15 minutes for most record types.
My Hostinger DNS change hasn't propagated after 24 hours — what's wrong?
First, verify the record is saved correctly in hPanel DNS Zone Editor. Then check propagation at DNSChecker.org. If most global servers show the new record but a few don't, wait another few hours. If no servers show the new record, the change may not have saved correctly — re-enter it in hPanel.
Can I force DNS propagation to happen faster?
You can't force third-party DNS resolvers to flush their cache. But lowering TTL before changes minimizes cache duration. You can also flush your local DNS cache (ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on Mac) to see the updated records on your own machine immediately.
Will my website go down during DNS propagation?
Visitors using DNS servers that have your old records cached will reach your old server. Visitors using DNS servers that have updated will reach your new server. For most transitions, this means partial availability rather than complete downtime — and it resolves as propagation completes.
Does lowering TTL before a DNS change actually help?
Yes, significantly. A TTL of 300 means DNS caches expire in 5 minutes. Combined with the immediate update on Hostinger's nameservers, this means most visitors see your changes within 10-15 minutes rather than hours. Always lower TTL 24 hours before planned major DNS changes.
Manage DNS Records on Hostinger
Full DNS control with instant updates on Hostinger's nameservers. Changes propagate in hours.
Register Your DomainHenry Fontaine
Chief of Staff & COO, RocketLabs
AI-native operator building the future of search visibility. Part of the team behind 3 tech exits and 400+ programmatic SEO deployments.