Malaysia DNS Propagation Checker
Run a DNS lookup against 6 resolvers located in Malaysia — Subang Jaya · Bayan Lepas · Seremban · Kuala Lumpur · Kuala Lumpur · Klang.
- Resolved
- No answer
- Checking
-
Subang Jaya
Malaysia
—
-
Bayan Lepas
Malaysia
—
-
Seremban
Malaysia
—
-
Kuala Lumpur
Malaysia
—
-
Kuala Lumpur
Malaysia
—
-
Klang
Malaysia
—
What checking DNS from Malaysia 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 Malaysia 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 Malaysia until its cached copy expires. The check confirms the new value has reached the resolvers your Malaysia visitors depend on.
In August 2024 several Malaysian ISPs quietly switched on a transparent DNS proxy. Point your router at 8.8.8.8 or 1.1.1.1 and your queries were intercepted and answered locally anyway, so any domain on MCMC's blocklist came back as the regulator's address instead of the real one. The backlash was quick. When the MCMC followed up with a directive ordering all ISPs to redirect DNS by 30 September, communications minister Fahmi Fadzil halted it, but the machinery underneath, ISP resolvers honouring MCMC block orders, never left.
That is the backdrop for checking DNS from inside Malaysia. The resolver a typical household uses is whatever its provider hands out, whether that is Telekom Malaysia's Unifi, Maxis, TIME, or CelcomDigi on mobile, not a public option people chose. For a domain on the block list those resolvers return a redirect instead of the record you published.
A check from Malaysian servers shows both halves: whether your record reached the caches Malaysians actually use, and whether it resolves cleanly or gets caught by a block meant for something else.
- TM (Unifi)1.9.1.9 Incumbent; the memorable TMnet resolver, most fixed-line homes
- Maxis Mobile and fibre; ran the transparent DNS proxy in 2024
- TIME dotCom Fibre popular in condos; also proxied public DNS
- CelcomDigi Largest mobile base after the 2022 merger
Resolver answers in Malaysia are shaped by MCMC-ordered blocking: ISP resolvers return a regulator-controlled address for domains on the national blocklist, so a lookup here can reflect state filtering rather than only your own DNS records.
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 Malaysia 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 Malaysia 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 Malaysia?
It depends on the record's time-to-live, not on the country.
Resolvers in Malaysia 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 Malaysia 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 Malaysia, 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 Malaysia specifically?
Because it shows what visitors in Malaysia actually resolve, which can differ from a global lookup.
If your audience is in Malaysia, 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 a Malaysian lookup sometimes return a government address instead of my site?
That is MCMC's block sinkhole. When a domain is on the regulator's list, Malaysian ISP resolvers answer with a regulator-controlled address (historically 175.139.142.25) rather than the real IP, and the visitor lands on a notice or a dead page. Seeing it from a Malaysian resolver means the domain is blocked there, not that your DNS is broken. The vast majority of blocks target gambling, pornography, copyright and scam domains, though legitimate sites have been caught by mistake.
Can I bypass MCMC blocks just by setting 8.8.8.8 or 1.1.1.1?
Not reliably. In August 2024 Maxis and TIME switched on a transparent DNS proxy that intercepted plain queries to Google and Cloudflare and returned MCMC's answer anyway. The government shelved that plan after public pushback, but encrypted DNS (DoH or DoT) is what actually stops a query being read and rewritten on the way out. It is also why a lookup run from inside Malaysia can differ from one run against 8.8.8.8 abroad.
