South Africa DNS Propagation Checker
Run a DNS lookup against 6 resolvers located in South Africa — Randburg · Pretoria · Pretoria · Cape Town · Groblersdal · Boksburg.
- Resolved
- No answer
- Checking
-
Randburg
South Africa
—
-
Pretoria
South Africa
—
-
Pretoria
South Africa
—
-
Cape Town
South Africa
—
-
Groblersdal
South Africa
—
-
Boksburg
South Africa
—
What checking DNS from South Africa tells you
A DNS resolver keeps a cached copy of each record for as long as its time-to-live allows, and does so separately in every location. A change you have published can be live on one resolver while another still serves the old answer.
Checking from South Africa looks up the record on servers inside the country, so you see what people there actually get rather than what a resolver on another continent returns.
This matters most right after you edit a record: an update visible on a global resolver like 8.8.8.8 can still be stale at a local ISP in South Africa until its cached copy expires. The check confirms the new value has reached the resolvers your South Africa visitors depend on.
South Africa spent decades at the end of a long wire, with most content fetched over submarine cables from Europe, and its internet still carries that shape. The fix has been local: Johannesburg and Cape Town now host some of the busiest exchange points on the continent, and the big CDNs keep caches there.
Whether your site benefits is exactly what a South African DNS check reveals. A resolver in Johannesburg that returns a local edge address means South Africans get your content at domestic latency; an answer pointing at Amsterdam or London means every page load swims to Europe and back.
Propagation works the same as anywhere, but the stakes of CDN steering are higher here than in almost any market this size.
- Vodacom Mobile operator; answers from Johannesburg
- RSAWEB Independent ISP; the Cape Town counterpoint
How DNS propagation works
Every DNS record carries a time-to-live: the seconds a resolver may keep its cached answer before asking again. Change a record and resolvers holding the old value keep serving it until that timer runs out.
Propagation is this expiry playing out across many independent resolvers, so a lower time-to-live set ahead of a change makes it take effect sooner. There is no fixed waiting period — each record's time-to-live decides how long the old answer lingers.
Frequently Asked Questions
Why do DNS servers in South Africa return different results than 8.8.8.8?
Two things cause it. Each resolver caches independently, so one can hold an older answer than another.
And content delivery networks reply based on where the asking resolver is, steering a resolver in South Africa toward a nearby edge node.
Both answers can be correct at the same time for their own location.
How long until a DNS change is visible in South Africa?
It depends on the record's time-to-live, not on the country.
Resolvers in South Africa keep the previous answer until their cached copy expires, then pick up the new one.
If you lowered the time-to-live before making the change, it appears sooner; otherwise the old value can persist until the original timer elapses.
Which DNS server should users in South Africa use?
For most people the resolver their internet provider assigns is fine and usually the lowest latency.
Anyone who wants an alternative can point to a public resolver reachable from South Africa, such as Cloudflare (1.1.1.1) or Google (8.8.8.8); the right choice depends on whether you value speed, privacy, or filtering.
Why check DNS from South Africa specifically?
Because it shows what visitors in South Africa actually resolve, which can differ from a global lookup.
If your audience is in South Africa, or you have moved hosting or mail there, checking against in-country resolvers confirms the records have reached the servers those users rely on.
Why is my site slow in South Africa even though DNS looks fine?
DNS being current does not mean content is served locally. If the answer points at a European address, every request crosses a submarine cable, adding well over a hundred milliseconds each way. The lookup from inside South Africa tells you which case you are in: local edge or long haul.
Do South African ISPs filter DNS?
There is no national DNS blocking regime, so differences between South African resolvers come down to caching and CDN steering rather than policy. That makes this an easy market to reason about: if Johannesburg and Cape Town agree on your new record, the change has propagated.
