Sweden DNS Propagation Checker
Run a DNS lookup against 6 resolvers located in Sweden — Slaka · Stockholm · Stockholm · Jursla · Stockholm · Stockholm.
- Resolved
- No answer
- Checking
-
Slaka
Sweden
—
-
Stockholm
Sweden
—
-
Stockholm
Sweden
—
-
Jursla
Sweden
—
-
Stockholm
Sweden
—
-
Stockholm
Sweden
—
What checking DNS from Sweden 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 Sweden 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 Sweden until its cached copy expires. The check confirms the new value has reached the resolvers your Sweden visitors depend on.
Sweden has been ahead of the curve on DNS for twenty years: .se became the first country-code domain in the world to sign with DNSSEC back in 2005, years before the root zone followed, and Swedish operators validate more consistently than most.
The ISP scene has personality too. Bahnhof built its brand on refusing to hand over subscriber data and fighting data-retention laws through the courts, and it runs its network accordingly.
For a propagation check this has a practical edge: Swedish resolvers that validate DNSSEC will drop answers from a zone whose signatures are broken, so a key rollover mistake surfaces here before it does in laxer markets. If your zone is signed, Sweden is your canary.
- Bahnhof Stockholm ISP known for its privacy fights
- Tele2 Validates DNSSEC, in keeping with Swedish practice
- GlobalConnect Nordic fiber; answers from the Swedish end
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 Sweden 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 Sweden 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 Sweden?
It depends on the record's time-to-live, not on the country.
Resolvers in Sweden 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 Sweden 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 Sweden, 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 Sweden specifically?
Because it shows what visitors in Sweden actually resolve, which can differ from a global lookup.
If your audience is in Sweden, or you have moved hosting or mail there, checking against in-country resolvers confirms the records have reached the servers those users rely on.
My domain works everywhere except Sweden. Why?
Check your DNSSEC signatures. Swedish resolvers validate more consistently than most, and a zone with expired or mismatched signatures gets a validation failure here, meaning no answer at all, while non-validating resolvers elsewhere keep serving it happily. Fixing the signatures or rolling keys properly clears it up.
Does Bahnhof filter or log DNS queries?
Bahnhof has spent years in Swedish courts resisting data-retention and blocking demands, and it publicises that stance; it has fought orders rather than quietly implementing them. No ISP can promise a court will never compel it, but Bahnhof's track record is the closest thing Sweden has to a written guarantee.
