How to Check DNS Propagation After Migrating Your Hosting

When we decide to change hosting providers to improve our website's performance, security, or cost, migrating domain name records is the most critical step. Modifying nameservers or updating the IP address in an A record often creates uncertainty due to the infamous DNS propagation period. During this window, web traffic is divided between the old and new servers.

In this guide, we explain in detail how this process works, the methods available to verify if your site is fully propagated, and how to avoid connectivity issues that affect your visitors and the security of your infrastructure.

---

What Is DNS Propagation and Why Does It Take So Long?

The Domain Name System (DNS), formally defined in standard documents such as the IETF RFC 1035, is a distributed and hierarchical database. Its primary function is to translate easy-to-remember names (like tecnocrypter.com) into numerical IP addresses that computers use to communicate.

When you modify your domain records at your registrar or DNS provider:

1. The information is updated immediately on the domain's authoritative server.
2. Resolver servers (resolvers) of Internet Service Providers (ISPs) worldwide, as well as public resolvers (Google Cloud DNS, Cloudflare, Quad9), do not request new information on every single visit. Instead, they save a local copy (cache).
3. This cache has an expiration time determined by the record's TTL (Time to Live). Until this time runs out, resolvers will continue to send users to the old IP.

This gradual update process worldwide is known as propagation. Depending on cache values and local ISP policies, this process can take anywhere from a few hours to a typical maximum of 48 hours.

---

Critical Steps Before Starting a Hosting Migration

To avoid prolonged downtime, we advise planning the migration in advance. Follow these steps to reduce the impact:

• Reduce TTL in advance: Access your domain's DNS settings 24 to 48 hours before the migration and reduce the TTL value to 300 seconds (5 minutes) or 600 seconds (10 minutes) if possible. This forces resolvers worldwide to refresh their cache frequently.
• Keep both servers active: Do not cancel your old hosting account immediately. Keep website files and databases running on both servers for at least 72 hours after changing the DNS.
• Email migration: If you are also changing mail servers (MX records), make sure you have created the email accounts on the new server before the change to prevent message loss.

---

Methods to Verify DNS Propagation

There are multiple ways to monitor propagation progress, from visual online tools to command-line utilities in your operating system.

1. Using Online Real-Time Tools

The fastest and most convenient way to perform global tracking is to use platforms designed to query resolvers from different parts of the world simultaneously. You can use our DNS Propagation Checker, a utility that queries public DNS resolvers across various continents directly and in real-time.

This tool allows you to check essential records at a glance:

• A and AAAA Records: To check the target IP.
• MX Records: To verify where emails are being routed.
• NS Records: To know which nameservers are responding.

2. Using Command-Line Interface (Terminal)

If you are a system administrator or developer, you can perform specific queries from your terminal using standard commands. Below are examples of how to check your records:

# Query the A record of your domain using the dig command
dig @8.8.8.8 tecnocrypter.com A

# Alternative on Windows systems using nslookup
nslookup -type=A tecnocrypter.com 1.1.1.1

With these commands, we force the query to a specific external DNS server (such as Google's 8.8.8.8 or Cloudflare's 1.1.1.1) to validate if they have already updated their internal tables with the new hosting IP.

---

Comparative Table of Popular DNS Resolvers

Not all DNS service providers clear their cache at the same rate. The following table shows the typical behavior of some of the most widely used public resolvers:

Resolver	Primary IP	Average Refresh Time	DNSSEC Support	Main Focus
Cloudflare	1.1.1.1	Very fast (seconds/minutes)	Yes	Speed and privacy
Google Public DNS	8.8.8.8	Fast (minutes)	Yes	Performance and reliability
Quad9	9.9.9.9	Moderate (minutes to hours)	Yes	Malware protection
OpenDNS	208.67.222.222	Moderate	Yes	Customizable filters

---

Common Problems After a DNS Change and How to Fix Them

Sometimes, even though the tools show that the DNS has propagated, you still see the old site in your browser or experience connection failures.

1. Local Browser Cache: Web browsers aggressively cache name resolution to speed up load times.
   • Solution: Clear your browser's cache or access via an incognito window. In Google Chrome, you can force a flush by visiting chrome://net-internals/#dns and clicking "Clear host cache".
2. Operating System Cache: Your computer saves DNS records locally.
   • Solution: Flush the cache by running ipconfig /flushdns in the Windows command prompt, or on macOS using the command sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.
3. Security Conflicts with DNSSEC: If you had DNSSEC active on your previous host and changed nameservers, your domain may become inaccessible on strict networks if you do not update the corresponding DS keys at your registrar.
   • Solution: Temporarily disable DNSSEC in your domain control panel before the migration, and reactivate it at the new provider once propagation is complete.

Conclusion

The website migration process requires precision to avoid losing users or compromising service continuity. Understanding how DNS caching works and actively monitoring global propagation is vital.

We recommend relying on trustworthy tools like our DNS Propagation Checker to validate every step, and checking out related security posts on our portal, such as our analysis of How DNS propagation works in real-time or our article on DNS Hijacking threats.

---

Sources and Recommended Readings:

• RFC 1035 - Domain Names - Implementation and Specification — Official IETF standard document.
• Wikipedia - Domain Name System — Core concepts of DNS architecture.
• TecnoCrypter Internal Tool: DNS Propagation Checker