Chile DNS Propagation Checker

Run a DNS lookup against 6 resolvers located in Chile — San Bernardo · Santiago · Providencia · Valdivia · Santiago · Las Condes.

Checking from 6 locations

Resolved
No answer
Checking

Location Result Time Status
San Bernardo Chile —
Santiago Chile —
Providencia Chile —
Valdivia Chile —
Santiago Chile —
Las Condes Chile —

What checking DNS from Chile tells you

Caching is local

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.

The in-country view

Checking from Chile 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.

When it matters

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 Chile until its cached copy expires. The check confirms the new value has reached the resolvers your Chile visitors depend on.

Field notes

Chile passed the world's first net neutrality law in 2010, and it shows in the DNS: ISPs are barred from blocking lawful content, there is no national blocklist, and answers from Chilean resolvers differ from each other only in the ordinary ways, cache age and CDN steering.

Geography does the rest of the talking. Chile hangs off the Pacific side of South America with its own cable routes north, so content served 'to South America' from Brazilian edges can still be a slow continent-crossing away from Santiago.

A check from Chilean servers confirms your records have reached the caches at GTD and the other national operators, and it shows whether your CDN treats Chile as a place or as an afterthought.

Local resolvers

GTD Santiago operator grown into a regional fiber group
Telefónica del Sur Historic operator of the country's south
Telmex Chile Part of Claro's family

How DNS propagation works

The TTL timer

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.

Staggered expiry

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 Chile 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 Chile 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 Chile?

It depends on the record's time-to-live, not on the country.

Resolvers in Chile 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 Chile 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 Chile, 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 Chile specifically?

Because it shows what visitors in Chile actually resolve, which can differ from a global lookup.

If your audience is in Chile, or you have moved hosting or mail there, checking against in-country resolvers confirms the records have reached the servers those users rely on.

Does Chile block or filter DNS?

No. The 2010 net neutrality law, the first of its kind anywhere, forbids ISPs from blocking lawful content, and no national blocklist exists. When Chilean resolvers disagree with each other it is cache timing or CDN geography, which makes Chile one of the simplest markets to interpret.

Is a Brazilian check good enough for Chilean users?

Not really. Brazil sits on the Atlantic side with its own exchange fabric, while Chilean traffic rides Pacific-coast routes, and CDNs treat the two markets separately. A record can be fresh in São Paulo caches and stale in Santiago, and the edge nodes serving each are usually different. Check them as different countries, because they are.