Slovenia DNS Propagation Checker
Run a DNS lookup against 6 resolvers located in Slovenia — Ljubljana · Ljubljana · Ljubljana · Ljubljana · Ljubljana · Izola.
- Resolved
- No answer
- Checking
-
Ljubljana
Slovenia
—
-
Ljubljana
Slovenia
—
-
Ljubljana
Slovenia
—
-
Ljubljana
Slovenia
—
-
Ljubljana
Slovenia
—
-
Izola
Slovenia
—
What checking DNS from Slovenia 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 Slovenia 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 Slovenia until its cached copy expires. The check confirms the new value has reached the resolvers your Slovenia visitors depend on.
Slovenia runs a surprising share of its DNS through one non-profit. ARNES, the academic and research network founded in 1992, manages the .si registry, hosts the national DNS infrastructure, runs the SI-CERT incident team, and operates the SIX exchange in Ljubljana where the country's networks peer.
The resolver an ordinary household uses, though, is whatever its access provider assigns: Telekom Slovenije's SIOL, Telemach's cable network, or A1, not a public resolver anyone picked. Checking a record from inside Slovenia shows what those ISP resolvers actually return, which is not always what 8.8.8.8 hands back from abroad.
Since a 2010 change to the Gaming Act, those same resolvers carry state-ordered gambling blocks. The Financial Administration (FURS) flags unlicensed foreign casino and betting domains, and providers redirect them at the DNS layer to a government warning page. A betting site that resolves cleanly on Cloudflare but lands on a stop page through SIOL or Telemach is blocked, not broken.
- Telekom Slovenije (SIOL)193.189.160.13 Incumbent; default resolver for most fixed-line homes, carries FURS gambling blocks
- Telemach84.20.224.66 Largest cable operator; applies the same mandated gambling blocks
- A1 Slovenija Second major operator (absorbed Amis); default resolver on its lines
- ARNES193.2.1.66 Academic/research network; runs the .si registry and national DNS infrastructure
Answers from Slovenian ISP resolvers reflect the state's mandatory gambling blocklist: under the Gaming Act, providers redirect unlicensed betting and casino domains flagged by the Financial Administration (FURS) to a government warning page, so a blocked domain can resolve on a public resolver yet fail through Telekom Slovenije or Telemach.
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 Slovenia 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 Slovenia 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 Slovenia?
It depends on the record's time-to-live, not on the country.
Resolvers in Slovenia 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 Slovenia 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 Slovenia, 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 Slovenia specifically?
Because it shows what visitors in Slovenia actually resolve, which can differ from a global lookup.
If your audience is in Slovenia, 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 Slovenian connection?
Slovenia's Gaming Act makes ISPs block unlicensed foreign gambling sites at the DNS level. The Financial Administration (FURS) maintains the blacklist, and Telekom Slovenije, Telemach, A1 and the others redirect a listed domain to an official warning page instead of its real address. A public resolver outside the country, such as Google's 8.8.8.8 or Cloudflare's 1.1.1.1, does not carry that list and returns the genuine record, which is why switching resolvers is the usual local workaround. It only defeats the DNS block, though: where FURS pursues payment-level or deep-packet enforcement, a clean lookup does not guarantee the site is reachable.
Who runs .si, and does checking a .si domain from Slovenia behave differently?
The .si registry is run by ARNES, the academic and research network, which also operates the national DNS infrastructure and the SIX internet exchange in Ljubljana where the major ISPs peer. Because the authoritative .si servers and most Slovenian interconnection sit inside the country, a .si lookup from a Slovenian vantage tends to resolve close to home and answer quickly. The records themselves match what you would see abroad; what an in-country check adds is confirmation that Slovenian caches have picked up your change, and whether a gambling-blocklist redirect is in play.
