Denmark DNS Propagation Checker
Run a DNS lookup against 6 resolvers located in Denmark — Fredericia · Copenhagen · Copenhagen · Frederikshavn · Hillerød · Copenhagen.
- Resolved
- No answer
- Checking
-
Fredericia
Denmark
—
-
Copenhagen
Denmark
—
-
Copenhagen
Denmark
—
-
Frederikshavn
Denmark
—
-
Hillerød
Denmark
—
-
Copenhagen
Denmark
—
What checking DNS from Denmark 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 Denmark 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 Denmark until its cached copy expires. The check confirms the new value has reached the resolvers your Denmark visitors depend on.
Denmark has history on both sides of the DNS filtering argument. Danish ISPs were among the first anywhere to block sites at resolver level, starting with a child-abuse filter in 2005 and, in 2008, one of the world's first Pirate Bay blocks.
The counterweight emerged locally too: UncensoredDNS, run by a Danish network engineer at 91.239.100.100, answers over anycast with no logging and no filtering, precisely because the national default involved both.
That tension makes Danish lookups worth reading closely. An ISP resolver shows what a typical household gets, blocks included; UncensoredDNS shows the clean answer. Your own domain should look identical on both, and confirming that from inside Denmark is the point of checking here.
- UncensoredDNS91.239.100.100 Anycast, unlogged, unfiltered, one-engineer project
- TDC Incumbent; most households, with mandatory blocks
- GlobalConnect Answers from its Nordic fiber backbone
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 Denmark 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 Denmark 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 Denmark?
It depends on the record's time-to-live, not on the country.
Resolvers in Denmark 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 Denmark 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 Denmark, 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 Denmark specifically?
Because it shows what visitors in Denmark actually resolve, which can differ from a global lookup.
If your audience is in Denmark, or you have moved hosting or mail there, checking against in-country resolvers confirms the records have reached the servers those users rely on.
What is UncensoredDNS?
A public resolver a Danish network engineer has run since 2009 as a response to ISP-level filtering: no logging, no blocking, funded by donations. It answers worldwide over anycast, but its home and its reason for existing are Danish. For testing, it is the unfiltered baseline to compare ISP answers against.
Do Danish ISPs still block domains?
Yes. The child-abuse filter continues, and rights holders have steadily expanded court-ordered piracy blocks since the 2008 Pirate Bay case. Blocks are implemented at DNS level by each ISP, so a blocked domain fails on TDC while resolving on UncensoredDNS, a gap this check makes visible.
