This was done now. All working fine. Will do another one tonight.
Thanks, it could be that your latency is spiking up in the evenings. Keep us posted on the results
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
This was done now. All working fine. Will do another one tonight.
Hi Peoples,
I am unable to open a couple of webpages. Is there a problem with Afrihost again? I PM'd the Afri-people but the do not reply.
Thanks
Likewise here. Intermittent DNS lookup errors. Switching to a telkom capped account and all is OK. This has been on and off since early this morning.
Reloading the page sometimes 3 times then it works.
Any issues afri-people?
DNS acting up again today and seems to be getting worse as the day goes on. I'm now fed up with this and cancelling.
Yeh, was having issues too. Also switched over to Telkom. Most international sites weren't working.
We are not seeing any DNS errors on our side at the moment, when the DNS issues flares up, are you able to ping the affected site at all? Or even run a traceroute to the affected site or IP?
Not seeing any issues on our end, have you run any troubleshooting on the connection that you can paste up here?
This is what is so strange about the situation. Don't seem to be getting any ping timeouts, but some trace routes look like they take forever to complete. I don't understand why some sites won't resolve, it doesn't seem to differentiate between international and local sites and it feels completely random in nature.
I've reconfigured my Telkom account and it feels much more responsive...
Yes. I tried 2 traces to this site and got the error: "Unable to resolve target system name www.mybroadband.co.za. Connected to a Telkom account and trace worked fine. My DNS is set to auto so it's 196.7.7.7 and 196.7.8.9.
This is happening on local and international and is intermittent. As a pc tech, "intermittent" at my end when nothing is changing at my end usually means the "intermittency" is at "the other end", ie: your end.![]()
Can I ask that you set your DNS to manual, then test using 196.7.7.7 as the primary DNS, with 196.7.8.9 as the secondary DNS.
Then see if that makes a difference, if it is the same, could you try 196.7.7.7 as the primary as 8.8.8.8 as the secondary.
We run constant monitoring on all of our DNS Clusters, and we would know as soon as one of them has an issue, as it stands they are all operational, so I wonder if it is perhaps the routing to some sites.
Issue seems completely resolved (for now) so testing as per your request would be pointless, not so? I will set it up all the same and see how it goes.
As I say, it's been intermittent and at the moment it's schweet.
Out of curiosity, what brand of modem do you have?
The non-telkom branded D-Link DSL2750U. In case you're wondering, DNS on it is set to Auto-discover.
Account is flying now, no issues whatsoever.

Spoke too soon.
Setting to Google DNS - no better. Setting to 196.7.7.7 and google, no better. Seems totally random. Can get to www.planetf1.com no problems 1 minute, then try again and nothing.
I have the exact modem, and I kept getting those types of errors as well, setting the DNS to manual seems to correct it for me. The strange thing is that I have gone through a few - lightning killed four in a year in Centurion - and this happened on two of them, so I wonder if there is perhaps not something on the modem firmware that is unhappy with automatically pulling the DNS settings from us.
I can open that perfectly fine on 196.7.7.7
But having an extremely slow connection