Colombia DNS Propagation Checker
Run a DNS lookup against 6 resolvers located in Colombia — Sopó · Pitalito · Bogotá · Medellín · Medellín · Medellín.
- Resolved
- No answer
- Checking
-
Sopó
Colombia
—
-
Pitalito
Colombia
—
-
Bogotá
Colombia
—
-
Medellín
Colombia
—
-
Medellín
Colombia
—
-
Medellín
Colombia
—
What checking DNS from Colombia 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 Colombia 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 Colombia until its cached copy expires. The check confirms the new value has reached the resolvers your Colombia visitors depend on.
In June 2024, subscribers on Claro and Tigo suddenly couldn't reach Reddit. The order came not from a court but from Coljuegos, the state gambling regulator, which had flagged the site and told ISPs to drop it. That is how most filtering works in Colombia: a MinTIC rule, External Circular 017 of 2025, now lets Coljuegos tell providers to block domains directly at the network level, and the agency has filed more than 55,000 such requests.
Almost nobody here picks a resolver. People use whatever Claro, Millicom's Tigo, or Bogotá's ETB hands out over DHCP, and those resolvers carry the official blocklist. Running a lookup from inside Colombia shows you the answer those defaults return, blocklist and all, not the clean record a resolver in another country would give.
That gap is also why moving to a public resolver like 8.8.8.8 is a common local workaround: it sits outside the ISP's control and usually returns the record unfiltered, at least where the block is enforced in DNS rather than at the IP layer.
- Claro (Telmex Colombia) Largest ISP; default resolver for most households
- Tigo (Millicom) Merged Tigo–Movistar network, the second-largest default resolver
- ETB Bogotá's city-owned incumbent; regional default resolver
- Google Public DNS8.8.8.8 Common opt-out from ISP-level Coljuegos blocking
Answers from Colombian ISP resolvers reflect government blocklists (notably Coljuegos gambling orders and copyright injunctions), so a blocked or redirected result may be state filtering rather than the domain's true DNS record.
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 Colombia 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 Colombia 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 Colombia?
It depends on the record's time-to-live, not on the country.
Resolvers in Colombia 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 Colombia 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 Colombia, 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 Colombia specifically?
Because it shows what visitors in Colombia actually resolve, which can differ from a global lookup.
If your audience is in Colombia, 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 is a site blocked on my Colombian ISP but resolves fine on 8.8.8.8?
Much of the blocking in Colombia is applied at the ISP's own resolver under MinTIC External Circular 017 of 2025, which lets Coljuegos order Claro, Tigo and other providers to drop domains at network level. A public resolver outside the country, such as Google's 8.8.8.8 or Cloudflare's 1.1.1.1, doesn't carry that blocklist, so it usually returns the real record — unless the block is enforced at the IP layer rather than in DNS.
Who decides what gets blocked in Colombia, courts or a regulator?
Both, but the volume comes from regulators. Coljuegos, the gambling authority, drives the bulk of blocks (55,000-plus requests) against unlicensed betting sites, and has also blocked Reddit, Bitcoin-related pages and news outlets. Separately, since 2024 Colombian courts have issued dynamic injunctions through the copyright directorate (DNDA) against piracy and unlicensed sports-streaming sites. ISPs implement both against their default resolvers.
