Brazil DNS Propagation Checker
Run a DNS lookup against 6 resolvers located in Brazil — São Paulo · Osasco · Jundiaí · Rio Verde · São Paulo · São Paulo.
- Resolved
- No answer
- Checking
-
São Paulo
Brazil
—
-
Osasco
Brazil
—
-
Jundiaí
Brazil
—
-
Rio Verde
Brazil
—
-
São Paulo
Brazil
—
-
São Paulo
Brazil
—
What checking DNS from Brazil 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 Brazil 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 Brazil until its cached copy expires. The check confirms the new value has reached the resolvers your Brazil visitors depend on.
Brazil's internet is bigger and more fragmented than outsiders expect. IX.br, the public exchange fabric anchored in São Paulo, is one of the largest in the world by connected networks, and thousands of small regional providers hang off it alongside the national carriers.
That fragmentation is the reason to check DNS from here: a record change reaches Vivo's caches on its own schedule, a Curitiba fiber operator's on another, and a rural wireless ISP's whenever its TTL happens to expire. CDNs meanwhile treat Brazil as its own universe, steering resolvers to São Paulo or Fortaleza edges rather than Miami when they can.
A check from Brazilian servers shows whether Brazilians get your new records and a nearby edge, or yesterday's answer routed through another continent.
- Vivo Telefônica's brand; the largest broadband base
- Ligga Telecom Answers from Curitiba in the industrial south
- Brisanet Fiber operator covering the Northeast
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 Brazil 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 Brazil 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 Brazil?
It depends on the record's time-to-live, not on the country.
Resolvers in Brazil 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 Brazil 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 Brazil, 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 Brazil specifically?
Because it shows what visitors in Brazil actually resolve, which can differ from a global lookup.
If your audience is in Brazil, 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 check DNS from Brazil instead of trusting a US check?
Because Brazilian resolvers cache on their own schedule and Brazilian CDN steering differs from North America's. A record that looks updated from Miami can still be stale in a Vivo cache, and a CDN that hands US resolvers a US edge should be handing Brazilian resolvers a São Paulo one. Only an in-country lookup shows either.
Do Brazilian ISPs block domains at DNS level?
Court-ordered blocks exist, occasionally dramatic ones, as when messaging apps were briefly ordered offline nationwide, but there is no standing national blocklist. Day to day, differences between Brazilian resolvers come down to caching and CDN geography rather than filtering.
