DNS Changes Not Propagating: What to Check Before Changing Records Again

DNSnameserversTTLCloudflaremigration

What this problem usually means

DNS “propagation” issues are often caused by editing the wrong DNS zone, cached records, mismatched nameservers, long TTLs, or checking from resolvers that have not refreshed yet. Repeatedly changing records can extend confusion.

Production caution: Do not keep changing DNS records while troubleshooting unless you know which authoritative zone is live. It can make diagnosis slower and migrations riskier.

Common symptoms

Some users see the new site while others see the old one
Email works for some senders but not others
DNS checkers show mixed results
Cloudflare says records are set but live traffic goes elsewhere
Migration cutover appears inconsistent

Common causes

Domain still uses old nameservers
Record edited at registrar but DNS is hosted elsewhere
TTL was high before the change
Local ISP or device DNS cache is stale
Conflicting A, CNAME or AAAA records
DNSSEC mismatch after nameserver change

Safe first checks

These checks are intended to help identify the direction of the issue. Always adjust paths, service names and commands for your environment.

Check authoritative nameservers

dig NS example.com +short

Query a public resolver

dig A example.com @1.1.1.1 +short

Trace DNS path

dig +trace example.com

Check common record types

dig A example.com; dig AAAA example.com; dig MX example.com

Typical fixes

Confirm the authoritative nameservers first
Lower TTL before planned migrations
Remove conflicting records
Check DNSSEC after nameserver changes
Use staged DNS cutovers for higher-risk migrations
Document old and new records before changes

When to get help

Get help if the system is production-facing, customer data is involved, backups are uncertain, or the issue affects revenue, security or uptime. We can review the logs, confirm the cause and quote a fixed-scope fix where appropriate.

Need this fixed?

Get remote support for this issue.

Fixed technical support starts from $499. Emergency incident support is $199/hr with a minimum window.