Afrihost New Network Feedback

Status
Not open for further replies.
Afrihost DNS server is currently having issues. Cannot access anything on imgur.com. Error: DNS_PROBE_FINISHED_NXDOMAIN

Google DNS works fine.

Same issue for me. Pretty annoying. Using VPN atm.

Also having imgur problems

Same thing. Cannot access Imgur either . Changed to Google DNS


Hi guys

Sorry about this :(
DNS errors are related to an outage we saw on 13 Feb https://www.afrihost.com/site/network_status?src=website_nav#tabs

This only seemed to affect some clients and only saw DNS lookup errors to international sites. All fixed up now though :)
 
It's not the Afrihost DNS that's an issue. Those services rely on the ns1 MTN Gallo Manor DNS proxy and CDN services. MTN Gallo Major is down. So the Afrihost DNS is fine, and is resolving to the correct addresses, but the servers cannot be reached due to the issues at MTN Gallo Manor where the DC DNS and CDN is down, and possibly the servers too...

The DNS issue and Gallo Manor were unrelated, this was a DNS outage on our end.
 
Any tests I can take a look at?
Im on my way to work now, but wil check again tonight. Strangely at 2am this morning i went to check on the download, and it was running at 360kbps which was alot better than the 19kbps before 00:00 :)
 
Im on my way to work now, but wil check again tonight. Strangely at 2am this morning i went to check on the download, and it was running at 360kbps which was alot better than the 19kbps before 00:00 :)

Thanks.
Have Telkom confirmed a resolution of congestion in your area though?
 
Thanks.
Have Telkom confirmed a resolution of congestion in your area though?

Hey Afriguy,

I know you weren't dealing with my issue (Genie was looking after my support ticket for the congestion), but I had some weird outages last night where the line would drop for 30 secs to a minute, then connect again. I was hoping it was due to the fact that it was Telkom working on the exchange to upgrade it.

It happened about 3 times, between 2PM and 8PM. Not sure if it was related to the congestion, or whether it was an Afrihost issue? I don't have any tracerts or pings or anything to look at, because it was down, then up, then down, then up. So a tracert would not show you anything.
 
Hey Afriguy,

I know you weren't dealing with my issue (Genie was looking after my support ticket for the congestion), but I had some weird outages last night where the line would drop for 30 secs to a minute, then connect again. I was hoping it was due to the fact that it was Telkom working on the exchange to upgrade it.

It happened about 3 times, between 2PM and 8PM. Not sure if it was related to the congestion, or whether it was an Afrihost issue? I don't have any tracerts or pings or anything to look at, because it was down, then up, then down, then up. So a tracert would not show you anything.

Heya!

Could be related, let's double check though. AfriGenie isn't in until a bit later, so drop me a PM with your deets and I can take a look at the logs :)
 
The DNS issue and Gallo Manor were unrelated, this was a DNS outage on our end.

Unless Afrihost host the DNS for services at MTN's DC this is unlikely that it was an Afrihost DNS issue as it impacted all ISPs. Our clients also couldn't access the local nodes for these services (international services that utilise a local DNS/CDN hosted at MTN) nor could the MTN website/shop be accessed at the time. The same was experienced across all ISP accounts, yet bypassing the local routing resolved the problem. So I highly suspect that somebody on your end has put this down to an internal issue when in fact it should be investigated by MTN and their DC NOC...
 
Unless Afrihost host the DNS for services at MTN's DC this is unlikely that it was an Afrihost DNS issue as it impacted all ISPs. Our clients also couldn't access the local nodes for these services (international services that utilise a local DNS/CDN hosted at MTN) nor could the MTN website/shop be accessed at the time. The same was experienced across all ISP accounts, yet bypassing the local routing resolved the problem. So I highly suspect that somebody on your end has put this down to an internal issue when in fact it should be investigated by MTN and their DC NOC...

Our DNS is not linked to MTN’s, as we now run on a completely discreet network. While we did have some problems with DNS – as listed on our network status page – this is not linked to MTN to the best of our knowledge.
 
Our DNS is not linked to MTN’s, as we now run on a completely discreet network. While we did have some problems with DNS – as listed on our network status page – this is not linked to MTN to the best of our knowledge.

The problem was not linked to your DNS, is what I'm telling you. All ISPs experienced the exact same problems when trying to connect to services that utilised the MTN DC infrastructure where ns1 local DC DNS/CDN services were involved, as they were the only services impacted. Point being, unless you guys host those services (which you don't) this was not linked to your DNS at all, and is in fact something that MTN need to respond about, which to date they have and simply stated "no known outage at Gallo Manor" which does not explain the cause of the problem and is an insufficient response at this point in time...
 
The problem was not linked to your DNS, is what I'm telling you. All ISPs experienced the exact same problems when trying to connect to services that utilised the MTN DC infrastructure where ns1 local DC DNS/CDN services were involved, as they were the only services impacted. Point being, unless you guys host those services (which you don't) this was not linked to your DNS at all, and is in fact something that MTN need to respond about, which to date they have and simply stated "no known outage at Gallo Manor" which does not explain the cause of the problem and is an insufficient response at this point in time...

Thanks for your concern, I'm sure our team are following their processes to ensure practices are in place to avoid this from happening again.
 
Thanks for your concern, I'm sure our team are following their processes to ensure practices are in place to avoid this from happening again.

Unlikely until MTN explain what the issue was. No "practice" on your end can/could have resolved this - only MTN can and so far there is no acknowledgment of an issue.

If you wish to get to the bottom of it, it would be best to liaise with them about it, as well as ns1 which we are in the process of doing...
 
Unlikely until MTN explain what the issue was. No "practice" on your end can/could have resolved this - only MTN can and so far there is no acknowledgment of an issue.

If you wish to get to the bottom of it, it would be best to liaise with them about it, as well as ns1 which we are in the process of doing...

I'm sure our network guys are on top of it, thanks.
 
Yes Afriguy still having the same slow internet and you call centre staff test my line and say everything is ok but they still wanted me to change modem and change all cables going to and from the modem and the results are still the same i tryed to send the test progrm data but the internet is to slow to get internet to work.
 
Last edited:
Yes Afriguy still having the same slow internet and you call centre staff test my line and say everything is ok but they still wanted me to change modem and change all cables going to and from the modem and the results are still the same i tryed to send the test progrm data but the internet is to slow to get internet to work.

Sounds like there's something else happening here :(
Drop me a PM with your details and we can run through a few checks together.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X