Taiwan DNS Propagation Checker
Run a DNS lookup against 3 resolvers located in Taiwan — Taipei · Kaohsiung · Taipei.
- Resolved
- No answer
- Checking
-
Taipei
Taiwan
—
-
Kaohsiung
Taiwan
—
-
Taipei
Taiwan
—
What checking DNS from Taiwan 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 Taiwan 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 Taiwan until its cached copy expires. The check confirms the new value has reached the resolvers your Taiwan visitors depend on.
Taiwan gives you two very different windows into the same island. HiNet's 168.95.1.1, run by Chunghwa Telecom, has been the default resolver for the vast majority of Taiwanese connections for decades, so its cache state is effectively what Taiwan sees.
Quad101 at 101.101.101.101 is the newer counterpoint: operated by TWNIC, the registry that runs .tw, it keeps no query logs and exists explicitly as a public service.
There is no standing national blocklist here, which keeps the picture clean: when the two disagree, you are looking at ordinary cache lag, not policy. For anyone serving Taiwanese users, or watching how mainland filtering stops at the strait, these resolvers show the unfiltered regional view.
- Quad101101.101.101.101 Run by .tw registry TWNIC; no-logging policy
- HiNet168.95.1.1 Chunghwa Telecom; the island's default resolver
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 Taiwan 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 Taiwan 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 Taiwan?
It depends on the record's time-to-live, not on the country.
Resolvers in Taiwan 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 Taiwan 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 Taiwan, 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 Taiwan specifically?
Because it shows what visitors in Taiwan actually resolve, which can differ from a global lookup.
If your audience is in Taiwan, or you have moved hosting or mail there, checking against in-country resolvers confirms the records have reached the servers those users rely on.
Is Quad101 really no-log?
TWNIC, the nonprofit registry that operates it, states that it keeps no query logs, and running the resolver is part of its public-service remit rather than a business. As with any resolver, that is a policy promise rather than something you can verify from outside, but the operator has no advertising model to feed.
Do Taiwan and mainland China see the same DNS answers?
Often not. Taiwan has no standing national blocklist, so Taiwanese resolvers return the global view, while queries inside the mainland are subject to national filtering. If you serve both markets, treat them as separate checks; a clean result in Taipei says nothing about Beijing, and the reverse.
