Rarely do I use Safaricom for internet but somehow I recently came by one of their generous data bundles. Naturally I decided to make use of it on my desktop to at least get some work done.
Usually I just tether my phone to my desktop’s Wi-Fi adapter rather than using my trusty unlocked Safaricom modem. It is much faster not to mention I don’t have to fret about missing any calls, though I can cumbersomely answer them using the modem.
Unfortunately, this particular Wi-Fi hotspot became quite problematic unlike what I’m used to when using Telkom or Airtel Kenya bundles. The problem: the computer successfully connects to the Wi-Fi hotspot but reports it has no Internet.
Thinking something might be wrong with the hotspot I tried both USB and Bluetooth tethering both of which resulted with the same error.
Next I tried running Windows Network Diagnostics which reported the following:
Your computer appears to be correctly configured but the device or resource (dns server) is not responding.
Thinking I had found the problem, I tried changing the DNS servers for the hotspot on my computer including to those of Google DNS, Open DNS and CloudFlare DNS none of which worked. I even went as far as changing the DNS server on my rooted Android phone which of course failed spectacularly.
Meanwhile I could still use the data bundle normally on my phone. A hotspot made with my Telkom line on the second SIM slot however worked perfectly regardless of which DNS server I used.
At this point I started suspecting foul play by Safaricom, after all some network operators are known to block tethering for end users. Nevertheless, I could not find evidence of this.
So after trying different public DNS servers with no actual change I decided to search for alternative DNS servers from Safaricom.
The first place I landed was on a forum discussing Your Freedom VPN. While completely unrelated to this, somewhere in that thread someone suggested to use a different DNS server: 184.108.40.206.
All this time my Safaricom internet had been using the DNS Server: 220.127.116.11. So I changed it to 18.104.22.168 and what do you know, the hotspot started working.
Now I’m not implying that this specific DNS Server will always solve this error for you. Safaricom uses different DNS servers and this happens to be just one of them.
Nevertheless, one thing is clear form this: should you encounter such an issue the first place you should go looking is in your DNS server settings. Try different public DNS and should those fail too, try different Safaricom DNS servers.
Now I should mention few moments later after making the change the new DNS server started acting up – it would lose internet for a while then recover on its own.
I suppose it wouldn’t be farfetched to just conclude Safaricom has unreliable DNS servers, which is rather amusing as I’ve never before experienced this kind of issue with their “unreliable” competitors.