Help me help Afrihost solve their DNS issue

0 votes

Hi,

I'm hoping this solves issues for a lot of people out there as this cannot be unique to my 2 afrihost fibre lines.

And the hope is that this community can help figure out what is going on and in-turn help all the guys who must be experiencing this in the same areas that I have both my fibre lines (Johannesburg, Glenhazel, Silvamonte + Edenvale Areas)

The Issue: Intermittent connectivity to international website (getting progressively worse)

When trying to connect to a number of international websites e.g.:

  • analytics.google.com
  • www.google.com
  • intercom.io
  • www.fiverr.com

I get almost always no response, they appear to be completely down and I cannot connect to them. 

I suspect this may be a DNS issue on Afrihosts side (I'm not a network guy so forgive me if I'm wrong here) and all the trace routes I run point to the fact that the 'routing' of the requests goes wrong for all these sites that I cannot access, as per below:

International site (FAILED)

Can be any of the sites mentioned above + numerous others

Local site

Can be any local site (that I've tried)

PS C:\WINDOWS\system32> tracert www.google.com

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

  1    <1 ms    <1 ms    <1 ms  Webcognoscere [192.168.0.1]
  2     2 ms     2 ms     2 ms  165-73-21-65.ip.afrihost.co.za [165.73.21.65]
  3     3 ms     2 ms     2 ms  169-1-21-101.ip.afrihost.co.za [169.1.21.101]
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
			
PS C:\WINDOWS\system32> tracert www.news24.com

Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Webcognoscere [192.168.0.1]
  2     2 ms     2 ms     2 ms  165-73-21-65.ip.afrihost.co.za [165.73.21.65]
  3     4 ms     2 ms     2 ms  169-1-21-101.ip.afrihost.co.za [169.1.21.101]
  4     3 ms     3 ms     3 ms  mweb.ixp.joburg [196.60.8.145]
  5    26 ms    22 ms    22 ms  te0-0-0-3.vic-p-1.optinet.net [197.80.7.65]
  6    21 ms    22 ms    22 ms  te0-0-0-0.cpt-p-2.optinet.net [197.84.4.46]
  7    21 ms    20 ms    20 ms  101.te0-0-2-0.cpt-tr-1.optinet.net [197.84.7.4]
  8    26 ms    22 ms    20 ms  197-84-247-89.cpt.mweb.co.za [197.84.247.89]
  9    22 ms    21 ms    21 ms  opti-cpt-n1-hosting.optinet.net [197.84.196.6]
 10    23 ms    21 ms    22 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146]
 11    20 ms    20 ms    20 ms  41-86-110-200.mweb.co.za [41.86.110.200]

Trace complete.
			

Everytime the request hits this node/computer/whatyoucallit (169-1-21-101.ip.afrihost.co.za) the request times out.

Compare this tracert to that while connected via a Vodacom 3G card

International site THROUGH VODACOM 3G (NOT AFRIHOST)

Connection Success

 

traceroute to www3.l.google.com (216.58.223.46), 64 hops max, 52 byte packets

 1  172.20.10.1 (172.20.10.1)  587.047 ms  672.727 ms  569.829 ms

 2  10.113.148.164 (10.113.148.164)  558.632 ms  588.185 ms  786.094 ms

 3  10.113.228.1 (10.113.228.1)  578.000 ms  607.389 ms  564.820 ms

 4  41.192.248.18 (41.192.248.18)  588.513 ms  694.598 ms  663.278 ms

 5  10.113.213.66 (10.113.213.66)  654.230 ms  607.620 ms  616.964 ms

 6  41.21.235.2 (41.21.235.2)  570.853 ms  552.792 ms  513.721 ms

 7  10.118.24.61 (10.118.24.61)  483.387 ms  590.567 ms  593.718 ms

 8  74.125.49.8 (74.125.49.8)  444.280 ms  640.140 ms  695.139 ms

 9  72.14.239.129 (72.14.239.129)  630.448 ms  576.570 ms  450.188 ms

10  jnb01s08-in-f46.1e100.net (216.58.223.46)  447.746 ms  594.748 ms  578.751 ms
			

 

The routing is obviously different between Afrihost and Vodacom, and Afrihosts routing is just not working.

My hope again is that one of you can assist as I surely can't be the only one who is experiencing this issue and the many non-technical customers of Afrihost would be completely oblivious to the issue as it's very intermittent (progressively getting worse).

I also, unfortunately, don't have much faith in Afrihosts ability to resolve this as I have 2 calls outstanding with them for 2 different lines for the same issue, one of which was logged on the 11th May 2018. It's currently 8th June.

 

 

 

asked Jun 8 in Fibre by webcognoscere (120 points)

Please log in or register to answer this question.

...