Kenya DNS Propagation Checker
Run a DNS lookup against 6 resolvers located in Kenya — Nairobi · Nairobi · Nairobi · Nairobi · Nairobi · Nairobi.
- Resolved
- No answer
- Checking
-
Nairobi
Kenya
—
-
Nairobi
Kenya
—
-
Nairobi
Kenya
—
-
Nairobi
Kenya
—
-
Nairobi
Kenya
—
-
Nairobi
Kenya
—
What checking DNS from Kenya 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 Kenya 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 Kenya until its cached copy expires. The check confirms the new value has reached the resolvers your Kenya visitors depend on.
Ask most people in Nairobi which DNS resolver they use and you'll get a blank look — they're on whatever Safaricom hands out. Safaricom carries the majority of Kenya's mobile and Home Fibre subscribers, so its resolver answers for a large share of the country, not a public option anyone deliberately chose.
Checking a record from inside Kenya shows what those ISP resolvers actually return, which matters because a lot of content is served locally. Google, Akamai and Meta cache inside the country and peer at KIXP, the exchange TESPOK has run in Nairobi since 2000 and in Mombasa since 2010, so a hostname often resolves to an edge node far closer than a check from Frankfurt or Ashburn would imply.
Kenya doesn't filter DNS across the board, but answers get shaped at specific moments. Operators blocked Telegram during the 2023 and 2024 KCSE exams; in 2023, OONI measured Telkom Kenya's Jambonet resolver returning a fake 192.168.7.222 for telegram.org, while Safaricom and Airtel cut the TLS handshake instead — a targeted block during exam windows, not a standing one.
- Safaricom Dominant mobile and Home Fibre carrier; its resolver by default
- Jamii Telecom (Faiba) Largest independent fibre and 4G network; own default resolver
- Airtel Kenya Second mobile operator; default resolver on Airtel data
- Telkom Kenya (Jambonet) State-owned backbone, AS12455; returned tampered DNS during exams
Kenya has no standing nationwide DNS filter, but during national secondary-school exam periods the state has directed operators to block Telegram — with Telkom Kenya's Jambonet resolver returning a fake 192.168.7.222 for telegram.org — so results for affected services can differ from what you'd otherwise expect.
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 Kenya 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 Kenya 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 Kenya?
It depends on the record's time-to-live, not on the country.
Resolvers in Kenya 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 Kenya 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 Kenya, 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 Kenya specifically?
Because it shows what visitors in Kenya actually resolve, which can differ from a global lookup.
If your audience is in Kenya, 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 Telegram sometimes fail to resolve or connect in Kenya?
During the KCSE secondary-school exams in November 2023 and 2024, the government pushed operators to block Telegram after exam papers leaked on it. In 2023, OONI measurements showed Telkom Kenya's Jambonet resolver returning a fake 192.168.7.222 for telegram.org, while Safaricom and Airtel interfered with the TLS handshake instead. The blocks lifted once exams ended, so a Kenyan DNS check for telegram.org can look completely normal outside those windows.
Does checking DNS from Kenya give different answers than checking from Europe or the US?
Often, yes. Major CDNs — Google, Akamai, Meta and Cloudflare — run caches inside Kenya and peer at KIXP in Nairobi and Mombasa, so popular hostnames resolve to an in-country or regional edge rather than a far-off datacentre. A record that points a Safaricom user at a Nairobi node can return a European or South African IP when queried from outside the country.
