I was building a brand-new website for a business. After I changed the domain's settings to point it at the new site, the page would not load. The assumption in the room was the same one you have probably heard: "It's just DNS. Give it a day."
It was not DNS. Waiting would never have fixed it. This post is about the difference, because it will save you an afternoon.
What is my take on "just wait for DNS"?
My view: "wait for DNS" should be the last thing you say, not the first. It is a comfortable answer, and comfortable answers stop people checking. I would rather spend ten minutes proving what is wrong than a day hoping it fixes itself. You are allowed to disagree, because sometimes waiting really is the right call. The checks below tell you which case you are in.
What does "give DNS time to propagate" actually mean?
DNS is the internet's phone book. It turns a name like example.com into the number of the computer that hosts it. When you change where a name points, the old answer is stored in lots of places for a while, so some people see the old site and some see the new one. That delay is called propagation, and it is real. Mozilla's glossary entry on DNS is a good primer.
So "wait for DNS" is a perfectly good answer sometimes. It becomes a lazy answer when you stop checking whether it is the actual problem.
How can I tell whether it really is DNS?
Ask what the error is, not just whether the site loads. Two quick checks:
- Try a different device on a different network, such as your phone on mobile data. If it loads there, the new setup works and something local to your browser is the problem.
- Look up the domain with a lookup tool and see whether it returns the new address. Google even has a page about flushing its public DNS cache if you want to force an update.
If the lookup shows the new address everywhere and the site still will not load in your browser, DNS has done its job. Something else is stopping you.
What was actually going on?
The browser was holding on to old security settings for the domain.
There is a feature called HSTS, short for HTTP Strict Transport Security. Once a site has told your browser "only ever talk to me over a secure connection", the browser remembers that instruction for a set time. MDN explains the header clearly. If the domain's setup changes in a way that does not match what the browser remembers, the browser refuses to connect rather than risk it. It is being cautious, not broken. (Google's page on how it treats HTTP status codes is a useful companion if you want to see what search engines make of a site that refuses connections.)
So the change I made was correct, the DNS had updated, and my browser, quite reasonably, refused to open a door it had been told not to open.
How do I fix it?
The sensible fix is to clear the browser's memory of that domain's security rule, not to wait.
- In Chrome, you can type
chrome://net-internals/#hsts, find the delete section, enter your domain and delete it. Then try again. - In other browsers the steps differ, and clearing the site's data for that domain often helps.
- Then test in a private window and on another device to confirm.
Do it only for your own domain, and only after checking that your site really does have a valid secure certificate. The point of the feature is to protect visitors, and you should not switch it off for something that is genuinely misconfigured.
What would I do differently next time?
A short checklist that I now keep for any domain change:
- Write down the old and new settings before touching anything.
- After the change, test from a second device on a different network.
- Check the lookup result, not only the browser.
- Test in a private window.
- Only then say "wait", and say how long you will wait before checking again.
The lesson that stuck with me is to stop treating "wait" as a plan. Waiting is only a plan if you know what you are waiting for and when you will check again. Otherwise it is hoping with a calendar.
The thing I like about this story is how ordinary it is. Nothing was broken in a dramatic way. A sensible default (be careful about security) and a sensible assumption (it must be DNS) combined to waste an afternoon. Most mysteries are two sensible things in the wrong order.
For the full story, see Case 001 in the case files. That build started from an empty domain and ended with a live B2B site with 8 solution pages, a 63-product catalogue and 3 lead tools, so it all worked out in the end. If a launch of your own is stuck, you are welcome to book a call.
Frequently asked questions
How long does DNS propagation really take?
It depends on how long old answers are stored, which the domain's settings control. It can be minutes or up to a day or more. Checking the lookup result tells you whether it has finished.
Is it safe to clear HSTS for my domain?
For your own site, once you have confirmed the certificate is valid, yes. It only clears your browser's memory. It does not weaken anyone else's.
Why does the site load on my phone but not my laptop?
That usually means something local to the laptop: a cached rule, an old DNS answer or a browser setting. The new setup is probably fine.
Could my host be the problem?
It can be. Check the host's status page and the lookup result. If both look fine and the site loads elsewhere, look at your browser first.
