Uzbekistan DNS Propagation Checker
Run a DNS lookup against 6 resolvers located in Uzbekistan — Tashkent · Tashkent · Tashkent · Tashkent · Tashkent · Tashkent.
- Resolved
- No answer
- Checking
-
Tashkent
Uzbekistan
—
-
Tashkent
Uzbekistan
—
-
Tashkent
Uzbekistan
—
-
Tashkent
Uzbekistan
—
-
Tashkent
Uzbekistan
—
-
Tashkent
Uzbekistan
—
What checking DNS from Uzbekistan 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 Uzbekistan 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 Uzbekistan until its cached copy expires. The check confirms the new value has reached the resolvers your Uzbekistan visitors depend on.
Since 2004, most traffic between Uzbek users and Uzbek servers has stayed inside the country, exchanged over TAS-IX, the Tashkent peering fabric that made local content cheap or free to reach. That history shaped the market: the resolver a person uses is almost always the one their ISP assigns, and on fixed-line connections that usually means Uzbektelekom, the state incumbent.
Checking a record from inside Uzbekistan shows what those ISP resolvers actually return, not what a global option like 8.8.8.8 says. The gap matters because the state filters at the DNS layer. The communications regulator, O'zkomnazorat, keeps a register of banned resources, and resolvers on networks like Uztelecom enforce it, handing back a failure or a redirect for a domain that resolves cleanly everywhere else.
So a lookup that answers abroad but fails from Tashkent is usually a block, not a broken record. Testing against the resolvers Uzbeks actually depend on is the only way to tell those two apart.
- Uzbektelekom (Uztelecom)195.158.0.3 State incumbent; default resolver on most fixed-line homes
- Uzbektelekom (Uztelecom)84.54.64.35 Uztelecom's other advertised resolver, Uzonline broadband
- TPS / Texnoprosistem80.80.218.218 Tashkent ISP resolver, a TAS-IX founding member
Uzbekistan filters the internet at the DNS layer through a state register of banned resources, so answers from local ISP resolvers like Uztelecom's can differ from what you see elsewhere.
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 Uzbekistan 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 Uzbekistan 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 Uzbekistan?
It depends on the record's time-to-live, not on the country.
Resolvers in Uzbekistan 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 Uzbekistan 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 Uzbekistan, 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 Uzbekistan specifically?
Because it shows what visitors in Uzbekistan actually resolve, which can differ from a global lookup.
If your audience is in Uzbekistan, 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 Uzbekistan block websites at the DNS level?
Yes. The regulator O'zkomnazorat maintains a register of banned resources, and ISP resolvers such as Uztelecom's enforce it, so a blocked domain may return no answer or a redirect from inside the country. After a wave of unblocking in 2019, platforms including X (Twitter) and TikTok were restricted or throttled again, largely under the data-localization law. A foreign resolver like 8.8.8.8 or 1.1.1.1 often sidesteps the DNS block, which is why testing against local resolvers is the only way to see the enforced answer.
Why do some Uzbek sites resolve to a local address only visible inside the country?
Traffic exchanged over TAS-IX, the Tashkent internet exchange running since 2004, is far cheaper and faster than routes that leave Uzbekistan through its limited international gateways. Many .uz sites and caches keep nodes on TAS-IX-connected networks, so a lookup from inside the country can return a local IP that a checker abroad never sees. Comparing an in-country answer with an external one shows whether a site is serving Uzbek users from local infrastructure.
