Switzerland DNS Propagation Checker
Run a DNS lookup against 3 resolvers located in Switzerland — Geneva · Menziken · Winterthur.
- Resolved
- No answer
- Checking
-
Geneva
Switzerland
—
-
Menziken
Switzerland
—
-
Winterthur
Switzerland
—
What checking DNS from Switzerland 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 Switzerland 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 Switzerland until its cached copy expires. The check confirms the new value has reached the resolvers your Switzerland visitors depend on.
Switzerland is home to the most privacy-forward of the big public resolvers. Quad9, which answers at 9.9.9.9 worldwide, moved its legal home to Zurich in 2021 specifically to put itself under Swiss privacy law, and it blocks known-malicious domains while promising not to log who asked.
Domestically, Swisscom resolvers serve most households, while Init7, the Winterthur operator best known for selling symmetric 25-gigabit fiber to consumers, runs its own.
Checking from Swiss servers is useful in the usual ways, confirming propagation to local caches, with one extra wrinkle: Quad9 filters for security, so a domain flagged by its threat feeds stops resolving there even though every other resolver still answers. Switzerland is where you notice.
- Quad99.9.9.9 Zurich foundation; blocks known-malicious domains
- Init7 Unfiltered resolvers from Winterthur
- Swisscom Default caches for most Swiss households
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 Switzerland 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 Switzerland 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 Switzerland?
It depends on the record's time-to-live, not on the country.
Resolvers in Switzerland 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 Switzerland 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 Switzerland, 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 Switzerland specifically?
Because it shows what visitors in Switzerland actually resolve, which can differ from a global lookup.
If your audience is in Switzerland, or you have moved hosting or mail there, checking against in-country resolvers confirms the records have reached the servers those users rely on.
Is Quad9 really subject to Swiss privacy law?
Yes. The foundation moved its headquarters from California to Zurich in 2021, putting its query handling under Swiss privacy rules. It states it does not log individual queries. The filtering it applies is security-driven, blocking domains its threat-intelligence feeds mark as malicious, not content policy.
Why would a domain fail on 9.9.9.9 but work on other resolvers?
Quad9 blocks domains that appear in its malware and phishing feeds. If your domain was compromised, or a feed flagged it by mistake, Quad9 returns nothing while unfiltered resolvers keep answering. Quad9 publishes a tool for checking whether a domain is blocked and a process for disputing it.
