Serbia DNS Propagation Checker
Run a DNS lookup against 6 resolvers located in Serbia — Niš · Obrovac · Belgrade · Belgrade · Belgrade · Novi Bečej.
- Resolved
- No answer
- Checking
-
Niš
Serbia
—
-
Obrovac
Serbia
—
-
Belgrade
Serbia
—
-
Belgrade
Serbia
—
-
Belgrade
Serbia
—
-
Novi Bečej
Serbia
—
What checking DNS from Serbia 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 Serbia 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 Serbia until its cached copy expires. The check confirms the new value has reached the resolvers your Serbia visitors depend on.
When Serbia's Gambling Law took effect in 2020, the Games of Chance Administration inside the Ministry of Finance got a new lever: hand ISPs a list of unlicensed foreign betting sites, and within 72 hours those domains go dark for Serbian users. A1 Serbia was the first to pull them, in October 2020. When the Belgrade digital-rights group SHARE Foundation asked to see the notice and the banned-URL list, the administration refused and cited state gambling revenue, so the blocklist stays secret.
Almost nobody in Serbia picks a resolver. A household takes whatever Telekom Srbija, the majority state-owned incumbent, or SBB, the largest cable operator, hands out over DHCP, and those resolvers carry the gambling blocks. Checking a record from inside Serbia shows what those defaults return, blocks included, not the clean answer 8.8.8.8 gives from abroad.
Outside gambling the picture is calm, and Freedom House finds no political or social content blocked, so for an ordinary domain a Serbian check is a plain propagation read of whether the incumbent caches hold your records.
- Telekom Srbija (mts) Majority state-owned incumbent; default resolver, most households
- SBB (Serbia Broadband)89.216.1.30 Largest cable operator (United Group); anycast resolver
- A1 Serbia First to enforce the 2020 gambling blocklist
- Google Public DNS8.8.8.8 Common workaround for the ISP gambling blocks
Serbian ISP resolvers enforce the state's blocklist of unlicensed foreign gambling sites at the DNS layer, so a blocked betting domain can resolve on a public resolver yet fail on Telekom Srbija or SBB. Other content is broadly accessible.
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 Serbia 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 Serbia 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 Serbia?
It depends on the record's time-to-live, not on the country.
Resolvers in Serbia 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 Serbia 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 Serbia, 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 Serbia specifically?
Because it shows what visitors in Serbia actually resolve, which can differ from a global lookup.
If your audience is in Serbia, 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 betting site load on 8.8.8.8 but not on my mts or SBB connection?
Serbia's block on unlicensed foreign gambling sites is applied at the ISP resolver. Once the Games of Chance Administration lists a domain, Telekom Srbija, SBB and the other providers stop resolving it within 72 hours, while a public resolver outside their control, like Google's 8.8.8.8 or Cloudflare's 1.1.1.1, still returns the real address. That gap is why switching DNS is the standard local workaround for those sites, and it is also the tell that you are looking at a state block rather than a broken record.
Is anything besides gambling blocked in Serbia's DNS?
Not much. The gambling blocklist is the one standing, state-ordered filter, and even that stays hidden: SHARE Foundation's freedom-of-information requests for the banned-URL list were refused. Freedom House rates Serbia's net Partly Free but records no blocking of political, news or social content. So for anything other than unlicensed betting, a Serbian resolver such as SBB's anycast service at 89.216.1.30 returns the same records a resolver abroad would, and the differences you see are ordinary cache timing.
