Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
My router is a Dlink 2750u and its running fine on the 2740b Model :), I'm using Ethernet to answer Iceman's Question. If its a telkom router, it could be blocking the Telnet port :P, if that's the case. Create a port forwarding rule for port 23 and add a static IP on your computer and assign the port to that IP and try again. Just remember to delete the port afterwards and set you pc back to DHCP :). Also note the Netgear message about debug mode.

View attachment 364634

Don't think you have to change it to static if it's just for a day, your router should lease the IP long enough for a night.
 
Recently upgraded to 20mbit. Using Vox I get around 16mbit.

Thinking that Afrihost is better than Vox, I switched over to an Afrihost account and only get around 7.7mbit :(
 
Recently upgraded to 20mbit. Using Vox I get around 16mbit.

Thinking that Afrihost is better than Vox, I switched over to an Afrihost account and only get around 7.7mbit :(

Hhhmm, that's a bit odd.
Any special setup on your end?
 
Hi

Line stats hardly ever stay the same, there are so many factors that bring in change.
Either way, I'll happily log a fault for you - please PM me the affected number and the ticket ref#.

I'm sorry, but I have to disagree with you there.

My SNR never changed (well, twice, one line fault and one faulty router) in 7 years at my previous house, and now at my second house which I've been living at for a year.

Ditto, I have line stat logs I have kept for more than 15 years, and the ONLY time they have changed is when there has been a cable fault, and the stats after proper repair are as they were before ....
 
Ditto, I have line stat logs I have kept for more than 15 years, and the ONLY time they have changed is when there has been a cable fault, and the stats after proper repair are as they were before ....

I don't think I was trying to convey that all lines change, although SNR margins are known to change.
Some clients are lucky with solid DSL lines, otherwise see quite a bit of variation around stability. All depends on how the area is setup.
 
Based on the posts in this thread

I did a trace route to the both Afrihost.com and Afrihost.co.za.

Could you provide some insight as to why both of these exist and why the results are so different, if both these devices belong to Afrihost?

Code:
Tracing route to www.afrihost.com [190.93.242.183]
over a maximum of 20 hops:

  1    <1 ms    <1 ms     1 ms  *************
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    13 ms    13 ms    13 ms  ipc-up-2.north.telkomsa.net [105.228.0.6]
  5    13 ms    12 ms    13 ms  ipc-aggr-1.north.telkomsa.net [105.224.0.13]
  6    13 ms    13 ms    13 ms  jb1-pr-02-te0-1-0.net.telkomsa.net [105.187.249.2]
  7    13 ms    13 ms    13 ms  cloudflare.jb1.napafrica.net [196.46.25.198]
  8    14 ms    13 ms    13 ms  190.93.242.183

Trace complete.

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

  1     1 ms     1 ms    <1 ms  ****************
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *       12 ms    13 ms  ipc-up-2.north.telkomsa.net [105.228.0.6]
  5    13 ms    12 ms    13 ms  ipc-aggr-1.north.telkomsa.net [105.224.0.13]
  6    33 ms    33 ms    33 ms  ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
  7    33 ms    34 ms    33 ms  ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
  8    34 ms    34 ms    34 ms  optinet.ct1.napafrica.net [196.10.140.145]
  9    35 ms    38 ms    38 ms  bu-ether1.cpt-p-1.optinet.net [197.84.7.33]
 10    35 ms    38 ms    38 ms  te0-0-0-0.vic-p-2.optinet.net [197.84.4.35]
 11    35 ms    34 ms    35 ms  102.te0-0-2-0.vic-tr-1.optinet.net [197.80.7.36]
 12    35 ms    34 ms    33 ms  197-81-226-77.jhb.mweb.co.za [197.81.226.77]
 13    35 ms    35 ms    36 ms  197-81-226-53.jhb.mweb.co.za [197.81.226.53]
 14    35 ms    34 ms    35 ms  197-81-229-2.jhb.mweb.co.za [197.81.229.2]
 15    35 ms    33 ms    34 ms  197-81-229-9.jhb.mweb.co.za [197.81.229.9]
 16    35 ms    34 ms    34 ms  41-86-112-68.mweb.co.za [41.86.112.68]

That is interesting.
AFAIK, the domain setup from our end is that the .co.za is only an alias for the .com.

I'll see what insights our team have on this :)

Any FB yet?
 
Okay it is an "alias" ,but then I need help to understand why the one ends up at IP address 41.86.112.68 (mweb.co.za), and the other ends up at 190.93.241.183 .... ?

The CDN/ failover is probably setup like that.
Our website runs off a pretty complex stack.
 
Well do you agree with the following definition of an "alias" in relation to the Internet?

One of several alternative hostnames with the same Internet address

If so then IF "afrihost.co.za" is an alias for "afrihost.com" then it should resolve to the same IP address??

Or am I wrong just looking for help to understand these things .....
 
Well do you agree with the following definition of an "alias" in relation to the Internet?



If so then IF "afrihost.co.za" is an alias for "afrihost.com" then it should resolve to the same IP address??

Or am I wrong just looking for help to understand these things .....

The simplest alias in DNS terms can point to the same IP, yes. It's usually a C Name of the root entry.
There are various layers to it and is split into various front/ backend processes, connects to a CDN and also has failover/ load balancing measures.

It's impossible to browse to afrihost.co.za - it simply redirects to afrihost.com, thus pulls content from the .com.
 
The simplest alias in DNS terms can point to the same IP, yes. It's usually a C Name of the root entry.
There are various layers to it and is split into various front/ backend processes, connects to a CDN and also has failover/ load balancing measures.

It's impossible to browse to afrihost.co.za - it simply redirects to afrihost.com, thus pulls content from the .com.

Got this of wiki, does this describe the process?

https://en.wikipedia.org/wiki/Content_delivery_network

Most CDNs are operated as an (ASP) on the Internet (also known as on-demand software or software as a service (SaaS)). An increasing number of Internet network owners have built their own CDNs to improve on-net content delivery, reduce demand on their own telecommunications infrastructure, and to generate revenues from content customers. This might include offering access to media streaming to internet service subscribers. Some larger software companies such as Microsoft build their own CDNs in tandem with their own products. Examples include Microsoft Azure CDN,[3] Amazon CloudFront,[4] and Google Cloud CDN.[5]

Here content (potentially multiple copies) may exist on several servers. When a user makes a request to a CDN hostname, DNS will resolve to an optimized server (based on location, availability, cost, and other metrics) and that server will handle the request.
 
Got this of wiki, does this describe the process?

https://en.wikipedia.org/wiki/Content_delivery_network

Most CDNs are operated as an (ASP) on the Internet (also known as on-demand software or software as a service (SaaS)). An increasing number of Internet network owners have built their own CDNs to improve on-net content delivery, reduce demand on their own telecommunications infrastructure, and to generate revenues from content customers. This might include offering access to media streaming to internet service subscribers. Some larger software companies such as Microsoft build their own CDNs in tandem with their own products. Examples include Microsoft Azure CDN,[3] Amazon CloudFront,[4] and Google Cloud CDN.[5]

Here content (potentially multiple copies) may exist on several servers. When a user makes a request to a CDN hostname, DNS will resolve to an optimized server (based on location, availability, cost, and other metrics) and that server will handle the request.

For the CDN bit, indeed :)
Our frontend runs via CloudFlare AFAIK.
 
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 ?

Does this indicate that there are multiple copies of the content one on an mweb server, and the other on your own server?
 
Last edited:
For the CDN bit, indeed :)
Our frontend runs via CloudFlare AFAIK.

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?

If one pings the other address it takes 35 ms or a trace route now goes over a complicated route involving 16 hops and ends up pickling all the way to Cape Town before finding its way back to JHB. ......

I would have thought ( as with other sites using the same principle) that even a trace route would resolve itself out and find the correct optimal routing .....

I will find an example ...
 
Last edited:
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X