[TelstraClear] Odd DNS to Google.co.nz and slow...

Forums › One NZ (including Farmside) › [TelstraClear] Odd DNS to Google.co.nz and slow...

DonGould

3892 posts

Uber Geek
+1 received by user: 164

#90946 4-Oct-2011 09:08

Following on from http://www.geekzone.co.nz/forums.asp?forumid=44&topicid=90929&page_no=1#528820

Trace to www.google.co.nz gives me 20+ hops and to a different ip range as my wellington connection.

1. router                                                                                                                                                        0.0%    12    0.2   0.2   0.2   0.4   0.0
2. ???
3. 218.101.61.101                                                                                                                                                0.0%    12   38.4 13.9   8.0 38.4   9.8
4. ???
5. ie1-g-0-0-0.telstraclear.net                                                                                                                                  0.0%    12   22.4 27.3 22.0 58.9 10.5
6. ge-0-2-0-1.xcore1.acld.telstraclear.net                                                                                                                       0.0%    12   24.5 27.6 21.9 51.4   8.7
7. 203.167.233.10                                                                                                                                                0.0%    12   22.8 23.7 21.7 27.7   1.7
8. i-0-0-4-1.tlot-core01.bx.reach.com                                                                                                                            0.0%    12 163.1 149.6 146.8 163.1   4.4
9. i-5-1.nwk-core01.bi.reach.com                                                                                                                                 0.0%    12 218.5 218.2 216.2 221.4   1.6
10. i-6-0.ulco-core01.bx.reach.com                                                                                                                                0.0%    12 288.8 288.5 286.9 290.5   1.2
11. 195.66.226.125                                                                                                                                                0.0%    12 301.4 305.6 301.3 317.3   5.9
12. 209.85.255.175                                                                                                                                                0.0%    12 302.0 308.4 302.0 345.0 12.4
13. 209.85.250.54                                                                                                                                                 0.0%    12 299.0 304.7 299.0 324.6   8.9
14. 209.85.254.48                                                                                                                                                 0.0%    12 289.1 295.9 287.6 312.0   9.2
15. 64.233.174.144                                                                                                                                                0.0%    12 289.0 292.7 288.7 305.2   5.0
16. 64.233.174.177                                                                                                                                                0.0%    12 349.2 355.6 346.6 370.7   9.2
17. 209.85.255.35                                                                                                                                                 0.0%    11 346.2 349.3 345.5 363.7   5.1
18. 64.233.175.0                                                                                                                                                  0.0%    11 350.5 355.1 350.0 369.0   6.8
19. 66.249.95.167                                                                                                                                                 0.0%    11 457.1 449.0 445.9 457.1   3.8
20. 72.14.237.47                                                                                                                                                  0.0%    11 447.5 447.4 446.2 450.4   1.1
21. 74.125.237.16                                                                                                                                                 0.0%    11 445.8 447.7 445.7 458.5   3.7

# host www.google.co.nz
www.google.co.nz is an alias for www.google.com.
www.google.com is an alias for www.l.google.com.
www.l.google.com has address 74.125.237.50
www.l.google.com has address 74.125.237.51
www.l.google.com has address 74.125.237.52
www.l.google.com has address 74.125.237.48
www.l.google.com has address 74.125.237.49

Where as TelstraClear NS...

# host www.google.co.nz 203.97.78.43
Using domain server:
Name: 203.97.78.43
Address: 203.97.78.43#53
Aliases:

www.google.co.nz is an alias for www.google.com.
www.google.com is an alias for www.l.google.com.
www.l.google.com has address 74.125.237.17
www.l.google.com has address 74.125.237.18
www.l.google.com has address 74.125.237.19
www.l.google.com has address 74.125.237.20
www.l.google.com has address 74.125.237.16

Wellington I get a much shorter and faster trace...

1. 202.68.81.105                                                                                                    0.0%     5    0.2   0.2   0.2   0.2   0.0
2. ge0-3.cr2.wlg.dts.net.nz                                                                                         0.0%     5    4.6   4.9   4.6   5.2   0.3
3. 124.157.96.210                                                                                                   0.0%     5   14.0 18.3 13.3 36.4 10.1
4. 172.18.8.185                                                                                                     0.0%     5   13.7 14.2 13.7 14.5   0.3
5. kordia.cre2.nct.odyssey.net.nz                                                                                   0.0%     5   14.7 15.5 14.2 19.6   2.3
6. 72.14.214.5                                                                                                      0.0%     5   37.6 38.0 37.6 38.4   0.3
7. 72.14.214.6                                                                                                      0.0%     5 149.2 78.1 37.7 149.2 55.2
8. 66.249.95.232                                                                                                    0.0%     5   38.8 38.8 38.5 38.9   0.2
9. 72.14.237.51                                                                                                     0.0%     4   39.1 38.9 38.7 39.2   0.2
10. 74.125.237.48                                                                                                    0.0%     4   38.5 38.7 38.5 39.2   0.3

Less than 1/10th of the time.

What am I missing?

Promote New Zealand - Get yourself a .kiwi.nz domain name!!!

Check out mine - i.am.a.can.do.kiwi.nz - don@i.am.a.can.do.kiwi.nz

1 | 2 | 3 | 4 | 5

738 posts

Ultimate Geek
+1 received by user: 190

#528846 4-Oct-2011 09:27

Seems to be a routing issue with TelstraClear. 195.66.226.125 is an IP on the London Peering Exchange, effectively means its being routed via Europe, so that would explain the high ping times and slowness.

I've just tested from a Telstra DSL connection and I see the same thing.

Nothing to do with DNS as I get the same IP resolving on a non-TelstraClear connection and it routes to Australia as expected.

DonGould

3892 posts

Uber Geek
+1 received by user: 164

#528859 4-Oct-2011 09:44

Kraven: Seems to be a routing issue with TelstraClear. 195.66.226.125 is an IP on the London Peering Exchange, effectively means its being routed via Europe, so that would explain the high ping times and slowness.

I've just tested from a Telstra DSL connection and I see the same thing.

Nothing to do with DNS as I get the same IP resolving on a non-TelstraClear connection and it routes to Australia as expected.

Good spot! :)

After I read this post by FM - http://www.geekzone.co.nz/forums.asp?forumid=44&topicid=90929&page_no=1#528699 - I started to wonder if the dns servers are just pointing people off in the wrong direction for all sorts of stuff (hence why they're reporting it as slow connections).

People who have been reporting that they're only getting 2mbit (blar blar), I'm wondering how they're testing it? If it's a single thread, then we already know that if it's coming from a long way away then the issues that TelstraClear Cable connections appear to be rate shaped in one way or another by jnawk has been looking at seem to impact that.

cyril7 suggests Reply - it might be TW capacity from the area. But have we seen a multi threaded download to prove this out?

I'm as confused as the next person but I'm just trying to connect some of the dots that people have been posting to understand the issues a bit better.

Promote New Zealand - Get yourself a .kiwi.nz domain name!!!

Check out mine - i.am.a.can.do.kiwi.nz - don@i.am.a.can.do.kiwi.nz

cyril7

9073 posts

Uber Geek
+1 received by user: 2499

ID Verified

Trusted

Subscriber

#528879 4-Oct-2011 10:21

cyril7 suggests Reply - it might be TW capacity from the area. But have we seen a multi threaded download to prove this out?

Good point Don, if their DNS is screwed and sending even local routes to the other side of the planet then your......... screwed.

Cyril

DonGould

3892 posts

Uber Geek
+1 received by user: 164

#528881 4-Oct-2011 10:24

cyril7:
cyril7 suggests Reply - it might be TW capacity from the area. But have we seen a multi threaded download to prove this out?

Good point Don, if their DNS is screwed and sending even local routes to the other side of the planet then your......... screwed.

Cyril

Ya thanks... but I was wrong... well I'm right (I think) that if the DNS is sending traffic off shore then yes... but in this case it's not the dns at all, it's just routing.

I grabbed the IP's that I was resolving in Wellington and hit them from here in Chch and got exactly the same result (off to London).

Promote New Zealand - Get yourself a .kiwi.nz domain name!!!

Check out mine - i.am.a.can.do.kiwi.nz - don@i.am.a.can.do.kiwi.nz

cyril7

9073 posts

Uber Geek
+1 received by user: 2499

ID Verified

Trusted

Subscriber

#528883 4-Oct-2011 10:27

Ahhh, yes should edit my post to read DNS or routes are screwed.

Cyril

captk

19 posts

Geek

#528930 4-Oct-2011 11:22

I'm having the same issue here, I opened a ticket with Telstra last week and they are looking into it. They sent somebody around to test/replicate the issue which they could.

They said that they would raise it with Reach so I guess we wait and see.

I have a direct line with the faults person there so if you guys want me to pass on any information/ideas to help the fix it (or take ownership of the problem) then just let me know.

Cheers
j

Geekzone

Want to support Geekzone and browse the site without the ads? Subscribe to Geekzone now (monthly, annual and lifetime options).

captk

19 posts

Geek

#528975 4-Oct-2011 12:19

I think this may have been resolved now, can anyone confirm?

My trace now is:

Tracing route to google.co.nz [203.97.30.152]
over a maximum of 30 hops:

1 10 ms 1 ms 1 ms [192.168.10.1]
2 2 ms 2 ms 2 ms 192.168.0.1
3 13 ms 14 ms 12 ms lo0.internet.ivpn.pe14.telstraclear.net [218.101.61.97]
4 21 ms 31 ms 21 ms 203.97.30.131
5 21 ms 21 ms 21 ms 203.97.30.152

Trace complete.

DonGould

3892 posts

Uber Geek
+1 received by user: 164

#528983 4-Oct-2011 12:30

captk: I think this may have been resolved now, can anyone confirm?

# host www.google.co.nz
www.google.co.nz is an alias for www.google.com.
www.google.com is an alias for www.l.google.com.
www.l.google.com has address 203.97.30.146
www.l.google.com has address 203.97.30.149
www.l.google.com has address 203.97.30.152
www.l.google.com has address 203.97.30.155

# host www.google.co.nz 203.97.78.43
Using domain server:
Name: 203.97.78.43
Address: 203.97.78.43#53
Aliases:

www.google.co.nz is an alias for www.google.com.
www.google.com is an alias for www.l.google.com.
www.l.google.com has address 203.97.30.149
www.l.google.com has address 203.97.30.152
www.l.google.com has address 203.97.30.155
www.l.google.com has address 203.97.30.146

# host www.google.co.nz 203.97.78.44
Using domain server:
Name: 203.97.78.44
Address: 203.97.78.44#53
Aliases:

www.google.co.nz is an alias for www.google.com.
www.google.com is an alias for www.l.google.com.
www.l.google.com has address 203.97.30.155
www.l.google.com has address 203.97.30.146
www.l.google.com has address 203.97.30.149
www.l.google.com has address 203.97.30.152

Ya, the results are different on both name servers from what they were earlier this morning.

# ping www.google.co.nz
PING www.l.google.com (203.97.30.155) 56(84) bytes of data.
64 bytes from 203.97.30.155: icmp_req=1 ttl=60 time=25.9 ms
64 bytes from 203.97.30.155: icmp_req=2 ttl=60 time=20.8 ms
64 bytes from 203.97.30.155: icmp_req=3 ttl=60 time=21.6 ms

# mtr www.google.co.nz
1. router                                                                     0.0%     5    0.2   0.2   0.2   0.3   0.0
2. ???
3. 218.101.61.101                                                             0.0%     5    9.9 13.3   9.8 24.1   6.1
4. 203.97.30.131                                                              0.0%     5   35.0 30.9 22.5 36.7   6.3
5. 203.97.30.149                                                              0.0%     5   22.5 24.0 21.9 27.5   2.3

So yes, does seem to be resolved for now.

Wonder what broke and why and want else is/was impacted?

http://www.telstraclear.co.nz/customer-zone/service-information/resolved-outages.cfm

Shows nothing.

If all this traffic was hitting links to the UK, then what impact was it having on the links and is that the cause of all the other issues people have been reporting?

Promote New Zealand - Get yourself a .kiwi.nz domain name!!!

Check out mine - i.am.a.can.do.kiwi.nz - don@i.am.a.can.do.kiwi.nz

captk

19 posts

Geek

#528988 4-Oct-2011 12:41

Still not good on ads and analytics etc, so still getting major slow downs on all sites which use them (which is a fair few).

Tracing route to partnerad.l.google.com [74.125.237.60]
over a maximum of 30 hops:

1 10 ms 1 ms 1 ms [192.168.10.1]
2 2 ms 1 ms 1 ms 192.168.0.1
3 12 ms 12 ms 12 ms lo0.internet.ivpn.pe14.telstraclear.net [218.101.61.97]
4 * * * Request timed out.
5 22 ms 20 ms 21 ms ie1-g-0-0-0.telstraclear.net [203.98.50.1]
6 21 ms 21 ms 21 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251]
7 21 ms 21 ms 21 ms 203.167.233.10
8 151 ms 151 ms 146 ms i-0-0-4-1.tlot-core01.bx.reach.com [202.84.142.106]
9 221 ms 225 ms 239 ms i-1-3.nwk-core01.bi.reach.com [202.84.141.153]
10 286 ms 295 ms 288 ms i-6-1.ulco-core01.bx.reach.com [202.84.249.94]
11 299 ms 320 ms 300 ms 195.66.226.125
12 300 ms 300 ms 300 ms 209.85.252.76
13 300 ms 299 ms 300 ms 216.239.46.224
14 290 ms 289 ms 289 ms 72.14.238.105
15 295 ms 295 ms 295 ms 64.233.174.146
16 347 ms 348 ms 361 ms 64.233.174.179
17 348 ms 347 ms 366 ms 209.85.255.57
18 352 ms 364 ms 352 ms 64.233.175.0
19 448 ms 448 ms 456 ms 66.249.95.167
20 447 ms 449 ms 450 ms 72.14.237.51
21 447 ms 448 ms 448 ms 74.125.237.60

Trace complete.

captk

19 posts

Geek

#528992 4-Oct-2011 12:47

This is odd as now it's back to the original route for me on both my connections.

Tracing route to google.co.nz [74.125.237.18]
over a maximum of 30 hops:

1 18 ms 1 ms 1 ms [192.168.10.1]
2 2 ms 2 ms 2 ms 192.168.0.1
3 14 ms 15 ms 13 ms lo0.internet.ivpn.pe14.telstraclear.net [218.101.61.97]
4 * * * Request timed out.
5 52 ms 25 ms 21 ms ie1-g-0-0-0.telstraclear.net [203.98.50.1]
6 26 ms 21 ms 21 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251]
7 25 ms 21 ms 21 ms 203.167.233.10
8 153 ms 153 ms 153 ms i-0-0-4-0.tlot-core01.bx.reach.com [202.84.142.118]
9 230 ms 228 ms 227 ms i-1-3.nwk-core01.bi.reach.com [202.84.141.153]
10 299 ms 298 ms 298 ms i-6-0.ulco-core01.bx.reach.com [202.84.144.142]
11 305 ms 305 ms 305 ms 195.66.226.125

12 306 ms 395 ms 306 ms 209.85.252.76
13 305 ms 308 ms 313 ms 216.239.46.224
14 296 ms 311 ms 296 ms 72.14.238.105
15 301 ms 313 ms 301 ms 64.233.174.146
16 353 ms 355 ms 367 ms 64.233.174.179
17 354 ms 354 ms 354 ms 209.85.255.57
18 379 ms 358 ms 357 ms 64.233.175.0
19 454 ms 453 ms 457 ms 66.249.95.167
20 454 ms 454 ms 454 ms 72.14.237.47
21 454 ms 456 ms 460 ms 74.125.237.18

Trace complete.

Beccara

1473 posts

Uber Geek
+1 received by user: 517

ID Verified

#528994 4-Oct-2011 12:50

Looks like a routing fault, This is what a good path to partnerad.l.google.com looks like

Tracing route to partnerad.l.google.com [74.125.237.28]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms 10.10.10.1
2 <1 ms <1 ms <1 ms 180.222.67.1
3 3 ms 3 ms 3 ms 124.157.96.186
4 4 ms 4 ms 35 ms 121.99.12.20
5 29 ms 27 ms 27 ms 72.14.214.5
6 28 ms 27 ms 27 ms 72.14.214.6
7 36 ms 29 ms 29 ms 66.249.95.232
8 28 ms 29 ms 29 ms 72.14.237.47
9 28 ms 28 ms 28 ms 74.125.237.28

Trace complete.

Most problems are the result of previous solutions...

All comment's I make are my own personal opinion and do not in any way, shape or form reflect the views of current or former employers unless specifically stated

Mighty Ape

Shop now at Mighty Ape (affiliate link).

floydbloke

3646 posts

Uber Geek
+1 received by user: 4554

ID Verified

#528997 4-Oct-2011 12:54

captk: Still not good on ads and analytics etc, so still getting major slow downs on all sites which use them (which is a fair few).

How long is a major slow down by your definition? I'm suffering wait times of up to a minute or more where the browser status says "waiting for accounts.google.com" or similar. It's definitely worse at peak times.
Wifey is a moderately heavy user of GMail and she is becoming less and less patient.

I haven't logged a trouble ticket yet but will be doing so tonight. I think I'll include a reference to these threads.

Edit: I'm quickly getting out of my technical depth with traceroutes and the likes. Is that time-out on the 4th hop something to be concerned about?

Sometimes I use big words I don't always fully understand in an effort to make myself sound more photosynthesis.

captk

19 posts

Geek

#529008 4-Oct-2011 13:04

floydbloke:
captk: Still not good on ads and analytics etc, so still getting major slow downs on all sites which use them (which is a fair few).

How long is a major slow down by your definition? I'm suffering wait times of up to a minute or more where the browser status says "waiting for accounts.google.com" or similar. It's definitely worse at peak times.
Wifey is a moderately heavy user of GMail and she is becoming less and less patient.

I haven't logged a trouble ticket yet but will be doing so tonight. I think I'll include a reference to these threads.

Hi floydbloke, yes that is exactly what I am experiencing. So I would log a ticket with them so they know other people are been affected.

Cheers
j

DonGould

3892 posts

Uber Geek
+1 received by user: 164

#529013 4-Oct-2011 13:11

captk: This is odd as now it's back to the original route for me on both my connections.

20 454 ms 454 ms 454 ms 72.14.237.47
21 454 ms 456 ms 460 ms 74.125.237.18

Trace complete.

Ya there seem to be two issues at play here.

1. TCL are playing with the dns entries
2. TCL have a routing issue for 74.125

Bottom line really, if you're on DSL then just go look for a different provider if it's really annoying you I guess.

I'm sure someone at TCL are aware that we're posting here on the issue but haven't even bothered to post a heads up about what's being done and in what time frames.

Promote New Zealand - Get yourself a .kiwi.nz domain name!!!

Check out mine - i.am.a.can.do.kiwi.nz - don@i.am.a.can.do.kiwi.nz

cyril7

9073 posts

Uber Geek
+1 received by user: 2499

ID Verified

Trusted

Subscriber

#529015 4-Oct-2011 13:13

I see no one has posted in the GZ ISP fault log

Cyril

1 | 2 | 3 | 4 | 5