How long does DNS propagation take?

DNS propagation typically takes between 15 minutes and 48 hours, though in rare cases it can take up to 72 hours. The actual time depends on the TTL (Time to Live) value set on your previous DNS records and how aggressively ISP resolvers cache those records. Lowering your TTL to 300 seconds (5 minutes) at least 24 hours before making changes can significantly speed up propagation.

What is the difference between an A record and a CNAME record?

An A record maps a domain name directly to an IPv4 address (e.g., 203.0.113.50), while a CNAME record maps a domain name to another domain name (e.g., www.example.com to example.com). A records are used for root domains and direct IP mappings, whereas CNAME records are useful for aliases and subdomains. You cannot place a CNAME on a root domain alongside other records like MX or TXT.

Can I speed up DNS propagation?

You cannot force global propagation, but you can prepare for it. Lower your TTL values to 300 seconds at least 24-48 hours before making DNS changes. This ensures that resolvers around the world will check for updated records more frequently. After the migration is complete, you can raise TTL values back to a higher setting like 3600 or 86400 seconds.

Why is my website showing the old server after changing DNS?

This is caused by DNS caching. Your ISP's resolver, your operating system, and even your browser can cache the old DNS response. Try flushing your local DNS cache, using a different network (like mobile data), or testing with tools like dig or nslookup. The old cache will expire once the TTL period elapses.

DNS and Hosting: Understanding Propagation and DNS Records Explained

What Is DNS and Why Does It Matter for Your Hosting?

Every time someone types your domain name into a browser, a complex but lightning-fast process takes place behind the scenes. The Domain Name System (DNS) translates human-readable domain names like example.com into machine-readable IP addresses like 203.0.113.50. Without DNS, we would all be memorizing strings of numbers to visit websites.

For anyone managing a website — whether it is a small WordPress blog or a high-traffic PrestaShop e-commerce store — understanding DNS is not optional. It is foundational. Misconfigured DNS records can take your site offline, break your email, and even harm your SEO rankings.

In this guide, we will break down how DNS works, what propagation really means, the most important DNS record types, and practical tips to avoid common mistakes.

How DNS Resolution Works: A Step-by-Step Breakdown

Before diving into records and propagation, let us walk through what happens when a user visits your website.

The DNS Lookup Chain

Browser cache — The browser checks if it already knows the IP address for the domain.
Operating system cache — If the browser has no answer, the OS checks its own local cache.
Recursive resolver — The request goes to your ISP’s (or a public) DNS resolver (e.g., Google’s 8.8.8.8 or Cloudflare’s 1.1.1.1).
Root name server — The resolver queries one of the 13 root server clusters, which directs it to the correct TLD server.
TLD name server — The .com, .net, or .fr server points the resolver to the domain’s authoritative name server.
Authoritative name server — This server holds the actual DNS records and returns the final IP address.
Response delivered — The resolver caches the result and sends it back to the user’s browser.

This entire process typically completes in 20 to 120 milliseconds. It is elegant, distributed, and — when configured properly — remarkably reliable.

Understanding DNS Propagation

DNS propagation is arguably the most misunderstood concept in web hosting. When you change a DNS record — for instance, pointing your domain to a new server — that change does not take effect instantly across the entire internet.

What Propagation Actually Means

Propagation is not a single broadcast that pushes your new record to every server on the planet. Instead, it is a passive, cache-expiration process. Here is what really happens:

Your authoritative name server is updated immediately with the new record.
Recursive resolvers around the world still have the old record cached.
Each resolver will continue serving the old record until its TTL (Time to Live) expires.
Once the TTL expires, the resolver fetches the new record from the authoritative server.
Different resolvers have different cache expiration times, so the update appears to “propagate” gradually.

Typical Propagation Times

Scenario	Expected Propagation Time
TTL was set to 300 seconds (5 min)	5 minutes to 2 hours
TTL was set to 3600 seconds (1 hour)	1 to 6 hours
TTL was set to 86400 seconds (24 hours)	12 to 48 hours
ISP resolver ignores TTL (rare but possible)	Up to 72 hours

The key takeaway: propagation time is largely determined by the TTL value that was set on the old record, not the new one.

How to Prepare for Fast Propagation

At Lueur Externe, when we manage hosting migrations for our clients, we follow a proven protocol to minimize downtime:

48 hours before migration: Lower all relevant TTL values to 300 seconds.
Wait for the old TTL to expire: If the old TTL was 86400, you need to wait 24 hours for all caches to cycle.
Make the DNS change: Update A records, CNAME records, or name servers.
Monitor propagation: Use tools like dig, nslookup, or online checkers like whatsmydns.net.
After confirmation: Raise TTL values back to a production-appropriate level (3600–86400).

This approach consistently reduces effective propagation to under 30 minutes for the majority of global users.

Essential DNS Record Types Explained

DNS is not just about pointing a domain to an IP address. There are multiple record types, each serving a distinct purpose. Let us examine the ones every website owner and developer should understand.

A Record (Address Record)

The most fundamental DNS record. It maps a domain name to an IPv4 address.

example.com.    3600    IN    A    203.0.113.50

Used for root domains and subdomains.
You can have multiple A records for load balancing (round-robin DNS).
Every website needs at least one A record (or an AAAA record for IPv6).

AAAA Record (IPv6 Address Record)

Identical in function to an A record, but maps to an IPv6 address.

example.com.    3600    IN    AAAA    2001:0db8:85a3::8a2e:0370:7334

With IPv4 address exhaustion accelerating, AAAA records are becoming increasingly important. As of 2024, Google reports that over 45% of connections to its services use IPv6.

CNAME Record (Canonical Name)

Maps one domain name to another domain name, creating an alias.

www.example.com.    3600    IN    CNAME    example.com.

Important rules:

A CNAME cannot coexist with other record types at the same name (no CNAME + MX on the same subdomain).
You should never place a CNAME on the root domain (example.com) — this violates the RFC and can break MX and TXT records.
Many CDN and PaaS providers (Cloudflare, AWS CloudFront, Heroku) require CNAME records for integration.

MX Record (Mail Exchange)

Directs email to the correct mail server. Without properly configured MX records, your domain cannot receive email.

example.com.    3600    IN    MX    10    mail1.example.com.
example.com.    3600    IN    MX    20    mail2.example.com.

The number (10, 20) indicates priority — lower numbers have higher priority. If mail1 is unreachable, email is routed to mail2.

TXT Record (Text Record)

Stores arbitrary text data, most commonly used for email authentication and domain verification.

Common uses include:

SPF (Sender Policy Framework): Specifies which servers are allowed to send email for your domain.
DKIM (DomainKeys Identified Mail): Provides a cryptographic signature for outgoing emails.
DMARC: Defines a policy for handling emails that fail SPF or DKIM checks.
Domain verification: Google Search Console, Microsoft 365, and other services use TXT records to verify domain ownership.

example.com.    3600    IN    TXT    "v=spf1 include:_spf.google.com ~all"

Neglecting TXT records for email authentication is one of the most common reasons businesses find their emails landing in spam folders.

NS Record (Name Server)

Delegates a domain (or subdomain) to specific authoritative name servers.

example.com.    86400    IN    NS    ns1.hosting-provider.com.
example.com.    86400    IN    NS    ns2.hosting-provider.com.

NS records are typically set at the registrar level and have high TTL values because they change infrequently.

SRV Record (Service Record)

Specifies the host and port for specific services like SIP, XMPP, or Microsoft Teams.

_sip._tcp.example.com.    3600    IN    SRV    10 60 5060 sipserver.example.com.

CAA Record (Certificate Authority Authorization)

Specifies which certificate authorities are allowed to issue SSL/TLS certificates for your domain. This is a valuable security measure that helps prevent unauthorized certificate issuance.

example.com.    3600    IN    CAA    0 issue "letsencrypt.org"

A Complete DNS Configuration Example

Here is what a well-configured DNS zone might look like for a typical business website with email hosted on Google Workspace:

; A Records
example.com.          300    IN    A       203.0.113.50

; AAAA Records
example.com.          300    IN    AAAA    2001:db8::1

; CNAME Records
www.example.com.      3600   IN    CNAME   example.com.
shop.example.com.     3600   IN    CNAME   shops.myplatform.com.

; MX Records
example.com.          3600   IN    MX      1   aspmx.l.google.com.
example.com.          3600   IN    MX      5   alt1.aspmx.l.google.com.
example.com.          3600   IN    MX      5   alt2.aspmx.l.google.com.

; TXT Records
example.com.          3600   IN    TXT     "v=spf1 include:_spf.google.com ~all"
example.com.          3600   IN    TXT     "google-site-verification=abcdef123456"

; CAA Records
example.com.          3600   IN    CAA     0 issue "letsencrypt.org"
example.com.          3600   IN    CAA     0 issue "digicert.com"

Notice how the A record TTL is set to 300 seconds. This is a deliberate choice during migration preparation. In stable production, you would increase this to 3600 or higher to reduce DNS query load.

Common DNS Mistakes and How to Avoid Them

After two decades of managing hosting infrastructure, the team at Lueur Externe has encountered virtually every DNS misconfiguration imaginable. Here are the most frequent issues we see:

1. Forgetting to Update MX Records After a Migration

When you move to a new hosting provider and change your name servers, your old MX records may disappear if they were configured in the previous provider’s DNS zone. Result: email stops working entirely, sometimes for days before anyone notices.

Prevention: Always document your complete DNS zone before any migration. Recreate all records — especially MX and TXT — in the new DNS zone before switching name servers.

2. Setting a CNAME on the Root Domain

Some users try to set a CNAME record on the bare domain (example.com) to point it to a service like Cloudflare or AWS. This is technically invalid because a CNAME cannot coexist with SOA and NS records, which are mandatory at the zone apex.

Solution: Use an A record for the root domain, or use a DNS provider that supports ALIAS or ANAME records (a non-standard but widely supported workaround).

3. Ignoring TTL Before Migration

Changing your A record when the existing TTL is 86400 seconds means some users will continue hitting your old server for up to 24 hours. If the old server is already decommissioned, those users will see errors.

Solution: Follow the TTL reduction protocol described earlier. Plan ahead.

4. Missing SPF, DKIM, and DMARC Records

Without proper email authentication records, your transactional emails (order confirmations, password resets, invoices) have a high chance of landing in spam. This is especially critical for e-commerce sites running on platforms like PrestaShop or WooCommerce.

Solution: Configure SPF and DKIM at minimum. Add a DMARC record in monitoring mode (p=none) to start, then progressively enforce it.

5. Using Too Many DNS Providers

Splitting DNS management between your registrar, your hosting provider, and a CDN provider creates confusion. It becomes unclear which zone is authoritative, leading to conflicting records.

Solution: Consolidate DNS management into one reliable provider. Use their control panel as the single source of truth.

Tools for DNS Troubleshooting

When things go wrong — and eventually they will — having the right diagnostic tools is essential.

dig (command line): The gold standard for DNS queries. Available on macOS and Linux natively.

dig example.com A +short
dig example.com MX
dig @8.8.8.8 example.com A   # Query Google's resolver specifically

nslookup (command line): Available on all platforms including Windows.
```
nslookup example.com
nslookup -type=MX example.com
```
whatsmydns.net: Visualize propagation across 20+ global resolvers in real time.
MXToolbox.com: Comprehensive email and DNS diagnostics.
Google Admin Toolbox Dig: A web-based version of dig for quick checks.

When troubleshooting, always test from multiple resolvers (Google 8.8.8.8, Cloudflare 1.1.1.1, your ISP’s resolver) to get a complete picture of propagation status.

DNS and SEO: The Connection You Should Not Ignore

DNS configuration directly impacts your website’s performance and availability, both of which are ranking factors.

DNS lookup speed: Slow DNS resolution adds latency to every page load. Using a premium DNS provider (Cloudflare, AWS Route 53, Google Cloud DNS) can reduce lookup times to under 10ms globally, compared to 50-150ms with budget registrar DNS.
Downtime from DNS errors: If your site is unreachable because of a DNS misconfiguration, search engine crawlers will record errors. Prolonged downtime can lead to deindexation.
HTTPS and CAA records: Properly configured CAA records demonstrate security best practices, and of course, SSL/TLS (enabled via correct DNS + hosting configuration) is a confirmed Google ranking signal.
CDN integration: DNS records (typically CNAMEs) are how you connect your domain to a CDN, which improves page load speed — another critical ranking factor.

When to Use Managed DNS Services

For small websites, the free DNS service included with your domain registrar is usually adequate. But for businesses where uptime and performance are non-negotiable, managed DNS services offer significant advantages:

Anycast routing: Queries are answered by the nearest server globally, reducing latency.
DDoS protection: Enterprise DNS providers can absorb massive query floods.
Failover and health checks: Automatically redirect traffic if your primary server goes down.
Geo-routing: Serve different IP addresses based on the user’s geographic location.

Providers like AWS Route 53, Cloudflare DNS, and Google Cloud DNS offer these features at very reasonable costs — often under $1/month for standard zones.

As AWS Solutions Architect certified professionals, the Lueur Externe team frequently architects DNS solutions using Route 53 for clients who need enterprise-grade reliability combined with advanced routing policies.

Conclusion: Master Your DNS, Master Your Hosting

DNS is the invisible infrastructure that holds the web together. It is easy to overlook when everything is working, but it is the first thing you will troubleshoot when something breaks.

Let us recap the essential takeaways:

DNS propagation is a cache-expiration process, not a broadcast. Control it by managing your TTL values proactively.
Know your records: A, AAAA, CNAME, MX, TXT, NS, and CAA each serve a critical role. Understand when and how to use each one.
Document everything before making changes. A missing MX record can silently kill your email for days.
Use proper tools (dig, whatsmydns.net, MXToolbox) to verify changes and troubleshoot issues.
Do not underestimate the SEO impact of DNS performance and reliability.

Whether you are launching a new website, migrating to a new hosting provider, or troubleshooting mysterious downtime, getting DNS right is the foundation of everything that follows.

Need help with a complex DNS setup, a hosting migration, or an infrastructure audit? Lueur Externe has been helping businesses across France and internationally get their web infrastructure right since 2003. Get in touch with our team and let us handle the complexity so you can focus on growing your business.