Back to tools

DNS Propagation Checker

See which DNS resolvers worldwide already have your new record — and which are still catching up.

Lookup

Check a domain's DNS propagation

Enter a domain and pick a record type. In the real version this fans out to resolvers in North America, Europe and Asia-Pacific at once; here it simulates that spread.

Paste the value you configured to highlight matches against it instead of the majority.

Results

Enter a domain and run a check.

Verify it yourself

Run these against the same resolvers used above, from your own machine.

dig (Linux / macOS)

dig @8.8.8.8 play.wespner.eu A +short
dig @1.1.1.1 play.wespner.eu A +short
dig @9.9.9.9 play.wespner.eu A +short
dig @208.67.222.222 play.wespner.eu A +short
dig @45.90.28.0 play.wespner.eu A +short
dig @185.222.222.222 play.wespner.eu A +short
dig @75.75.75.75 play.wespner.eu A +short
dig @4.2.2.2 play.wespner.eu A +short
dig @223.5.5.5 play.wespner.eu A +short
dig @129.250.35.250 play.wespner.eu A +short

nslookup (Windows / cross-platform)

nslookup -type=a play.wespner.eu 8.8.8.8
nslookup -type=a play.wespner.eu 1.1.1.1
nslookup -type=a play.wespner.eu 9.9.9.9
nslookup -type=a play.wespner.eu 208.67.222.222
nslookup -type=a play.wespner.eu 45.90.28.0
nslookup -type=a play.wespner.eu 185.222.222.222
nslookup -type=a play.wespner.eu 75.75.75.75
nslookup -type=a play.wespner.eu 4.2.2.2
nslookup -type=a play.wespner.eu 223.5.5.5
nslookup -type=a play.wespner.eu 129.250.35.250

Why results differ

How DNS propagation actually works

Every DNS record carries a TTL (time-to-live) — how many seconds a resolver may keep an answer before asking the authoritative nameserver again. If the old record had a one-hour TTL, a resolver that already cached it can keep serving the old value for up to that long after you make the change, even though the authoritative nameserver already has the new one. That's expected behaviour, not a broken change — it's the trade-off that makes DNS fast.

The #1 false alarm: it's not unpropagated, your own resolver is just stale.

If every public resolver above already shows the new value but your own browser still loads the old one, the problem is almost always a cached answer on your machine or your ISP’s resolver — not a stuck propagation. Flush the local cache and check again from that machine:

Windows

ipconfig /flushdns

macOS

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Linux (systemd-resolved)

sudo resolvectl flush-caches

Running your own game server?

Wespner game servers with DDoS protection, NVMe drives and activation within minutes.

Browse hosting