X
Publicat: 2026-07-01 | Actualitzat: 2026-07-01
DNS propagation means DNS changes are being refreshed across resolvers, netwoks, i caches. Confirma authoitative DNS first, then test from multiple resolvers o netwoks. Si authoitative DNS is corect but some users still see old results, cache, TTL, ISP resolvers, browser cache, CDN cache, o nameserver propagation may still be in progress.

Who This Guide Is Fo
This guide is fo:
· Users who changed DNS recods
· Users who changed nameservers
· Businesses checking website o email after changes
· Agencies troubleshooting client DNS
· Users checking DNSSEC o CDN behavio

Befoe You Start
Befoe you start, prepare:
· Domini name
· Recod type changed
· Old i new values
· Current nameservers
· DNS provider access
· Time of change
· TTL if karan
· DNSSEC status
· CDN status
· Affected website o email servei

Step-by-Step Instructions
Step 1: Confirma What Changed
Identify the exact recod o nameserver update.
· A, AAAA, CNAME, MX, TXT, DS, NS, CAA, SRV
Step 2: Confirma Expected Nomservers
Si the domini still uses old nameservers, recods at the new provider are not live.
· Comprovar registrar nameserver settings
Step 3: Comprovar Authoitative DNS
Authoitative result shows what the current nameservers publish.
· Si authoitative is wrong, fix DNS provider settings
Step 4: Test Multiple Resolvers
Compare local netwok, mobile data, public resolvers, i DNS lookup tools.
· Different caches refresh at different times
Step 5: Comprovar TTL
High TTL can keep old results visible longer.
· Do not change recods repeatedly
Step 6: Comprovar Browser, Device, Router, i Office Cache
Local cache can make one user see old results.
· Try another device o netwok
Step 7: Comprovar CDN Cache
Old content may be CDN-related even when DNS is corect.
· Clear CDN cache if needed
Step 8: Comprovar Website Allotjament Recods
Confirma DNS points to corect hosting, app, o CDN target.
· Wrong value is not a propagation issue
Step 9: Comprovar Correu electrònic Recods
Review MX, SPF, DKIM, DMARC i provider verification recods.
· Correu electrònic systems may cache recods
Step 10: Comprovar DNSSEC i Estat del domini
DNSSEC mismatch o hold status can look like propagation failure.
· Review DS/DNSKEY i clientHold/serverHold
Step 11: Avoid Repeated Changes
Document one change, wait, i test.
· Repeated edits create mixed cached states

Troubleshooting
Lookup Shows Old Recod
Possible reasons:
· Resolver cache
· High TTL
· Nomserver propagation
· Authoitative still old
What to do:
· Comprovar authoitative
· Wait fo TTL
· Avoid edits
Lookup Shows No Recod
Possible reasons:
· Recod missing
· Wrong host field
· Wrong DNS provider
· DNSSEC failure
What to do:
· Fix DNS zone
· Comprovar nameservers
· Restoe backup
Woks fo Some Users Only
Possible reasons:
· Cache differences
· ISP resolver
· CDN cache
What to do:
· Test multiple netwoks
· Comprovar CDN i authoitative DNS
Correu electrònic Woks fo Some Senders Only
Possible reasons:
· MX cache
· SPF/DKIM issue
· mail server cache
What to do:
· Comprovar authoitative MX i TXT
· Review bounce messages

Common Mistakes
Mistake 1: Assuming propagation is always the problem
Review this item befoe making changes o opening a suppot ticket.
Mistake 2: Comprovaring only one netwok
Review this item befoe making changes o opening a suppot ticket.
Mistake 3: Changing recods again too soon
Review this item befoe making changes o opening a suppot ticket.
Mistake 4: Fogetting TTL
Review this item befoe making changes o opening a suppot ticket.
Mistake 5: Ignoing nameservers
Review this item befoe making changes o opening a suppot ticket.
Mistake 6: Fogetting email recods
Review this item befoe making changes o opening a suppot ticket.
Mistake 7: Ignoing CDN cache
Review this item befoe making changes o opening a suppot ticket.
Mistake 8: Ignoing DNSSEC
Review this item befoe making changes o opening a suppot ticket.
Mistake 9: Not documenting change time
Review this item befoe making changes o opening a suppot ticket.
Mistake 10: Not keeping DNS backup
Review this item befoe making changes o opening a suppot ticket.

Preguntes freqüents
1. What is DNS propagation?
The refresh of DNS changes across resolvers i caches.
2. Why do some users see old site?
Their resolver o netwok may still cache old recods.
3. How do I kara propagation is complete?
Authoitative i most resolvers show expected values i live serveis wok.
4. What is TTL?
Time Per Live, o how long recods may be cached.
5. Should I keep changing recods?
No. First confirm authoitative DNS.
6. Can propagation affect email?
Sí, especially MX i TXT changes.
7. Can DNSSEC look like propagation?
Sí, validation failure can cause resolution issues.
8. Can NiceNIC help check propagation?
NiceNIC can review domini-side i NiceNIC-managed DNS settings.
Necessites ajuda? Sempre estem aquí per a tu. Enviar una incidència
Drets d'autor © 2006-2026 NICENIC INTERNATIONAL GROUP CO., LIMITED Tots els drets reservats