France DNS Propagation Checker
Run a DNS lookup against 6 resolvers located in France — Paris · Paris · Roubaix · Montesson · Paris · Paris.
- Resolved
- No answer
- Checking
-
Paris
France
—
-
Paris
France
—
-
Roubaix
France
—
-
Montesson
France
—
-
Paris
France
—
-
Paris
France
—
What checking DNS from France 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 France 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 France until its cached copy expires. The check confirms the new value has reached the resolvers your France visitors depend on.
France has a DNS culture of its own. FDN, an association-run ISP founded in 1992 and the oldest in the country, operates a public resolver at 80.67.169.12 as a matter of principle: unfiltered and run by volunteers.
The big commercial providers sit at the other end of the spectrum, since French courts regularly order Orange, SFR and the other national ISPs to block domains at resolver level, from pirate streaming sites to Sci-Hub.
The practical consequence is that the answer a French visitor gets depends heavily on which resolver their connection uses. Checking from inside France shows you that spread, and whether your own records have reached both the filtered and unfiltered sides of it.
- FDN80.67.169.12 Volunteer association; unfiltered since the dial-up era
- Orange Default household resolver; applies court-ordered blocks
- SFR Applies the same court-ordered blocks by default
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 France 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 France 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 France?
It depends on the record's time-to-live, not on the country.
Resolvers in France 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 France 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 France, 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 France specifically?
Because it shows what visitors in France actually resolve, which can differ from a global lookup.
If your audience is in France, 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 FDN's resolver private?
FDN is a volunteer-run association that has opposed DNS blocking and mass surveillance in French courts, and its resolver does not filter answers. Private in the absolute sense, no resolver is: whoever runs one can technically see your queries. But FDN's policies are published and its incentives are not commercial.
Why does a domain resolve on FDN but not on Orange?
French courts order the major ISPs to block specific domains at resolver level, and Orange implements those orders. FDN does not. If the two disagree about a domain that is not yours, that is filtering; if they disagree about your own domain right after a change, that is ordinary cache lag.
