Australia DNS Propagation Checker
Run a DNS lookup against 6 resolvers located in Australia — South Brisbane · South Brisbane · South Brisbane · St Leonards · Sydney · Belmont.
- Resolved
- No answer
- Checking
-
South Brisbane
Australia
—
-
South Brisbane
Australia
—
-
South Brisbane
Australia
—
-
St Leonards
Australia
—
-
Sydney
Australia
—
-
Belmont
Australia
—
What checking DNS from Australia 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 Australia 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 Australia until its cached copy expires. The check confirms the new value has reached the resolvers your Australia visitors depend on.
Ask an Australian network engineer to name an IP address from memory and there is a decent chance you get 139.130.4.4, Telstra's resolver, known by its old hostname uneeda.telstra.net since the 1990s.
DNS from Australia has a distinct character because the country is far from almost everything: a cache miss that has to consult authoritative servers in Virginia costs an Australian resolver a couple of hundred milliseconds round trip, so caches and local CDN nodes carry more of the load than they do in Europe.
That distance is exactly why checking from inside Australia is worth doing. It shows whether your CDN is actually serving Australians from Sydney rather than Singapore or the US West Coast, and whether your record change has landed in the caches Australians really use.
- Telstra139.130.4.4 Elder statesman; answers a huge share of queries
- Aussie Broadband Challenger ISP running its own resolvers
- Exetel One of the larger independents
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 Australia 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 Australia 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 Australia?
It depends on the record's time-to-live, not on the country.
Resolvers in Australia 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 Australia 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 Australia, 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 Australia specifically?
Because it shows what visitors in Australia actually resolve, which can differ from a global lookup.
If your audience is in Australia, 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 139.130.4.4 so well known?
It has been Telstra's recursive resolver since the mid-1990s under the hostname uneeda.telstra.net, and generations of Australian technicians memorised it the way the rest of the world memorised 8.8.8.8. It still answers, which makes it a handy sanity check for how the country's biggest ISP resolves your domain.
My site is on a CDN. What should an Australian check show?
Ideally an IP belonging to a Sydney, Melbourne or Brisbane edge node rather than one in Singapore or the US. CDNs choose the edge based on the resolver asking, so an Australian resolver getting an offshore answer usually means the CDN has no nearby capacity for your plan, and Australian visitors are paying for it in latency.
