Algeria

Algeria DNS Propagation Checker

Run a DNS lookup against the Algiers resolver in Algeria.

Please enter a valid domain name.

Checking from 1 location
  • Resolved
  • No answer
  • Checking
Algiers36.65° N, 3.15° E
  • DZ Algiers Algeria

What checking DNS from Algeria tells you

Caching is local

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.

The in-country view

Checking from Algeria 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.

When it matters

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 Algeria until its cached copy expires. The check confirms the new value has reached the resolvers your Algeria visitors depend on.

Field notes

Every June, when more than 700,000 students sit Algeria's baccalauréat, the state leans on the network. After exam answers leaked across Facebook in 2016, the government began blocking social media during exams, escalated to nationwide shutdowns in 2018, and by 2024 had settled on timed daily blackouts and targeted blocking of WhatsApp, Telegram and Signal rather than pulling the whole country offline.

Outside those windows, the resolver behind most Algerian connections belongs to Algérie Télécom, the state incumbent (AS36947) carrying nearly every fixed line under its Idoom and Djaweb brands, or to one of three mobile networks — Mobilis, Djezzy and Ooredoo — which between them hold every mobile subscription. None publishes a branded public resolver; a home takes whatever its line hands out over DHCP.

Checking a record from inside Algeria shows what those carrier resolvers actually return. During exam season, or for a platform ISPs have been told to block, that answer can differ from what 8.8.8.8 reports abroad — which is the reason to test locally.

Local resolvers
  • Algérie Télécom (Djaweb / Idoom) State incumbent (AS36947); nearly all fixed lines, DHCP resolvers
  • Mobilis (ATM Mobilis) State-owned mobile network; disrupted during exam-season blocks
  • Djezzy (Optimum Telecom Algérie) Major mobile network, state-controlled since 2015
  • CERIST / NIC.DZ193.194.64.242 Runs .dz registry since 1994; authoritative, not a public resolver

DNS answers from Algeria's carrier resolvers can be shaped by state-ordered blocking — most visibly the annual restrictions during baccalauréat exams, when social and messaging platforms are cut — so a record checked through a local ISP may differ from what a public resolver abroad returns.

How DNS propagation works

The TTL timer

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.

Staggered expiry

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 Algeria 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 Algeria 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 Algeria?

It depends on the record's time-to-live, not on the country.

Resolvers in Algeria 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 Algeria 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 Algeria, 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 Algeria specifically?

Because it shows what visitors in Algeria actually resolve, which can differ from a global lookup.

If your audience is in Algeria, 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 can a DNS lookup from Algeria differ from one abroad during June?

Since 2016, when baccalauréat answer sheets leaked on social media, Algeria has restricted the internet during exams — first by blocking Facebook, Twitter and Instagram, then with nationwide shutdowns from 2018, and since 2024 with timed daily blackouts plus targeted blocking of WhatsApp, Telegram, Signal and Messenger. Much of it is enforced at the ISP level, so a record checked through an Algérie Télécom or mobile resolver during an exam window can come back blocked or unreachable while the same name resolves cleanly on a resolver outside the country.

Does Algeria run a national public DNS resolver, and who runs .dz?

There is no widely used government or national public recursive resolver. CERIST, the state research centre, has managed the .dz country-code domain since Algeria first connected to the internet in 1994, and runs the authoritative NIC.DZ nameservers (ns1.nic.dz at 193.194.64.242, alongside ns-dz.afrinic.net) — but those answer for the .dz zone, not general recursive queries. Households take whatever Algérie Télécom or their mobile carrier assigns, and the technically inclined switch to 8.8.8.8 or 1.1.1.1, which is also the usual route around local blocks.