Help for owners
I changed my DNS settings and nothing happened
Short answer
DNS answers are cached for a set time (TTL), so a change can take a while to reach everyone, and your own computer may show the old answer longer. If it still has not changed after the old TTL has passed, the usual causes are editing at the wrong provider, a conflicting record, or nameservers that point elsewhere.
Does this sound like your situation?
- I saved a new record but my website still shows the old server.
- It works on my phone and not on my office computer, or the other way round.
- Email still goes to the old provider after I changed the mail records.
- The DNS panel looks right, but a checking tool shows something else.
- A provider says the change is pending and I do not know what that means.
Why does this happen?
Answers are cached for a set time
The TTL says how long a record is cached, which decides how quickly changes reach users. Longer TTLs mean faster lookups but slower updates. Cloudflare's proxied records use an automatic TTL of 300 seconds, and its docs note your local DNS cache may take longer than five minutes to show a change.
Confirmed by developers.cloudflare.com
You edited the wrong place
The records that count are the ones at whichever provider your domain's nameservers point to. If the registrar says one thing and your nameservers point to a hosting company or Cloudflare, edits at the registrar change nothing.
The nameserver switch has not finished
When a domain moves to Cloudflare, its zone can sit in a state called Pending Nameserver Update until the registrar change is made. Cloudflare has a separate troubleshooting guide for a zone stuck there.
Confirmed by developers.cloudflare.com
A conflicting or duplicate record
Two records of the same kind for one name, or an old record left behind, can send some visitors one way and some another.
The cache is on your side
Your computer, your router and your browser keep their own copies. Your own view can lag behind the real situation, so one machine proves little.
What can I do about it today?
- Save a copy of the records before touching anythingScreenshot the whole DNS list. Most DNS trouble that becomes an outage comes from deleting a record that was needed.
- Find out who runs the DNSLook up your domain's nameservers with any public lookup tool. The provider they name is the one whose records count.
- Note the TTL on the record you changedThe old value tells you how long to wait before the world must see the change. Waiting at least that long avoids false alarms.
- Check from a second networkTry a phone on mobile data, not Wi-Fi, and a private browser window. Do not keep re-saving the record.
- Do not delete old records yetLeave the previous server and mail records in place until the new ones are confirmed working.
- Write down what you expectedA short note of which name should point where, and what you see instead, saves a developer a lot of time.
When should I bring someone in?
- The site or email has been wrong for longer than the old TTL.
- Some visitors see the new site and some the old one, and it does not settle.
- You are about to change nameservers on a live business domain.
How do I handle it?
- Start from the nameserversI confirm which provider is actually answering for the domain before reading any record.
- Compare intended and actual answersI query the records from outside your network and compare them with what you wanted.
- Look for conflictsDuplicate records, stale entries and proxy settings that hide the real address are checked one by one.
- Lower the TTL before a planned moveFor migrations I reduce the TTL ahead of time so a rollback is quick, and keep the old setup until the new one is proven.
- Leave a record of the final stateYou get a written list of every record and what it is for.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
How long does DNS propagation really take?
It depends on the TTL of the old record and on caches along the way. Cloudflare's docs say TTL controls how quickly changes reach users, and that local caches may take longer than five minutes. I cannot give one number that fits every domain.
Why does it work for me but not for a customer?
Different devices and networks cache independently, so the old answer can last longer for some of them.
Should I clear my cache?
It can make your own view current, but it does not change what other people see. It is safe to try and does not affect the domain.
Can I change the TTL to speed things up?
Lowering it helps for future changes. It does not shorten the time already counted on records that others cached under the old value.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.