Morocco DNS Propagation Checker
Run a DNS lookup against 4 resolvers located in Morocco — Rabat · Rabat · Rabat · Casablanca.
- Resolved
- No answer
- Checking
-
Rabat
Morocco
—
-
Rabat
Morocco
—
-
Rabat
Morocco
—
-
Casablanca
Morocco
—
What checking DNS from Morocco 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 Morocco 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 Morocco until its cached copy expires. The check confirms the new value has reached the resolvers your Morocco visitors depend on.
In January 2016 Morocco's telecom regulator, the ANRT, ordered all three carriers — Maroc Telecom, Meditel (now Orange), and Inwi — to cut off WhatsApp, Skype, and Viber calls, first on mobile data, then on ADSL. The block held most of the year before public backlash forced a reversal. It was a reminder of who controls the pipes: nearly every connection in Morocco terminates at one of those three operators, and each hands customers its own resolver by default.
That's what makes checking DNS from inside Morocco worth doing. A Maroc Telecom subscriber resolves through 212.217.0.1, not 8.8.8.8, so the answer you see is what AS6713's recursive servers return: cache state, any operator redirection, and blocked names included. Orange and Inwi customers hit different resolvers on different networks, so one domain can resolve three ways in a single country.
Morocco has also used DNS to block a small set of sites, mainly Western Sahara and Polisario pages and some circumvention tools, so a lookup here can diverge from what a resolver abroad returns.
- Maroc Telecom (IAM)212.217.0.1 Incumbent; default resolver for most households, AS6713
- Orange Maroc (Meditel)41.87.131.33 ISP resolver (ispdns1.meditel.net.ma), AS36925
- Inwi (Wana Corporate)196.12.221.130 Third carrier's resolver (siarnaq2.inwi.ma), AS36884
Morocco has used DNS-level blocking for a narrow set of politically sensitive sites (mainly Western Sahara and Polisario content) and some circumvention tools, so resolver answers here can differ from those abroad for those specific names.
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 Morocco 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 Morocco 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 Morocco?
It depends on the record's time-to-live, not on the country.
Resolvers in Morocco 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 Morocco 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 Morocco, 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 Morocco specifically?
Because it shows what visitors in Morocco actually resolve, which can differ from a global lookup.
If your audience is in Morocco, or you have moved hosting or mail there, checking against in-country resolvers confirms the records have reached the servers those users rely on.
Which resolver does a typical Moroccan connection use?
Whatever the carrier assigns. Maroc Telecom hands out 212.217.0.1 and 212.217.0.12, both on its own AS6713 network, while Orange and Inwi run their own recursive servers on separate networks (AS36925 and AS36884). Since those three carry nearly all fixed and mobile subscribers, checking against a Moroccan node shows the record as one of their systems resolves it, not a public option like Cloudflare or Google that most users never switch to.
Does Morocco tamper with DNS, and will that change my results?
Mostly no, for ordinary domains. Morocco's best-known block — the 2016 shutdown of WhatsApp and Skype voice — was enforced at the protocol level by the carriers, not by altering DNS. But DNS-based blocking has been documented for a narrow list: Western Sahara and Polisario sites, and circumvention tools such as anonymizer.com. For those names an ISP resolver in Morocco can return a different answer than one abroad; for everything else, results match a global resolver.
