Bangladesh DNS Propagation Checker
Run a DNS lookup against 6 resolvers located in Bangladesh — Dhaka · Dhaka · Dhaka · Tongi · Dhaka · Dhaka.
- Resolved
- No answer
- Checking
-
Dhaka
Bangladesh
—
-
Dhaka
Bangladesh
—
-
Dhaka
Bangladesh
—
-
Tongi
Bangladesh
—
-
Dhaka
Bangladesh
—
-
Dhaka
Bangladesh
—
What checking DNS from Bangladesh 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 Bangladesh 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 Bangladesh until its cached copy expires. The check confirms the new value has reached the resolvers your Bangladesh visitors depend on.
In July 2024 the government had operators cut service at the international internet gateways, and Bangladesh lost the internet for the better part of two weeks. That is the backdrop for DNS in the country: most international traffic funnels through a limited number of licensed International Internet Gateways, and deep-packet-inspection boxes sit on roughly two dozen of them.
Day to day, blocks usually arrive as DNS tampering. Ask your ISP's resolver for a site the telecom regulator wants gone and you get a wrong or empty answer instead of the real record. Most people never switch resolvers: a fixed-line home takes whatever BTCL or its local ISP hands out, and a phone takes Grameenphone's. Checking a record from inside Bangladesh shows what those resolvers actually return.
That is why it can disagree with 8.8.8.8. If a domain resolves cleanly on Google or Cloudflare but comes back mangled on a Bangladeshi ISP resolver, you are looking at a gateway-level block, not a fault in the record itself.
- BTCL (Bangladesh Telecommunications Company Limited) State-owned incumbent; fixed-line default, runs the .bd registry
- Grameenphone Largest mobile operator; default resolver on most phones
- Google Public DNS8.8.8.8 Common escape hatch from DNS-level blocks
- Cloudflare1.1.1.1 Encrypted public resolver used to dodge gateway blocks
DNS answers from Bangladeshi ISP resolvers can be altered by state-ordered filtering at the international gateways, so results may differ from what a public resolver returns.
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 Bangladesh 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 Bangladesh 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 Bangladesh?
It depends on the record's time-to-live, not on the country.
Resolvers in Bangladesh 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 Bangladesh 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 Bangladesh, 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 Bangladesh specifically?
Because it shows what visitors in Bangladesh actually resolve, which can differ from a global lookup.
If your audience is in Bangladesh, 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 site resolve on 8.8.8.8 but fail on my BTCL or Grameenphone connection?
Most blocking in Bangladesh happens at the DNS and gateway level. When the BTRC orders a site blocked, ISP resolvers are made to return a bogus or empty answer for it, while a public resolver like Google or Cloudflare still hands back the real IP. That gap is why switching resolvers or using encrypted DNS is a common workaround. Keep in mind the gateways can also block by IP, so a correct DNS answer does not guarantee the site will load.
Who controls DNS and blocking in Bangladesh?
The regulator, BTRC, issues the block orders, and they are enforced upstream at the International Internet Gateways that all Bangladeshi traffic passes through, with deep packet inspection deployed across roughly two dozen of them. BTCL, the state-owned incumbent, also runs the .bd country registry and hands default resolvers to its fixed-line customers. During the 2024 protests, authorities used those same chokepoints to switch the internet off entirely for days at a time.
