Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
daniellgr said:
Thanks for the info much appreciated.

So when one types in www.afrihost.co.za, the request is immediately resolved in to "afrihost.com", and presumably goes off and finds the optimized server, and that is what happens.

BUT now you do a trace route and you end up on a different IP address? Does this make sense ?
Click to expand...

Correct. Any requests to afrihost.co.za are pushed to afrihost.com.
DNS will differ as the IPs differ. Various backends and failovers have different IPs too. Our site uses multiple IPs due to a round robin type setup for load balancing.

Most large websites have this implemented.
 
daniellgr said:
Yes it does and it suggest that your server is co located at NapAfrica JHB which is at the Teraco site in Isando.
Normally reached in 13 ms over 8 hops. from my location in PTA?
Click to expand...

NAPAfrica only assists with the CDN and routing for that particular node, the site isn't hosted there :)
 
Last edited:
I have run a number of analysis tools on your Afrihost.co.za and Afrihost.com domains, and all the tests show up DMARC and Domain health errors ......

Everything may be fine when there are no network anomalies, but when there are network issues, you will find clients experiencing problems ...... which are avoidable if the errors are fixed .....

In fact a full test of your site show up 441 errors warnings and code violations on the one test I ran.

Compared to another very large organisation in SA with over 30 000 such issues on their website, you are doing very well !:D
 
Last edited:
daniellgr said:
I have run a number of analysis tools on your Afrihost.co.za and Afrihost.com domains, and all the tests show up DMARC and Domain health errors ......

Everything may be fine when there are no network anomalies, but when there are network issues, you will find clients experiencing problems ......
Click to expand...

Care to post the results here? Not aware of any issues on our site/ network.
 
What Me? an amateur needs to show an ISP how to run tests to check if their DNS setups are correct ? Please, you are the guys with the cash and the in-depth know how ......

Not to talk of making sure their website code complies with standards .....

For free too? No way, pay me and I will gladly teach your guys how to suck eggs.
 
daniellgr said:
What Me? an amateur needs to show an ISP how to run tests to check if their DNS setups are correct ? Please, you are the guys with the cash and the in-depth know how ......

Not to talk of making sure their website code complies with standards .....

For free too? No way, pay me and I will gladly teach your guys how to suck eggs.
Click to expand...

As mentioned previously, there are no issues with our website setup or DSL network.
If you're seeing issues that affects your experience I'll need to see some test data to advise further.
 
AfriGenie, hows that line issue of mine coming along, have you followed up with Telkom yet, didn't they say by the end of this week?
 
bigboy529 said:
AfriGenie, hows that line issue of mine coming along, have you followed up with Telkom yet, didn't they say by the end of this week?
Click to expand...

I'm sure he's been following up religiously :) I've asked him to check for any recent feedback and drop you a PM with any news.
 
AfriGenie said:
It's not quite a bottleneck in the strictest sense of the word, the traceroute is still able to resolve to the target destination. That specific network point could be under more load than usual, which means it will de-prioritize non-essential traffic such as ICMP traffic requests.

I've asked our Team to check what's going on.
Click to expand...

Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

tracert www.afrihost.co.za

Tracing route to www.afrihost.co.za [41.86.112.68]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 11 ms 11 ms 11 ms 169-0-44-1.ip.afrihost.co.za [169.0.44.1]
3 * * * Request timed out. <<<<<<<<<<<<<<<<<<<<<<<-----I call it a bottleneck
4 17 ms 13 ms 13 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 16 ms 14 ms 13 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 12 ms 12 ms 13 ms optinet.ct1.napafrica.net [196.10.140.15]
7 38 ms 35 ms 35 ms bu-ether1.cpt-p-1.optinet.net [197.84.7.33]
8 37 ms 34 ms 35 ms te0-0-0-0.vic-p-2.optinet.net [197.84.4.35]
9 33 ms 32 ms 33 ms 102.te0-0-2-0.vic-tr-1.optinet.net [197.80.7.36]
10 33 ms 39 ms 34 ms 197-81-226-77.jhb.mweb.co.za [197.81.226.77]
11 33 ms 34 ms 34 ms 197-81-226-53.jhb.mweb.co.za [197.81.226.53]
12 35 ms 34 ms 33 ms 197-81-229-2.jhb.mweb.co.za [197.81.229.2]
13 33 ms 33 ms 32 ms 197-81-229-9.jhb.mweb.co.za [197.81.229.9]
14 32 ms 31 ms 31 ms 41-86-112-68.mweb.co.za [41.86.112.68]

Trace complete.


and

tracert www.afrihost.com

Tracing route to www.afrihost.com [190.93.241.183]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 10 ms 10 ms 11 ms 169-0-44-1.ip.afrihost.co.za [169.0.44.1]
3 * * * Request timed out. <<<<<<<<<<<<<-----bottleneck
4 14 ms 13 ms 13 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 14 ms 13 ms 13 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 13 ms 11 ms 13 ms africainx.ct1.napafrica.net [196.10.140.7]
7 28 ms 29 ms 29 ms CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za.africainx.net [41.84.13.228]
8 28 ms 29 ms 28 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59]
9 29 ms 28 ms 29 ms 190.93.241.183

Trace complete.
 
Here.

Tracing route to www.google.com [216.58.223.4]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 15 ms 15 ms 14 ms 169-0-5-1.ip.afrihost.co.za [169.0.5.1]
3 * * * Request timed out.
4 168 ms 81 ms 66 ms 169-1-5-250.ip.afrihost.co.za [169.1.5.250]
5 84 ms 45 ms 11 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 222 ms 200 ms 112 ms 169-1-5-243.ip.afrihost.co.za [169.1.5.243]
7 229 ms 149 ms 146 ms 72.14.237.239
8 77 ms 49 ms 63 ms jnb01s07-in-f4.1e100.net [216.58.223.4]

Trace complete.

Anything else?
 
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
 
Slaught3r said:
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Click to expand...
Thats pretty bad. Which area are you in pal?
 
Slaught3r said:
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Click to expand...

The reason its timing out to that ip is because you are still on the old system where you get a reply on the 2nd hop. The timing out on the 3rd hop and terrible latency on further hops is pretty bad though.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X