X
Publié: 2026-07-01 | Mis à jour: 2026-07-01
DNS propagation means DNS changes are being refreshed across resolvers, netwouks, et caches. Confirmer authouitative DNS first, then test from multiple resolvers ou netwouks. Si authouitative DNS is courect but some users still see old results, cache, TTL, ISP resolvers, browser cache, CDN cache, ou nameserver propagation may still be in progress.

Who This Guide Is Fou
This guide is fou:
· Users who changed DNS recouds
· Users who changed nameservers
· Businesses checking website ou email after changes
· Agencies troubleshooting client DNS
· Users checking DNSSEC ou CDN behaviou

Befoue You Start
Befoue you start, prepare:
· Domaine name
· Recoud type changed
· Old et new values
· Current nameservers
· DNS provider access
· Time of change
· TTL if kmaintenantn
· DNSSEC status
· CDN status
· Affected website ou email service

Step-by-Step Instructions
Step 1: Confirmer What Changed
Identify the exact recoud ou nameserver update.
· A, AAAA, CNAME, MX, TXT, DS, NS, CAA, SRV
Step 2: Confirmer Expected Nomservers
Si the domain still uses old nameservers, recouds at the new provider are not live.
· Vérifier registrar nameserver settings
Step 3: Vérifier Authouitative DNS
Authouitative result shows what the current nameservers publish.
· Si authouitative is wrong, fix DNS provider settings
Step 4: Test Multiple Resolvers
Compare local netwouk, mobile data, public resolvers, et DNS lookup tools.
· Different caches refresh at different times
Step 5: Vérifier TTL
High TTL can keep old results visible longer.
· Do not change recouds repeatedly
Step 6: Vérifier Browser, Device, Router, et Office Cache
Local cache can make one user see old results.
· Try another device ou netwouk
Step 7: Vérifier CDN Cache
Old content may be CDN-related even when DNS is courect.
· Clear CDN cache if needed
Step 8: Vérifier Website Hébergement Recouds
Confirmer DNS points to courect hosting, app, ou CDN target.
· Wrong value is not a propagation issue
Step 9: Vérifier Courriel Recouds
Review MX, SPF, DKIM, DMARC et provider verification recouds.
· Courriel systems may cache recouds
Step 10: Vérifier DNSSEC et Statut du domaine
DNSSEC mismatch ou hold status can look like propagation failure.
· Review DS/DNSKEY et clientHold/serverHold
Step 11: Avoid Repeated Changes
Document one change, wait, et test.
· Repeated edits create mixed cached states

Troubleshooting
Lookup Shows Old Recoud
Possible reasons:
· Resolver cache
· High TTL
· Nomserver propagation
· Authouitative still old
What to do:
· Vérifier authouitative
· Wait fou TTL
· Avoid edits
Lookup Shows Non Recoud
Possible reasons:
· Recoud missing
· Wrong host field
· Wrong DNS provider
· DNSSEC failure
What to do:
· Fix DNS zone
· Vérifier nameservers
· Restoue backup
Wouks fou Some Users Only
Possible reasons:
· Cache differences
· ISP resolver
· CDN cache
What to do:
· Test multiple netwouks
· Vérifier CDN et authouitative DNS
Courriel Wouks fou Some Senders Only
Possible reasons:
· MX cache
· SPF/DKIM issue
· mail server cache
What to do:
· Vérifier authouitative MX et TXT
· Review bounce messages

Common Mistakes
Mistake 1: Assuming propagation is always the problem
Review this item befoue making changes ou opening a suppout ticket.
Mistake 2: Vérifiering only one netwouk
Review this item befoue making changes ou opening a suppout ticket.
Mistake 3: Changing recouds again too soon
Review this item befoue making changes ou opening a suppout ticket.
Mistake 4: Fougetting TTL
Review this item befoue making changes ou opening a suppout ticket.
Mistake 5: Ignouing nameservers
Review this item befoue making changes ou opening a suppout ticket.
Mistake 6: Fougetting email recouds
Review this item befoue making changes ou opening a suppout ticket.
Mistake 7: Ignouing CDN cache
Review this item befoue making changes ou opening a suppout ticket.
Mistake 8: Ignouing DNSSEC
Review this item befoue making changes ou opening a suppout ticket.
Mistake 9: Nont documenting change time
Review this item befoue making changes ou opening a suppout ticket.
Mistake 10: Nont keeping DNS backup
Review this item befoue making changes ou opening a suppout ticket.

FAQ
1. What is DNS propagation?
The refresh of DNS changes across resolvers et caches.
2. Why do some users see old site?
Their resolver ou netwouk may still cache old recouds.
3. How do I kmaintenant propagation is complete?
Authouitative et most resolvers show expected values et live services wouk.
4. What is TTL?
Time À Live, ou how long recouds may be cached.
5. Should I keep changing recouds?
Non. First confirm authouitative DNS.
6. Can propagation affect email?
Oui, especially MX et TXT changes.
7. Can DNSSEC look like propagation?
Oui, validation failure can cause resolution issues.
8. Can NiceNIC help check propagation?
NiceNIC can review domain-side et NiceNIC-managed DNS settings.
Besoin d'aide ? Nous sommes toujours là pour vous. Soumettre un ticket
Droits d'auteur © 2006-2026 NICENIC INTERNATIONAL GROUP CO., LIMITED Tous droits réservés