Nigeria DNS Propagation Checker
Run a DNS lookup against 6 resolvers located in Nigeria — Lekki · Lagos · Abuja · Lagos · Lagos · Lagos.
- Resolved
- No answer
- Checking
-
Lekki
Nigeria
—
-
Lagos
Nigeria
—
-
Abuja
Nigeria
—
-
Lagos
Nigeria
—
-
Lagos
Nigeria
—
-
Lagos
Nigeria
—
What checking DNS from Nigeria 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 Nigeria 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 Nigeria until its cached copy expires. The check confirms the new value has reached the resolvers your Nigeria visitors depend on.
Nigeria's carriers do not all censor the same way, and OONI has measured the difference since 2017: MTN tends to tamper with DNS answers, Globacom drops routes at the TCP/IP layer, and Airtel interferes at HTTP. When the government ordered Twitter blocked in June 2021, that block landed mostly as IP and TCP filtering across the carriers, but MTN's habit of blocking in the DNS is the part a resolver check can see.
That per-carrier split still matters, because almost nobody in Nigeria picks a resolver. You take whatever MTN, Airtel, Globacom or 9mobile assigns, and MTN alone answers for roughly 90 million mobile subscribers. A lookup from inside Nigeria shows the record as those carrier resolvers return it, including the DNS tampering MTN reserves for a narrow blocklist of sensitive sites.
It also reads your CDN's geography. IXPN in Lagos now keeps more than 2 Tbps of traffic domestic, so a Nigerian resolver should reach a Lagos edge rather than one in London. This check tells you whether it does.
- MTN Nigeria102.88.11.19 Largest carrier, ~90M mobile subscribers; blocks via DNS tampering
- Airtel Nigeria105.112.1.234 Second-largest network; default resolver for its subscribers
- Globacom (Glo)41.203.80.158 Indigenous carrier; owns the Glo-1 submarine cable
- Spectranet197.255.160.101 Leading fixed-wireless broadband ISP; home and office default
Nigeria has used DNS-level blocking for a narrow set of politically sensitive sites — pro-Biafran pages flagged by monitors since 2017, and MTN in particular enforces blocks by tampering with DNS answers — so a resolver answer here can differ from one abroad for those specific names, while ordinary domains resolve normally.
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 Nigeria 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 Nigeria 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 Nigeria?
It depends on the record's time-to-live, not on the country.
Resolvers in Nigeria 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 Nigeria 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 Nigeria, 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 Nigeria specifically?
Because it shows what visitors in Nigeria actually resolve, which can differ from a global lookup.
If your audience is in Nigeria, 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 the same domain resolve one way on MTN and another on Airtel?
Because Nigeria's carriers enforce blocks at different layers. Across OONI's measurements since 2017, MTN has tended to tamper with DNS answers, Globacom to drop routes at the TCP/IP layer, and Airtel to filter at HTTP. For a domain on the blocklist that means MTN's resolver can hand back a bogus address while an Airtel line returns your real record and blocks the connection later, so the two disagree. For any domain nobody has listed, they return the same answer and the difference is just cache timing. That per-carrier gap is why a Nigerian check is worth running against more than one network.
Should I check where my CDN serves Nigerian users from?
Yes. IXPN, the Lagos exchange the NCC set up in 2006, now peers more than 100 networks and carries over 2 Tbps at peak, and Globacom lands its own Glo-1 submarine cable in Lagos, so a Nigerian resolver can legitimately be steered to a Lagos edge. If your CDN answers a Nigerian lookup with a London or Amsterdam node instead, your visitors are paying for an intercontinental round trip that sites on local hosting avoid. An in-country check shows which edge MTN, Airtel or Spectranet users actually reach.
