Fix · Domains and DNS

I changed DNS but nothing changed yet (propagation)

Not checked against the vendor's current screens

What you may see

The domain still shows the old site or an error after my change
It works on my phone and not on my computer

Most likely cause

Resolvers around the world keep the old answer until its time-to-live (TTL) ends, so people see changes at different times.

Check first (about two minutes)

Check the record at your domain company is saved exactly as intended.
Use a public lookup tool to see what different places answer.

The fix prompt

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

The exact error or what you see

What you did before it happened

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a patient senior engineer who knows domain names and DNS settings and explains them to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

Menu and button names change over time. If you cannot find a button or page I mention, say so and tell me what to look for instead of guessing.

THE PROBLEM
I changed DNS but nothing changed yet (propagation)

THE EXACT ERROR OR WHAT I SEE
[paste the exact error here]

WHAT I DID BEFORE IT HAPPENED
[write in a few words what you did before it happened]

MOST LIKELY CAUSE
Resolvers around the world keep the old answer until its time-to-live (TTL) ends, so people see changes at different times.

DO THESE STEPS, IN THIS ORDER
1. Look up the name with public resolvers (for example dig @8.8.8.8 and dig @1.1.1.1) and compare with my authoritative nameservers.
2. If the authoritative answer is already right, tell me to wait for the old TTL and how to clear my own computer's cache; if it is wrong, find the record problem.
3. Suggest lowering the TTL a day before planned changes next time.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- Public resolvers all return the new value, and the site opens on the phone on mobile data.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not keep changing the record every few minutes.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Look up the name with public resolvers (for example dig @8.8.8.8 and dig @1.1.1.1) and compare with my authoritative nameservers.
If the authoritative answer is already right, tell me to wait for the old TTL and how to clear my own computer's cache; if it is wrong, find the record problem.
Suggest lowering the TTL a day before planned changes next time.

Do not do this

Do not assume it is broken before the old TTL has passed.
Do not keep changing the record every few minutes.

Try another entry