Indonesia DNS Propagation Checker
Run a DNS lookup against 6 resolvers located in Indonesia — Jakarta · Magetan · Sepatan · Teluknaga · Madiun · Jakarta.
- Resolved
- No answer
- Checking
-
Jakarta
Indonesia
—
-
Magetan
Indonesia
—
-
Sepatan
Indonesia
—
-
Teluknaga
Indonesia
—
-
Madiun
Indonesia
—
-
Jakarta
Indonesia
—
What checking DNS from Indonesia 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 Indonesia 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 Indonesia until its cached copy expires. The check confirms the new value has reached the resolvers your Indonesia visitors depend on.
Indonesia filters at national scale but implements locally, which makes its DNS unusually varied. The communications ministry maintains the Trust Positif blocklist, hundreds of thousands of domains from gambling to pornography, and each ISP enforces it with its own tooling, so a domain can be redirected to a block page on one network and resolve fine on another the same day.
Nawala, the best-known Indonesian public resolver, bakes similar family-oriented filtering in on purpose. Add an archipelago of users spread across thousands of islands with infrastructure concentrated in Jakarta, and checking from inside Indonesia becomes the only way to see what the fourth-largest internet population on earth actually resolves for your domain.
- Nawala Community filtering resolver; shows the filtered view
- Linknet First Media cable network in greater Jakarta
- DTPNET A further independent test point
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 Indonesia 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 Indonesia 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 Indonesia?
It depends on the record's time-to-live, not on the country.
Resolvers in Indonesia 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 Indonesia 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 Indonesia, 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 Indonesia specifically?
Because it shows what visitors in Indonesia actually resolve, which can differ from a global lookup.
If your audience is in Indonesia, 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 does my domain show an ISP landing page in Indonesia?
It is on the Trust Positif blocklist, or on an ISP's local extension of it. Indonesian providers redirect blocked lookups to their own notice pages rather than failing them. Listings can be contested through the ministry, and mistaken entries happen, so an in-country check that catches the redirect early is worth having.
Should I test the filtered and unfiltered view separately?
Yes, if Indonesian users matter to you. Nawala shows the deliberately filtered answer, while an ISP resolver shows what a typical household gets, which includes the mandatory blocks but not Nawala's extra layers. Your own records should be identical on both; only policy-listed domains diverge.
