Rain DNS Issues

racer · Mar 8, 2018

Hi

There's some serious issues with DNS on Rain's network, could you please escalate through to them...

Eg, I can't get to dailymail.co.uk as Rain's DNS is pointing to a UK server, where its supposed to point to a locally based Akamai server.. All other ZA ISP's point correctly to the Akamai server, have tested.

2nd example, see pic attached of what Microsoft website looks like using Rain's network. Again, its not going to the local server like it should be.. On my Telkom sim, the site is fine and local and displays prices in ZAR as it should. On Rain's network, the site doesn't load correctly, prices are in USD as its using the incorrect server....

tks...

AfriFella · Mar 8, 2018

racer said:
Hi

There's some serious issues with DNS on Rain's network, could you please escalate through to them...

Eg, I can't get to dailymail.co.uk as Rain's DNS is pointing to a UK server, where its supposed to point to a locally based Akamai server.. All other ZA ISP's point correctly to the Akamai server, have tested.

2nd example, see pic attached of what Microsoft website looks like using Rain's network. Again, its not going to the local server like it should be.. On my Telkom sim, the site is fine and local and displays prices in ZAR as it should. On Rain's network, the site doesn't load correctly, prices are in USD as its using the incorrect server....

tks...

Hi Racer. Thanks for reaching out. We're not aware of any general Rain DNS issues at the moment. Is this a recent development?

Could you please send me a traceroute to the affected site?

racer · Mar 8, 2018

AfriFella said:
Hi Racer. Thanks for reaching out. We're not aware of any general Rain DNS issues at the moment. Is this a recent development?

Could you please send me a traceroute to the affected site?

Its been about a week now...

This is my traceroute to dailymail.co,uk from RAIN and from Telkom:

1. RAIN

>tracert dailymail.co.uk

Tracing route to dailymail.co.uk [41.73.43.137]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms homerouter.cpe [192.168.200.1]
2 * * * Request timed out.
3 51 ms 53 ms 42 ms 41.73.34.193
4 45 ms 44 ms 38 ms 41.73.34.205
5 * * * Request timed out.
6 39 ms 40 ms 38 ms noidea.sainet.co.za [41.73.34.1]
7 54 ms 38 ms 36 ms 41.73.42.129
8 68 ms 52 ms 37 ms 41.216.199.4
9 40 ms 43 ms 39 ms bnkcrs01-vl677.neology.io [41.216.193.66]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 ^C

2. TELKOM

>tracert dailymail.co.uk

Tracing route to dailymail.co.uk [105.225.1.233]
over a maximum of 30 hops:

1 2 ms 1 ms <1 ms 192.168.43.1
2 * * * Request timed out.
3 19 ms 21 ms 42 ms 105-187-252-109.ti-sen.telkomsa.net [105.187.252.109]
4 27 ms 42 ms 16 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
5 45 ms 41 ms 46 ms cen-pr-02-be200-vl1.net.telkomsa.net [105.228.0.17]
6 40 ms 42 ms 48 ms cen-pr-02-be200-vl1.net.telkomsa.net [105.228.0.17]
7 42 ms 48 ms 43 ms cen-pr-02-te0-7-0-21-vl12.net.telkomsa.net [105.187.249.118]
8 47 ms 39 ms 40 ms a105-225-1-233.deploy.akamaitechnologies.com [105.225.1.233]

Trace complete.

I've realised it might not be a DNS problem after all, as both IPs point to Akamai servers,.. routing problem perhaps?

AfriFella · Mar 9, 2018

racer said:
Its been about a week now...

This is my traceroute to dailymail.co,uk from RAIN and from Telkom:

1. RAIN

>tracert dailymail.co.uk

Tracing route to dailymail.co.uk [41.73.43.137]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms homerouter.cpe [192.168.200.1]
2 * * * Request timed out.
3 51 ms 53 ms 42 ms 41.73.34.193
4 45 ms 44 ms 38 ms 41.73.34.205
5 * * * Request timed out.
6 39 ms 40 ms 38 ms noidea.sainet.co.za [41.73.34.1]
7 54 ms 38 ms 36 ms 41.73.42.129
8 68 ms 52 ms 37 ms 41.216.199.4
9 40 ms 43 ms 39 ms bnkcrs01-vl677.neology.io [41.216.193.66]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 ^C

2. TELKOM

>tracert dailymail.co.uk

Tracing route to dailymail.co.uk [105.225.1.233]
over a maximum of 30 hops:

1 2 ms 1 ms <1 ms 192.168.43.1
2 * * * Request timed out.
3 19 ms 21 ms 42 ms 105-187-252-109.ti-sen.telkomsa.net [105.187.252.109]
4 27 ms 42 ms 16 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
5 45 ms 41 ms 46 ms cen-pr-02-be200-vl1.net.telkomsa.net [105.228.0.17]
6 40 ms 42 ms 48 ms cen-pr-02-be200-vl1.net.telkomsa.net [105.228.0.17]
7 42 ms 48 ms 43 ms cen-pr-02-te0-7-0-21-vl12.net.telkomsa.net [105.187.249.118]
8 47 ms 39 ms 40 ms a105-225-1-233.deploy.akamaitechnologies.com [105.225.1.233]

Trace complete.

I've realised it might not be a DNS problem after all, as both IPs point to Akamai servers,.. routing problem perhaps?

Thanks for testing.

I'm going to pass this info onto our NOC Team to investigate.

racer · Mar 11, 2018

AfriFella said:
Thanks for testing. I'm going to pass this info onto our NOC Team to investigate.

Sorry to be impatient, but this needs to be resolved... I have a lot of work on office.com and I've been buying unnecceary Telkom data just to work on that site.... see attached pic for what it looks like on Rain's network....

AfriFella · Mar 12, 2018

racer said:
Sorry to be impatient, but this needs to be resolved... I have a lot of work on office.com and I've been buying unnecceary Telkom data just to work on that site.... see attached pic for what it looks like on Rain's network....View attachment 505991

We're unable to replicate results on our side.

Do you have any specific DNS settings configured on your router or PC?

Chris8 · Mar 19, 2018

Issue confirmed

My brother and I also have Rain/Afrihost LTE-A routers, and experience the same problems.

We mostly have problems with Akamai resources, for example:
https://guzzle.akamaized.net/media/suppliers/Game-1.png
ttps://bitmovin-a.akamaihd.net/bitmovin-player/stable/7.5/bitmovinplayer.js

These resources just time out on my connection, but if I send the link to anyone else or open over an MTN LTE connection, it opens fine.

Traceroutes to these domains time out after a couple of hops:

Code:

tracert bitmovin-a.akamaihd.net
Tracing route to a280.g2.akamai.net [41.73.43.137]
over a maximum of 30 hops:
  1     1 ms    <1 ms    <1 ms  homerouter.cpe [192.168.8.1]
  2     *        *        *     Request timed out.
  3    41 ms    30 ms    27 ms  41.73.34.193
  4    36 ms    23 ms    23 ms  41.73.34.205
  5     *        *        *     Request timed out.
  6    39 ms    22 ms    22 ms  10.1.29.13
  7    44 ms    22 ms    22 ms  41.73.42.129
  8    20 ms    22 ms    17 ms  41.216.199.4
  9     *       50 ms    34 ms  bnkcrs01-vl677.neology.io [41.216.193.66]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
....and so on

I've changed my host entries manually to access other Akamai servers(which I get by asking colleagues to ping these domains), and then it works for a while.

Something between Rain and Akamai is messed up(probably routing or DNS). We have opened tickets with Afrihost support, but it doesn't seem to be going anywhere.

AfriFella · Mar 20, 2018

Chris8 said:
My brother and I also have Rain/Afrihost LTE-A routers, and experience the same problems.

We mostly have problems with Akamai resources, for example:
https://guzzle.akamaized.net/media/suppliers/Game-1.png
ttps://bitmovin-a.akamaihd.net/bitmovin-player/stable/7.5/bitmovinplayer.js

These resources just time out on my connection, but if I send the link to anyone else or open over an MTN LTE connection, it opens fine.

Traceroutes to these domains time out after a couple of hops:

Code:

tracert bitmovin-a.akamaihd.net Tracing route to a280.g2.akamai.net [41.73.43.137] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms homerouter.cpe [192.168.8.1] 2 * * * Request timed out. 3 41 ms 30 ms 27 ms 41.73.34.193 4 36 ms 23 ms 23 ms 41.73.34.205 5 * * * Request timed out. 6 39 ms 22 ms 22 ms 10.1.29.13 7 44 ms 22 ms 22 ms 41.73.42.129 8 20 ms 22 ms 17 ms 41.216.199.4 9 * 50 ms 34 ms bnkcrs01-vl677.neology.io [41.216.193.66] 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. ....and so on

I've changed my host entries manually to access other Akamai servers(which I get by asking colleagues to ping these domains), and then it works for a while.

Something between Rain and Akamai is messed up(probably routing or DNS). We have opened tickets with Afrihost support, but it doesn't seem to be going anywhere.

Thanks for your detailed feedback. Have you logged this in a support ticket that I can escalate to our network team?

Chris8 · Mar 20, 2018

Yes, I have logged the issue with Afrihost support, I'll send you the ref. number directly.

The issue still remains, and might be more widespread and serious than originally thought.

Please escalate and resolve as a matter of urgency.

Iblis · Mar 21, 2018

Same issue here.

A random one I just picked up today.

No custom DNS configured.

Same thing happens for the Steam website, probably the Akamai issue Chris8 and Racer mentioned above.

Code:

C:\Windows\system32>tracert cracked.com

Tracing route to cracked.com [52.200.110.180]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  homerouter.cpe [192.168.8.1]
  2     *        *        *     Request timed out.
  3    24 ms    26 ms    23 ms  41.73.34.197
  4    22 ms    22 ms    18 ms  41.73.34.209
  5     *        *        *     Request timed out.
  6    26 ms    20 ms    21 ms  10.1.29.13
  7    32 ms    21 ms    21 ms  196.250.232.25
  8   189 ms   185 ms   192 ms  154.66.247.179
  9   189 ms   217 ms   189 ms  154.66.247.146
 10   260 ms   263 ms   263 ms  nyiix-peering.amazon.com [198.32.160.64]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16   286 ms   280 ms   277 ms  54.239.110.223
 17   274 ms   280 ms   278 ms  54.239.110.57
 18   268 ms   270 ms   267 ms  205.251.244.236
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Chris8 · Mar 21, 2018

I'm using Google's DNS servers as a work-around:

Primary 8.8.8.8
Secondary 8.8.4.4

Other Rain clients unaware of this issue are probably very frustrated.

AfriGenie · Mar 22, 2018

Iblis said:

Same issue here.

A random one I just picked up today.

No custom DNS configured.

Same thing happens for the Steam website, probably the Akamai issue Chris8 and Racer mentioned above.

Code:

C:\Windows\system32>tracert cracked.com

Tracing route to cracked.com [52.200.110.180]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  homerouter.cpe [192.168.8.1]
  2     *        *        *     Request timed out.
  3    24 ms    26 ms    23 ms  41.73.34.197
  4    22 ms    22 ms    18 ms  41.73.34.209
  5     *        *        *     Request timed out.
  6    26 ms    20 ms    21 ms  10.1.29.13
  7    32 ms    21 ms    21 ms  196.250.232.25
  8   189 ms   185 ms   192 ms  154.66.247.179
  9   189 ms   217 ms   189 ms  154.66.247.146
 10   260 ms   263 ms   263 ms  nyiix-peering.amazon.com [198.32.160.64]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16   286 ms   280 ms   277 ms  54.239.110.223
 17   274 ms   280 ms   278 ms  54.239.110.57
 18   268 ms   270 ms   267 ms  205.251.244.236
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Thanks for the heads-up! I'll pass it onto our Team!

AfriGenie · Mar 22, 2018

Chris8 said:
I'm using Google's DNS servers as a work-around:

Primary 8.8.8.8
Secondary 8.8.4.4

Other Rain clients unaware of this issue are probably very frustrated.

Ah! Okay, and using the Google DNS hasn't resulted in any performance issues?

Iblis · Mar 22, 2018

Chris8 said:
I'm using Google's DNS servers as a work-around:

Primary 8.8.8.8
Secondary 8.8.4.4

I tried that before I found this thread, and it didn't work for me. (Which I why I thought Racer was right about it not actually being a DNS issue.)

Did you set that DNS in your router? Or in your Network properties?

Here's What I'm getting from Steam (Website only, client works fine):

Code:

C:\Windows\system32>tracert store.steampowered.com

Tracing route to store.steampowered.com [104.92.153.49]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  homerouter.cpe [192.168.8.1]
  2     *        *        *     Request timed out.
  3    28 ms    20 ms    30 ms  41.73.34.193
  4    21 ms    28 ms    18 ms  41.73.34.205
  5     *        *        *     Request timed out.
  6    18 ms    20 ms    19 ms  10.1.29.13
  7    31 ms    19 ms    24 ms  vox.ixp.joburg [196.60.8.146]
  8    18 ms    20 ms    20 ms  a104-92-153-49.deploy.static.akamaitechnologies.com [104.92.153.49]

If I wait long enough, the page that eventually loads looks a lot like Racers screenshot...no style sheets, images etc.

Couldn't get onto Absa a few minutes ago either, but I see other people are reporting probs with their online banking right now, so hopefully that's it, otherwise I'm really going to have problems.

AfriGenie · Mar 22, 2018

Iblis said:
I tried that before I found this thread, and it didn't work for me. (Which I why I thought Racer was right about it not actually being a DNS issue.)

Did you set that DNS in your router? Or in your Network properties?

Here's What I'm getting from Steam (Website only, client works fine):

Code:

C:\Windows\system32>tracert store.steampowered.com Tracing route to store.steampowered.com [104.92.153.49] over a maximum of 30 hops: 1 2 ms 2 ms 2 ms homerouter.cpe [192.168.8.1] 2 * * * Request timed out. 3 28 ms 20 ms 30 ms 41.73.34.193 4 21 ms 28 ms 18 ms 41.73.34.205 5 * * * Request timed out. 6 18 ms 20 ms 19 ms 10.1.29.13 7 31 ms 19 ms 24 ms vox.ixp.joburg [196.60.8.146] 8 18 ms 20 ms 20 ms a104-92-153-49.deploy.static.akamaitechnologies.com [104.92.153.49]

If I wait long enough, the page that eventually loads looks a lot like Racers screenshot...no style sheets, images etc.

Couldn't get onto Absa a few minutes ago either, but I see other people are reporting probs with their online banking right now, so hopefully that's it, otherwise I'm really going to have problems.

Are you configuring the DNS on the WiFi router or on your laptop or computer?

Iblis · Mar 24, 2018

On the router.

Iblis · Mar 24, 2018

Hey, issue seems to be resolved. All sites I couldn't access before now accessible...

AfriFella · Mar 26, 2018

Iblis said:
Hey, issue seems to be resolved. All sites I couldn't access before now accessible...

Brilliant! Thanks for the feedback.

Chris8 · Mar 28, 2018

Just saw your question - I set it on both the Router and OS Network properties. No performance issues.

AfriMan · Apr 3, 2018

As far as I am aware - this issue should be resolved now

Join the MyBroadband community

Get started

Rain DNS Issues

Senior Member

Attachments

Afrihost

Senior Member

Afrihost

Senior Member

Afrihost

New Member

Afrihost

New Member

Member

New Member

Afrihost

Afrihost

Member

Afrihost

Member

Member

Afrihost

New Member

Afrihost Representative