Skip to content
ENID
DNS

Why Your DNS Changes Aren’t Showing (and How to Fix It)

A step-by-step checklist for the usual reasons a DNS change does not appear: TTL, wrong nameservers, local caches, proxies, and DNSSEC.

Published 3 min read

Start with what you can measure

Before changing anything else, find out where the old value still lives. Run the DNS Propagation Checker and compare several resolvers, then ask your authoritative nameserver directly:

dig example.com A @ns1.yourprovider.com

Three outcomes, three different problems:

  • The nameserver still returns the old value. The change was not saved, or it was made at the wrong provider.
  • The nameserver is right, resolvers are mixed. Caching. Wait for the old TTL.
  • Everything online is right, but your device is wrong. Local caching.

1. You are waiting for the TTL

If the old record had a TTL of 3600 seconds, resolvers may keep it for up to an hour after they last fetched it. Nothing you do on your side shortens that. Next time, lower the TTL a day before the change.

2. You edited the wrong DNS zone

A domain can have a zone at your registrar and another at your hosting company, but only the zone at the nameservers listed in the domain’s NS records counts. Check the NS records, then edit records there.

3. The nameservers were changed recently

Delegation at the registry can take up to 48 hours to settle. During that time some resolvers use the old nameservers and some the new ones. Keep identical records at both providers until the move completes.

4. DNSSEC is out of step

If the old provider signed the zone and you moved to one that does not, the DS record at the registrar must be removed. A stale DS record makes validating resolvers return SERVFAIL, while non-validating ones still work, which looks like a random failure.

5. A CDN or proxy is in front

With a proxied record (for example an orange-cloud setting at some providers) a lookup returns the proxy’s address, not your server. That is intended, but it can look like the change did not apply.

6. Your local machine has its own cache

Operating systems, browsers, and routers all cache DNS. Flush the system cache (ipconfig /flushdns on Windows, resolvectl flush-caches on many Linux systems), restart the browser, and try another network such as a phone hotspot. Also check the hosts file, which overrides DNS completely.

7. The record itself is wrong

Look for a trailing dot or a missing one, a typo in the hostname, a CNAME sitting next to other records, or a value with an extra space. Compare with the example in DNS record types explained.

8. Negative caching

If a name did not exist when someone first asked, resolvers may remember “not found” for a while. That period is set by the SOA record, so a brand-new record can seem missing for longer than expected.

FAQ

Is it the website or the DNS?

Resolve the name first. If it returns the right IP but the site still fails, use the HTTP Status & Redirect Checker to look at the web server instead.

Should I delete and re-add the record?

Usually no. It does not clear remote caches and can create a gap.

Related guides

Enter to open, Esc to close

Scroll to Top