What Is DNS Propagation

Introduction

People say “DNS propagation” when different networks see different DNS answers after a change. That usually means caching and TTL — not magic delay at the registrar.

Understanding propagation helps you tell the difference between a normal wait and a real misconfiguration.

Quick answer

What it means

When you change DNS at the authoritative provider, the new value is available immediately at that source. Other resolvers worldwide may still return old cached values until their TTL expires.

• Authoritative DNS — the source of truth at your DNS provider
• Resolver cache — ISP, public DNS (8.8.8.8, 1.1.1.1) storing old answers
• TTL — how long cached values remain valid
• Local cache — browser, OS or router DNS cache
• Nameserver changes can take longer than single record edits

Where you see this:

• After changing A records for website migration
• After MX changes for email provider moves
• After nameserver updates at registrar
• When users in different regions see different results

Why this matters

How to check it

1. Check NS records to find authoritative nameservers.
2. Query DNS directly at authoritative NS with dig @ns1.example.com.
3. Compare with public resolvers like 8.8.8.8 and 1.1.1.1.
4. Note TTL and when old cache should expire.
5. Rule out CDN or browser cache if DNS is already correct.

Common mistakes

Example

dig +short example.com A
dig @8.8.8.8 +short example.com A
dig @ns1.provider.com +short example.com A

Frequently asked questions