Thailand DNS Propagation Checker
Run a DNS lookup against 3 resolvers located in Thailand — Pathum Thani · Koh Tao · Bangkok.
- Resolved
- No answer
- Checking
-
Pathum Thani
Thailand
—
-
Koh Tao
Thailand
—
-
Bangkok
Thailand
—
What checking DNS from Thailand 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 Thailand 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 Thailand until its cached copy expires. The check confirms the new value has reached the resolvers your Thailand visitors depend on.
Thailand's home-broadband market folded into a near-duopoly in 2023: AIS bought 3BB to become the largest fixed-broadband provider, and True absorbed DTAC. So the resolver a typical Thai household uses is almost never one it chose — it's whatever AIS or True hands out over the fibre, with state-owned NT (the 2021 merger of TOT and CAT Telecom) covering much of the rest.
That matters because those same ISP resolvers enforce the national blocklist. Under Section 20 of the Computer Crime Act, the Ministry of Digital Economy and Society obtains a court order and ISPs carry it out mostly through DNS, returning a spoofed answer or a redirect to a block page for gambling, copyright, and lèse-majesté domains. Checking a name from inside Thailand shows what those resolvers actually return, not the clean answer 8.8.8.8 gives from outside.
When the two disagree, you're usually looking at a local block, not a propagation lag.
- AIS (Advanced Wireless Network)115.178.58.10 Largest fixed-broadband group after buying 3BB; default fibre resolver
- NT (National Telecom)203.113.127.199 State incumbent from the 2021 TOT–CAT merger; legacy TOT resolver
- True True–DTAC group; hands out its own resolvers with court-ordered blocks
Some resolver answers seen from Thailand reflect court-ordered DNS blocks that ISPs apply under the Computer Crime Act, not the domain's real 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 Thailand 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 Thailand 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 Thailand?
It depends on the record's time-to-live, not on the country.
Resolvers in Thailand 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 Thailand 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 Thailand, 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 Thailand specifically?
Because it shows what visitors in Thailand actually resolve, which can differ from a global lookup.
If your audience is in Thailand, 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 do some domains resolve to a block page in Thailand?
Because ISP resolvers enforce court-ordered blocks. Under Section 20 of the Computer Crime Act, the Ministry of Digital Economy and Society (MDES) gets a court order and providers like True, AIS, and NT implement it at the DNS layer — returning a spoofed answer or a redirect to an access-denied page, mostly for gambling, copyright, and lèse-majesté sites. Pointing your device at a public resolver such as 8.8.8.8 or 1.1.1.1, or using DNS-over-HTTPS, sidesteps most of these plain-DNS blocks, which is why an answer from inside Thailand can differ from one taken abroad.
Which resolver does a typical Thai internet connection use?
On fibre it's the ISP's own recursive resolver: AIS (which now also runs the former 3BB network), True (which absorbed DTAC), or state-owned NT, whose address space still traces to the old TOT and CAT Telecom networks it was merged from. Plenty of Thai users manually switch to Google or Cloudflare to avoid blocks and get faster answers, but the ISP resolvers remain the default path for most households — which is exactly why checking a record against them still matters.
