TNZ connection; cannot access TVNZ site

Forums › Spark New Zealand (including Skinny and BigPipe) › TNZ connection; cannot access TVNZ site

rscole86

4999 posts

Uber Geek
+1 received by user: 462

Moderator

Trusted

Lifetime subscriber

#72203 22-Nov-2010 22:05

At home on my TNZ connection I cannot reach www.tvnz.co.nz

Anyone else on Telecom having a similar issue?
I am connecting via the great proxy in the sky, AKmdrL2CacheBC8.telecom.co.nz .

1    <1 ms     1 ms     1 ms homeportal [192.168.1.254]
2    11 ms    11 ms    11 ms 219-89-58-1.dialup.xtra.co.nz [219.89.58.1]
3     *        *        *     Request timed out.
4    20 ms    20 ms    20 ms ae4-20.akcr10.global-gateway.net.nz [202.50.238.49]
5    22 ms    20 ms    27 ms iconz-dom.akcr10.global-gateway.net.nz [122.56.118.74]
6    20 ms    21 ms    22 ms ge-3-3.cat01-sky-core.iconz.net [210.48.5.61]
7    21 ms    19 ms    21 ms GigabitEthernet0-2-102.akkin-rt1.fx.net.nz [131.203.252.97]
8    23 ms    22 ms    22 ms 131.203.251.217
9     *        *        *     Request timed out.

1 | 2 | 3 | 4

597 posts

Ultimate Geek
+1 received by user: 143

Subscriber

#407908 22-Nov-2010 22:22

Same Issue Here. Has been happening since about mid day.

More than likely to be something to do with telecom's caching system i have had problems like this before with it.

It usually resets overnight.

Geoff E

ptinson

677 posts

Ultimate Geek
+1 received by user: 27

Trusted

#407979 23-Nov-2010 08:40

rscole86: At home on my TNZ connection I cannot reach www.tvnz.co.nz

Anyone else on Telecom having a similar issue?
I am connecting via the great proxy in the sky, AKmdrL2CacheBC8.telecom.co.nz .

1    <1 ms     1 ms     1 ms homeportal [192.168.1.254]
2    11 ms    11 ms    11 ms 219-89-58-1.dialup.xtra.co.nz [219.89.58.1]
3     *        *        *     Request timed out.
4    20 ms    20 ms    20 ms ae4-20.akcr10.global-gateway.net.nz [202.50.238.49]
5    22 ms    20 ms    27 ms iconz-dom.akcr10.global-gateway.net.nz [122.56.118.74]
6    20 ms    21 ms    22 ms ge-3-3.cat01-sky-core.iconz.net [210.48.5.61]
7    21 ms    19 ms    21 ms GigabitEthernet0-2-102.akkin-rt1.fx.net.nz [131.203.252.97]
8    23 ms    22 ms    22 ms 131.203.251.217
9     *        *        *     Request timed out.

That is considered a domestic route so it should not pass through the cache farm.
The response however may be an international one, need to confirm it.

Did you glean the proxy name from the VIA header or from a site that tells you what proxy you are using?
The way the farm works would mean that going to an international proxy identification site will result in it reporting the same proxy most of the time. So please dont rely on it to tell you which proxy you are passing through for any other requests.

I will triple check that it is national traffic and post back. If it is then you may have an issue that is not related to the cache.

Regards

Paul

meat popsicle

VinLew

210 posts

Master Geek
+1 received by user: 1

#408099 23-Nov-2010 12:09

Just checked, I can't get onto the TVNZ site either. Perhaps the site is overloaded because of the Coal Mine Disaster?

Tracert:
Tracing route to tvnz.co.nz [202.89.4.222]
over a maximum of 30 hops:

1    80 ms    99 ms    99 ms dsldevice.lan [192.168.1.254]
2    30 ms    29 ms    45 ms 122-59-8-1.jetstream.xtra.co.nz [122.59.8.1]
3     *        *        *     Request timed out.
4    48 ms    48 ms    49 ms ae4-20.akcr10.global-gateway.net.nz [202.50.238.49]
5    49 ms    48 ms    51 ms iconz-dom.akcr10.global-gateway.net.nz [122.56.118.74]
6    49 ms    48 ms    49 ms ge-3-3.cat01-sky-core.iconz.net [210.48.5.61]
7    49 ms    48 ms    49 ms GigabitEthernet0-2-102.akkin-rt1.fx.net.nz [131.203.252.97]
8    51 ms    50 ms    50 ms 131.203.251.217
9     *        *        *     Request timed out.

All further hops time out.

qraider

374 posts

Ultimate Geek
+1 received by user: 10

#408126 23-Nov-2010 13:06

Just checked as well, seems to be working fine (for me)

Anyone still having problems?

Current Phone:
- Android: Samsung SM-G900F Galaxy S5 (XT)
- Win Phone 8: Samsung ATIV S (XT)

Current Tablet:

- Acer Iconia 7" Android Tablet

Twitter: qraider

rscole86

4999 posts

Uber Geek
+1 received by user: 462

Moderator

Trusted

Lifetime subscriber

#408127 23-Nov-2010 13:09

ptinson:Did you glean the proxy name from the VIA header or from a site that tells you what proxy you are using?
The way the farm works would mean that going to an international proxy identification site will result in it reporting the same proxy most of the time. So please dont rely on it to tell you which proxy you are passing through for any other requests.

I will triple check that it is national traffic and post back. If it is then you may have an issue that is not related to the cache.

Regards

Paul

Yes I got it from whatismyip.

I will see if this is still a problem when I get home.

ptinson

677 posts

Ultimate Geek
+1 received by user: 27

Trusted

#408150 23-Nov-2010 13:42

It is something I can replicate and i am providing assistance to TVNZ on this.
I can confirm that the cachefarm does not see any of this traffic though.

Regards

Paul

meat popsicle

Geekzone support

Support Geekzone with one-off or recurring donations Donate via PressPatron.

julianz

118 posts

Master Geek
+1 received by user: 1

#408154 23-Nov-2010 13:51

Yep it's happening for me too. Telecom connection, static IP.

geocom

597 posts

Ultimate Geek
+1 received by user: 143

Subscriber

#408168 23-Nov-2010 14:03

Hi Paul

Without fully knowing what TVNZ did to there site yesterday i can only speculate.

In the past on any telecom connection when i change the DNS Settings on any of my sites telecom fails to see any changes to the DNS and routes to the old DNS settings however things usually resolve over night which it has done so for me. If TVNZ changed there DNS settings then this would echo what i have seen in the past.

Edit
Also when this has happened before if the site has been visited by someone on the (e.g. Avondale Exchange) has viewed the site and then the DNS changes then the site will not resolve for anyone in that exchange but some one on the (e.g. Auckland CBD Exchange) has not viewed the site before the site will resolve.

If that makes any sense

Geoff E

ptinson

677 posts

Ultimate Geek
+1 received by user: 27

Trusted

#408222 23-Nov-2010 14:25

geocom: Hi Paul

Without fully knowing what TVNZ did to there site yesterday i can only speculate.

In the past on any telecom connection when i change the DNS Settings on any of my sites telecom fails to see any changes to the DNS and routes to the old DNS settings however things usually resolve over night which it has done so for me. If TVNZ changed there DNS settings then this would echo what i have seen in the past.

Edit
Also when this has happened before if the site has been visited by someone on the (e.g. Avondale Exchange) has viewed the site and then the DNS changes then the site will not resolve for anyone in that exchange but some one on the (e.g. Auckland CBD Exchange) has not viewed the site before the site will resolve.

If that makes any sense

Interesting comments.
I can state explicitly that our DNS caching resolvers follow the TTL set for the record.
If you find an example of it not doing that I would really like to know as its a fault.

If you mean changes to the Telecom hosted names then, overnight is about right.

The link to exchanges doesn't make a whole lot of sense to me, our DNS servers are not tied in anyway to an exchange boundary...
Do you mean that DNS fails for that site for a period or just that you cant browse to that site?

All slightly OT i guess but interesting to me none the less.

Paul

meat popsicle

geocom

597 posts

Ultimate Geek
+1 received by user: 143

Subscriber

#408244 23-Nov-2010 14:32

Hi Paul

The example i gave was a real one which is what makes it more confessing in this case the Avondale Exchange is me and the Auckland CBD one was a telecom support person.

The only time i have ever had issues is with changing the DNS settings on my sites the DNS is every DNS which is in the states. Just last week i had to port one of my .com domains over and like i have said it would not work un till the morning however it worked just fine on my mobile as i had not viewed the .com domain on that connection at all during the day

Anyway your right this is getting a bit off topic from TVNZ wont work

Geoff E

ptinson

677 posts

Ultimate Geek
+1 received by user: 27

Trusted

#408249 23-Nov-2010 14:36

Feel free to send me details of example you have and i can look into it.
Or start a new thread an i can reply in there, saving clutering this one:)

Paul

meat popsicle

Samsung

Shop now on Samsung phones, tablets, TVs and more (affiliate link).

julianz

118 posts

Master Geek
+1 received by user: 1

#408251 23-Nov-2010 14:38

Interesting... if I do a traceroute to anywhere that isn't TVNZ, it starts off like this, by heading through a nest of "global-gateway.net.nz" addresses:

>tracert www.geekzone.co.nz

Tracing route to www.geekzone.co.nz [202.175.128.164]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms 192.168.1.1
2    12 ms     9 ms     8 ms 219-89-50-1.dialup.xtra.co.nz [219.89.50.1]
3     *        *        *     Request timed out.
4     6 ms    14 ms     8 ms ae4-20.akcr10.global-gateway.net.nz [202.50.238.49]
5     7 ms     7 ms     7 ms g0-1-0-4.akcr8.global-gateway.net.nz [210.55.202.49]
6     8 ms     8 ms     7 ms ae2-10.tkcr4.global-gateway.net.nz [210.55.202.36]
7     8 ms     8 ms     7 ms orcon-dom.tkcr4.global-gateway.net.nz [203.96.66.102]

but if I traceroute tvnz.co.nz it goes through mobile.telecom.co.nz instead, and nothing else does that. Bad route?

>tracert www.tvnz.co.nz

Tracing route to tvnz.co.nz [202.89.4.222]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms 192.168.1.1
2     9 ms     8 ms     8 ms 219-89-50-1.dialup.xtra.co.nz [219.89.50.1]
3     *        *        *     Request timed out.
4    11 ms     9 ms     7 ms 122-56-222-3.mobile.telecom.co.nz [122.56.222.3]
5     *        *        *     Request timed out.
(...it's all timeouts past here)

crazed

484 posts

Ultimate Geek
+1 received by user: 26

Trusted

#408386 23-Nov-2010 16:53

Hey guys, yea same problem here cant access TVNZ at all from our Home connection(Telecom Pro DSL)

I'm using Telecoms DNS servers at present.

C:\Users\Charles>tracert www.tvnz.co.nz

Tracing route to tvnz.co.nz [202.89.4.222]
over a maximum of 30 hops:

  1 1 ms 1 ms 1 ms 10.0.0.1
  2 63 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
  3 11 ms 10 ms 12 ms 115-188-240-1.jetstream.xtra.co.nz [115.188.240.
1]
  4 * * * Request timed out.
  5 139 ms 369 ms 380 ms 122.56.224.13
  6 104 ms 487 ms 410 ms GigabitEthernet0-0-413.wnmur-rt1.fx.net.nz [202.
53.187.65]
  7 28 ms 31 ms 28 ms 131.203.251.217
  8 * * * Request timed out.
  9 * * * Request timed out.
10 * * * Request timed out.
Timeouts from here onwards

CraZeD,
Your friendly Southern Geeky Fellow :P

skewt

752 posts

Ultimate Geek
+1 received by user: 215

#408547 23-Nov-2010 21:20

Still can't access it here using pro broadband and also xt data

rscole86

4999 posts

Uber Geek
+1 received by user: 462

Moderator

Trusted

Lifetime subscriber

#408549 23-Nov-2010 21:21

Ditto, still ongoing.

1 | 2 | 3 | 4