Checked
2026-11-14
/ DNS

DNS is not resolving, or still points at the old server

'Waiting for propagation' covers two very different things. Either the change is right and resolvers still hold the old answer for as long as its TTL allows, or the change never reached the servers that answer for your domain. dig tells them apart in a minute.

Ask the servers in charge of the domain

Find out which name servers answer for the domain, then ask one of them directly. Its answer is the truth; everything else is a cache.

dig +short NS example.com
dig +short A example.com @ns1.your-dns-provider.com

If the name server gives the new address, the change is made and only caches lag behind. If it gives the old one, or nothing, the record was changed in the wrong place.

Changed in the wrong place

The usual case: the record was edited at the registrar or the old host, but the domain's name servers are somewhere else, a CDN or a DNS provider set up years ago. Edit the record where the NS records point, or move the NS records on purpose.

Waiting out the caches

dig +short A example.com @1.1.1.1 and the same with @8.8.8.8 show what two big public resolvers hold. Without +short, dig also prints the TTL left on a cached answer, in seconds: that is the longest the old address can stay.

Your own computer caches too. resolvectl flush-caches clears it on Linux with systemd-resolved, ipconfig /flushdns on Windows. Browsers keep a cache of their own; a private window often skips it.

A domain that does not resolve at all

  • NXDOMAIN from the domain's own name servers: the name does not exist there. Check the spelling, and whether the record is on the bare domain, on www, or on both.
  • SERVFAIL, or no answer from anyone: the domain may have expired, or the registrar put it on hold. whois example.com shows the expiry date and the status lines.
  • SERVFAIL that goes away with dig +cd example.com: DNSSEC is broken, usually because the DS record at the registrar still describes the old DNS provider's keys after a move. Update or remove the DS record at the registrar.
  • Mail broke as well: MX records are often left behind when the A record moves. dig +short MX example.com shows where mail goes.

What not to do

  • Do not keep changing the record while you wait. Every change starts a new wait, and a real mistake hides in the noise.
  • Do not move the name servers and the server on the same day unless you have to. One change at a time is easier to check.
  • Do not switch off the old server while caches can still send visitors to it.

When to stop and hand it over

Stop when the name servers answer correctly and the site still does not load, when DNSSEC is involved, or when mail and web broke together after a move. Our Server Rescue is one incident at a fixed $69, with a same-day start listed at $109, and nothing to pay if we cannot fix it. If the DNS change is part of a move, the server migration at $109 plans the records, the TTL and the switch together.

/ Questions

Questions people ask

How long does DNS propagation take?
As long as the old record's TTL, counted from the change. With a TTL of 3600 seconds, a resolver can hold the old address for up to an hour. Lowering the TTL a day before a change keeps the wait short.
Why does the site load on my phone and not on my computer?
They ask different resolvers with different caches. The phone on mobile data asks the carrier's resolver; the computer may still hold the old answer.
What TTL should I use?
An hour or a few hours for records that rarely change, five minutes in the days around a move.
What does fixing DNS cost?
With us, Server Rescue at $69 for the incident, or $109 for a same-day start. If we cannot fix it, you pay nothing.
/ Sources

Where each statement comes from

Checked against the sources on .

More server help