Belgium DNS Propagation Checker
Run a DNS lookup against 4 resolvers located in Belgium — Brussels · Saint-Gilles · Ixelles-Elsene · Kortrijk.
- Resolved
- No answer
- Checking
-
Brussels
Belgium
—
-
Saint-Gilles
Belgium
—
-
Ixelles-Elsene
Belgium
—
-
Kortrijk
Belgium
—
What checking DNS from Belgium 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 Belgium 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 Belgium until its cached copy expires. The check confirms the new value has reached the resolvers your Belgium visitors depend on.
DNS Belgium, the non-profit in Leuven that runs the .be, .brussels and .vlaanderen registries, has pushed copies of its authoritative nameservers inside the networks of the four big ISPs: Proximus, Telenet, VOO and Orange. Together they carry roughly 90% of Belgian connections, so a .be lookup usually resolves without leaving the country and keeps answering even during a DDoS.
The resolver a Belgian actually uses is almost always the one their ISP hands out, and those resolvers are where the country's blocks live. Since the 2011 Antwerp ruling against The Pirate Bay, Proximus and Telenet have applied court-ordered DNS blocks, and the Gaming Commission's list of illegal gambling sites is enforced the same way: the ISP hijacks the lookup and redirects it to a government StopPage.
Checking from inside Belgium shows your record as those ISP resolvers return it, not what 8.8.8.8 says from abroad. A domain that resolves on a public resolver but lands on the StopPage or fails on Proximus is being blocked, not lagging in propagation.
- Proximus195.238.2.21 Incumbent (ex-Belgacom/Skynet); most households, court-ordered blocks
- Telenet195.130.130.1 Largest cable operator; Flanders default, applies DNS blocks
- Orange Belgium212.224.249.245 Third national ISP (ex-Mobistar), absorbed VOO in Wallonia
Some answers seen from Belgium are shaped by state-mandated DNS blocking: ISP resolvers redirect court-ordered piracy domains and the Gaming Commission's illegal-gambling list to a government StopPage, so a blocked site can resolve on a public resolver yet fail on Proximus, Telenet or Orange.
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 Belgium 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 Belgium 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 Belgium?
It depends on the record's time-to-live, not on the country.
Resolvers in Belgium 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 Belgium 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 Belgium, 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 Belgium specifically?
Because it shows what visitors in Belgium actually resolve, which can differ from a global lookup.
If your audience is in Belgium, 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 site load on 1.1.1.1 but show a "StopPage" on my Belgian ISP?
Belgium enforces its blocks at the ISP resolver. The Gaming Commission's list of illegal gambling sites, plus court-ordered piracy blocks, are applied by Proximus, Telenet and Orange, which redirect the lookup to a federal StopPage instead of the real address. A public resolver like 1.1.1.1 or 8.8.8.8 is not bound by those orders and still returns the genuine record. If the two disagree on a site that is not yours, that gap is the national block rather than a DNS error.
Does checking a .be domain from inside Belgium behave differently?
Often, yes. DNS Belgium runs the .be, .brussels and .vlaanderen registries from Leuven and has placed authoritative copies inside Proximus, Telenet, VOO and Orange, covering about 90% of the market. A .be lookup from one of those networks tends to answer from a node in the same ISP, so it stays fast and keeps working during a DDoS. From outside Belgium you hit the public anycast set instead, which can show slightly different timing but the same records.
