[root@host11 ~]# traceroute pop3.xtra.co.nz
traceroute to pop1.tnz.mail.vip.aue.yahoo.com (124.108.96.66), 30 hops
max, 38 byte packets
1 fe-1-1-0-213-jcore3.wxnz.net (58.28.96.17) 0.401 ms 0.401 ms
0.355 ms
2 ge-0-0-0-akl-core1.wxnz.net (58.28.8.8) 0.608 ms 0.445 ms 0.484 ms
3 Gi9-1.gw1.AKL1.asianetcom.net (203.192.166.105) 0.489 ms 0.580 ms
0.479 ms
4 ip-202.147.55.210.asianetcom.net (202.147.55.210) 0.735 ms 59.904
ms 1.479 ms
5 po4-0.cr2.syd1.asianetcom.net (202.147.55.254) 23.844 ms 23.702 ms
24.089 ms
6 po12-2.gw2.syd1.asianetcom.net (202.147.40.126) 23.972 ms 24.343
ms 23.844 ms
7 202.167.228.35 (202.167.228.35) 24.467 ms 24.647 ms 25.588 ms
8 gi1-1.bas2.aue.yahoo.com (203.84.216.206) 24.968 ms
gi1-2.bas1.aue.yahoo.com (203.84.216.210) 24.133 ms
gi1-1.bas2.aue.yahoo.com (203.84.216.206) 24.567 ms
9 *
Which neatly circumvents all our privacy and surveillance laws.
Well, not for certain, but probably. They are storing your email at that
address, but the mail servers aren't necessarily there. Yahoo are
certainly managing all mail for them, but...
$ dig mx xtra.co.nz
; <<>> DiG 9.3.4 <<>> mx xtra.co.nz
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54943
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 0
;; QUESTION SECTION:
;xtra.co.nz. IN MX
;; ANSWER SECTION:
xtra.co.nz. 300 IN MX 10 mx1.tnz.mail.yahoo.com.
xtra.co.nz. 300 IN MX 20 mx2.tnz.mail.yahoo.com.
;; AUTHORITY SECTION:
xtra.co.nz. 86400 IN NS terminator.xtra.co.nz.
xtra.co.nz. 86400 IN NS alien.xtra.co.nz.
;; Query time: 373 msec
;; SERVER: 10.0.0.201#53(10.0.0.201)
;; WHEN: Sat Aug 18 15:13:39 2007
;; MSG SIZE rcvd: 131
So there are 2 mail servers in use by xtra. mx1 and mx2. Both point to the
same IP address, 124.108.96.67. This reports to be running ysmtp software,
which is as far as I know, yahoo's own.
However, attempts at geolocation of the servers actually fails - although
one of the services says it's in Hong Kong, and a somewhat smarter one
(ipaddresslocation.org ) supports your theory, and puts it somewhere on
Oz, but hidden.
Steve
> So there are 2 mail servers in use by xtra. mx1 and mx2. Both point to the
> same IP address, 124.108.96.67.
>
> However, attempts at geolocation of the servers actually fails - although
> one of the services says it's in Hong Kong, and a somewhat smarter one
> (ipaddresslocation.org ) supports your theory, and puts it somewhere on
> Oz, but hidden.
Interesting. According to the latest version of
<ftp://ftp.apnic.net/public/stats/apnic/delegated-apnic-latest>, that IP
address is in a range assigned to region code "AP". But there's no such
country or TLD.
I would think Asia-Pacific is a logical region code, even if domain names
aren't assigned along similar lines to the EU.
Look at the trace, I would be extremely surprised if that was not in
Australia -
[root@galaxian ~]# tcptraceroute 124.108.96.66 110
traceroute to 124.108.96.66 (124.108.96.66), 30 hops max, 110 byte packets
1 fe-1-1-0-213-jcore3.wxnz.net (58.28.96.17) 0.703 ms 10.361 ms
10.392 ms
2 ge-0-0-0-akl-core1.wxnz.net (58.28.8.8) 0.512 ms 0.630 ms 0.539 ms
3 Gi9-1.gw1.akl1.asianetcom.net (203.192.166.105) 0.527 ms 0.373 ms
0.493 ms
4 ip-202.147.55.210.asianetcom.net (202.147.55.210) 0.644 ms 0.710
ms 0.758 ms
5 po4-0.cr2.syd1.asianetcom.net (202.147.55.254) 23.532 ms 23.707
ms 23.675 ms
6 po12-1.gw2.syd1.asianetcom.net (202.147.40.122) 24.133 ms 23.718
ms 23.708 ms
7 202.167.228.35 (202.167.228.35) 24.714 ms 25.041 ms 25.151 ms
8 gi1-2.bas1.aue.yahoo.com (203.84.216.210) 24.781 ms
gi1-1.bas2.aue.yahoo.com (203.84.216.206) 24.638 ms
gi1-2.bas1.aue.yahoo.com (203.84.216.210) 24.835 ms
9 pop1.tnz.mail.vip.aue.yahoo.com (124.108.96.66) 168.982 ms
168.917 ms 165.367 ms
[root@galaxian ~]#
Outsourcing a core competency of a company is rarely a good move for the
companies customers. If Xtra can't do email, well I guess they are good
at making ads.. nope outsourced.. how about helpdesk.. nope
outsourced... well network.. no outsourced (to Telecom)... hmm
oops... that's outsourced to Alcatel..
Point.
Mock.
Yahoo is not Telecom.
NZ law only applies in NZ.
Point.
Mock.
Which is where Telecom NZ is based.
Works ok for Coke. All they own is a recipe.
> On Sat, 18 Aug 2007 17:16:12 +1200, Tony wrote:
>
>> oops... that's outsourced to Alcatel..
>
> Isn't that entirely owned by Telecom?
>
>
I thought Lucent had a fair share.
> Look at the trace, I would be extremely surprised if that was not in
> Australia -
gi1-1.bas2.aue.yahoo.com (203.84.216.206) 24.638 ms
> gi1-2.bas1.aue.yahoo.com (203.84.216.210) 24.835 ms
> 9 pop1.tnz.mail.vip.aue.yahoo.com (124.108.96.66) 168.982 ms
> 168.917 ms 165.367 ms
> [root@galaxian ~]#
I wou;dn't bet on it. Are you basing this on the hostnames? Look at the
delay times.
...and don't log in as root (:
Go on try and copy the shape of their bottle to yours as competition. Or the
name etc..
Yahoo is in bed with Telecom.
Didn't a lot of 1970s cars do pretty much that? :)
I'd say that 'AP' stands for 'APNIC' and is used if for some reason or
other the address range can't be allocated to a specific country.
Cheers,
Cliff
Cheers,
Cliff
--
Have you ever noticed that if something is advertised as 'amusing' or
'hilarious', it usually isn't?
> Jonathan Walker wrote:
>> On Sat, 18 Aug 2007 16:41:26 +1200, Mickey Mouse wrote:
>>
>>> I would think Asia-Pacific is a logical region code, even if domain
>>> names aren't assigned along similar lines to the EU.
>>
>> Given that internet usage in Asia is growing quickly I think that it is
>> now time for IP addresses to be assigned to countries rather than to the
>> nebulous "asia pacific" region.
>>
> That would be difficult because you can have valid addresses in one
> country that are apparently allocated to another. This happens when a
> large global network provider (with IPs allocated in one country) has
> points of presence in another country.
But that hasn't stopped most existing IP addresses being assigned by
country. And such global networks can cross NIC allocation regions too, so
what.
> [root@host11 ~]# host pop3.xtra.co.nz
> pop3.xtra.co.nz is an alias for pop3.tnz.yahoo.com.
> pop3.tnz.yahoo.com is an alias for pop1.tnz.mail.vip.aue.yahoo.com.
> pop1.tnz.mail.vip.aue.yahoo.com has address 124.108.96.66
>
>
>
> [root@host11 ~]# traceroute pop3.xtra.co.nz
> traceroute to pop1.tnz.mail.vip.aue.yahoo.com (124.108.96.66), 30 hops
> max, 38 byte packets
Xtra sent out an email last night or today to do with the move.
Unfortunately the dumb &^#%s back-dated the email to 16 July,
so it is way down in the inbox and could be missed.
| From: Yahoo! <mailbot at yahoo.com>
|
| Hi there,
|
| With Yahoo!Xtra Bubble you will have access to an exciting
| range of services that will change the way you use the Internet
| with Telecom, all for no additional cost.
|
| Your Xtra email address is still the same and will give you
| access to all the great services on offer.
|
| Your mailbox has been upgraded to Yahoo!Xtra Pro Mail and has
| loads of useful features:
| • Loads of storage allows you to save all your emails
| • SpamGuard Plus helps keep unwanted messages out of your inbox
| • With 10 additional sub accounts everyone in your household and
| business can have their own email address and mailbox
Bullet point 2 looks like it still needs some work.
See thread "Is Xtra's spam filter broken?" starting
with news:2nvcc3tp0rc1ahskp...@4ax.com
--
Cheers,
Ralph
The 24ms is Australia, the only question is the last hop which is a US
relay time, but I suspect this is only beacuse the last hop router does
not have a direct to nz path so is sending the traffic by the US. The
one below via GG is definitive, look at the times, that is 100% Australia.
[tonyw@host1 tonyw]$ traceroute 124.108.96.66
traceroute to 124.108.96.66 (124.108.96.66), 30 hops max, 38 byte packets
1 ns25 (210.55.20.241) 0.457 ms 0.407 ms 0.400 ms
2 202.37.244.57 (202.37.244.57) 7.125 ms 7.249 ms 7.213 ms
3 ge-0-3-0-6.akbr3.global-gateway.net.nz (202.37.246.18) 6.790 ms
6.725 ms 6.767 ms
4 so1-2-0.tkbr9.global-gateway.net.nz (203.96.120.74) 7.444 ms 7.332
ms 7.381 ms
5 so1-1-1.sybr4.global-gateway.net.nz (210.55.202.197) 30.676 ms
30.647 ms so-1-2-2.sybr4.global-gateway.net.nz (202.50.232.218) 31.258 ms
6 yahoo.sybr4.global-gateway.net.nz (202.50.236.30) 31.121 ms 31.466
ms 31.494 ms
7 gi1-2.bas2.aue.yahoo.com (203.84.216.202) 30.881 ms 31.218 ms
gi1-1.bas1.aue.yahoo.com (203.84.216.198) 31.087 ms
8 *
um, no http://www.alcatel-lucent.com/ is probably 100 times the size of
Telecom. Telecom is but a small customer.
Checking country of origin by IP address is just not accurate. IPV6 is
going to make it worse too.
> On Sat, 18 Aug 2007 18:34:59 +1200, Mark Robinson wrote:
>
>
>>>The fact that Telecom has outsourced it's SMTP server does not remove
>>>from it the obligation to honour it's legal and contractural
>>>obligations.
>>
>>Yahoo is not Telecom.
>>
>>NZ law only applies in NZ.
>
>
> Correct.
>
> And your agreement here in NZ is between yourself and Telecom NZ.
>
> Telecom is beholden to the law of this land.
>
>
LOL Not when the NSA and Yahoo do a back passage deal and get ASIO
to oversee transferred web mail. Remember John Howard was the visiting
proctologist for the recent back passage foray looking for Dubya's head.
--
Posted via a free Usenet account from http://www.teranews.com
A National Security Letter dropped on Yahoo trumps any agreement you may have
with Telecom and any New Zealand law.
Dude, if you get 200ms to Australia your ISP really sucks ! That means
your traffic is going via the US which is 150 or so ms longer than it
should do via a direct Auckland-Sydney path. Note below the first 2 go
direct to Australia, and the third goes to the US.
snz_icore1_na#traceroute telstra.com.au
Translating "telstra.com.au"...domain server (202.170.160.1) [OK]
Type escape sequence to abort.
Tracing the route to telstra.com.au (144.135.18.41)
1 lnk1-telstraclear.safenz.net (203.97.21.97) [AS 4768] 64 msec 28
msec 16 msec
2 ge-1-0-0-927.ie1.telstraclear.net (218.101.61.8) 12 msec 16 msec 16
msec
3 ge-0-2-0-1.xcore1.acld.telstraclear.net (203.98.50.251) [AS 4768]
16 msec 16 msec 16 msec
4 203.167.128.1 [AS 4768] 16 msec 16 msec 16 msec
5 i-7-3.syd-core01.net.reach.com (202.84.142.141) 40 msec 40 msec 40 msec
6 i-3-0.syd-core03.net.reach.com (202.84.249.14) 40 msec 40 msec 40 msec
7 i-7-0.syd-core04.net.reach.com (202.84.221.86) 40 msec 40 msec 40 msec
8 10GigabitEthernet5-0.oxf-core1.Sydney.telstra.net (203.50.13.33) 40
msec 40 msec 36 msec
9 Bundle-Ethernet3.chw-core2.Sydney.telstra.net (203.50.6.26) 40 msec
44 msec 40 msec
10 TenGigabitEthernet8-1.pit2.Sydney.telstra.net (203.50.20.184) 40
msec 40 msec 40 msec
11 pitt-tcom-r02 (139.130.41.70) 40 msec 40 msec 40 msec
12 * *
snz_icore1_na#
snz_icore1_na#traceroute optus.com.au
Translating "optus.com.au"...domain server (202.170.160.1) [OK]
Type escape sequence to abort.
Tracing the route to optus.com.au (202.139.146.70)
1 lnk1-telstraclear.safenz.net (203.97.21.97) [AS 4768] 24 msec 16
msec 16 msec
2 ge-1-0-0-927.ie1.telstraclear.net (218.101.61.8) 16 msec 16 msec 16
msec
3 ge-0-2-0-1.xcore1.acld.telstraclear.net (203.98.50.251) [AS 4768]
16 msec 16 msec 16 msec
4 203.98.4.7 [AS 4763] 16 msec 16 msec 16 msec
5 i-7-3.syd-core01.net.reach.com (202.84.142.141) 40 msec 40 msec 36 msec
6 unknown.net.reach.com (134.159.126.34) 40 msec 40 msec 40 msec
7 Bundle-Ethernet3.chw-core2.Sydney.telstra.net (203.50.6.26) 40 msec
44 msec 40 msec
8 Bundle-Ether4.ken-core4.Sydney.telstra.net (203.50.6.41) 40 msec 40
msec 40 msec
9 Bundle-POS1.win-core1.Melbourne.telstra.net (203.50.6.22) 56 msec
56 msec 52 msec
10 TenGigabitEthernet9-2.lon42.Melbourne.telstra.net (203.50.79.52) 56
msec 52 msec 52 msec
11 optus1.lnk.telstra.net (139.130.96.90) 52 msec 52 msec 52 msec
12 ge-wan8-1.ue2.optus.net.au (61.88.221.175) [AS 4768] 72 msec 100
msec 136 msec
13 202.139.144.52 56 msec 56 msec 52 msec
snz_icore1_na#traceroute cnn.com
Translating "cnn.com"...domain server (202.170.160.1) [OK]
Type escape sequence to abort.
Tracing the route to cnn.com (64.236.16.52)
1 Gi1-0-418.gw1.akl1.asianetcom.net (203.192.166.65) [AS 10026] 12
msec 12 msec 12 msec
2 ip-202.147.55.210.asianetcom.net (202.147.55.210) [AS 10026] 12
msec 16 msec 12 msec
3 po4-0.cr2.syd1.asianetcom.net (202.147.55.254) [AS 10026] 32 msec
32 msec 36 msec
4 po12-2.gw2.syd1.asianetcom.net (202.147.40.126) [AS 10026] 36 msec
36 msec 36 msec
5 203.103.244.189 [AS 703] 36 msec 36 msec 36 msec
6 so-3-1-0.XT2.SYD2.ALTER.NET (210.80.33.237) [AS 703] 36 msec 36
msec 36 msec
7 0.so-1-3-2.XT2.TKO2.Alter.Net (210.80.49.58) [AS 703] 156 msec 156
msec 152 msec
8 505.at-2-0-0.GW3.TKO5.ALTER.NET (210.80.4.86) [AS 703] 152 msec 156
msec 156 msec
9 docomoaol-jp-gw.aspac.customer.alter.net (210.81.9.106) [AS 703]
148 msec 148 msec 148 msec
10 bb2-tkn-P0-1.atdn.net (66.185.150.50) [AS 1668] 152 msec 148 msec
148 msec
11 bb2-las-P8-1.atdn.net (66.185.152.56) [AS 1668] 200 msec 204 msec
200 msec
12 bb1-las-P2-0.atdn.net (66.185.152.24) [AS 1668] 204 msec 200 msec
200 msec
13 bb1-pho-P7-0.atdn.net (66.185.152.27) [AS 1668] 208 msec 212 msec
208 msec
14 bb2-pho-P1-0.atdn.net (66.185.152.37) [AS 1668] 208 msec 212 msec
208 msec
> On Sun, 19 Aug 2007 10:30:18 +1200, Tony wrote:
>
> >>> oops... that's outsourced to Alcatel..
> >>
> >> Isn't that entirely owned by Telecom?
> >
> > um, no http://www.alcatel-lucent.com/ is probably 100 times the size of
> > Telecom. Telecom is but a small customer.
>
> IF that's the case then Telecom is being operated by morons, goons, and
> idiots.
>
> You should NOT outsource core competancies.
Yeah, but who ever claimed telecom/xtra were competent ?
I wonder if this could have anything to do with the fact that my mate (on
Xtra) just can't seem to get an email to me on either my Orcon or Actrix
addys. We're having to communicate via my trusty old Yahoo account.
Hmmmm.
--
TTFN.
Shaun.
Damn, and now it has gone back to similar to your, 4 hops after it gets
to the Melbourne router.
Traffic to Monash seems to always go via the States as below. Melbourne
is closer to me than Sydney via the Internet!!
You are probably right that about 40ms may be something to do with my
connection to my ISP. I gets >40ms first hop!
Cheers,
Cliff
traceroute to www.monash.edu.au (130.194.11.149), 30 hops max, 52 byte
packets
1 radiostar (192.168.1.253) 0.554 ms 0.475 ms 0.433 ms
2 wn-cisco-r5-lo-5.connections.net.nz (202.49.152.169) 51.028 ms
48.437 ms 49.990 ms
3 wn-sum-1-wnlan7.connections.net.nz (202.49.152.161) 47.486 ms
50.410 ms 48.690 ms
4 wn-cisco-r9-fa-0-0.connections.net.nz (192.100.53.13) 50.053 ms
50.797 ms 52.213 ms
5 p1-telstra-int-pri.connections.net.nz (202.154.157.88) 60.310 ms
64.941 ms 60.588 ms
6 ge-0-2-0-1.xcore1.acld.telstraclear.net (203.98.50.251) 60.867 ms
63.842 ms 60.122 ms
7 ge-0-1-0-914.icore1.acld.telstraclear.net (203.98.42.19) 61.326 ms
60.731 ms 67.200 ms
8 at-0-0-1-300.jb1.wils.telstraclear.net (203.98.42.37) 208.171 ms
203.115 ms 205.719 ms
9 GigabitEthernet5-1.GW4.LAX1.ALTER.NET (157.130.245.21) 195.138 ms
203.906 ms 196.067 ms
10 0.so-2-0-0.XL2.LAX1.ALTER.NET (152.63.53.62) 227.638 ms 200.498 ms
201.252 ms
11 0.so-7-2-1.XT2.LAX7.ALTER.NET (152.63.57.82) 198.771 ms 194.681 ms
195.643 ms
12 0.so-7-0-0.BR1.LAX7.ALTER.NET (152.63.112.153) 198.534 ms 195.064
ms 196.057 ms
13 144.232.18.17 (144.232.18.17) 194.874 ms 195.044 ms 198.059 ms
14 sl-bb24-ana-2-0.sprintlink.net (144.232.8.93) 209.400 ms 207.899
ms 207.657 ms
15 sl-gw28-ana-1-0.sprintlink.net (144.232.1.50) 202.250 ms 199.078
ms 195.374 ms
16 sl-aarne-46055-0.sprintlink.net (144.223.30.26) 233.052 ms 234.927
ms 236.515 ms
17 so-3-1-0.bb1.b.syd.aarnet.net.au (202.158.194.77) 232.599 ms
234.767 ms 231.851 ms
18 so-2-0-0.bb1.a.mel.aarnet.net.au (202.158.194.33) 242.164 ms
244.825 ms 247.274 ms
19 gigabitethernet0.er1.monash.cpe.aarnet.net.au (202.158.200.226)
242.620 ms 244.413 ms 247.876 ms
20 gw1.er1.monash.cpe.aarnet.net.au (202.158.200.234) 243.672 ms
243.158 ms 243.856 ms
21 clay0-gw-v591.net.monash.edu.au (130.194.29.145) 246.432 ms
247.942 ms 242.899 ms
22 clay1-gw-t9-4.net.monash.edu.au (130.194.28.145) 249.753 ms
253.743 ms 248.526 ms
> Lawrence D'Oliveiro wrote:
>> In message <46c6cb96$1...@news2.actrix.gen.nz>, Enkidu wrote:
>>
>>> Jonathan Walker wrote:
>>>> On Sat, 18 Aug 2007 16:41:26 +1200, Mickey Mouse wrote:
>>>>
>>>>> I would think Asia-Pacific is a logical region code, even if domain
>>>>> names aren't assigned along similar lines to the EU.
>>>> Given that internet usage in Asia is growing quickly I think that it is
>>>> now time for IP addresses to be assigned to countries rather than to
>>>> the nebulous "asia pacific" region.
>>>>
>>> That would be difficult because you can have valid addresses in one
>>> country that are apparently allocated to another. This happens when a
>>> large global network provider (with IPs allocated in one country) has
>>> points of presence in another country.
>>
>> But that hasn't stopped most existing IP addresses being assigned by
>> country. And such global networks can cross NIC allocation regions too,
>> so what.
>
> APNIC and the others do not allocate 'by country'.
And yet the files that they make available recording the allocations _do_
record country/region codes for each block.
> Remember John Howard was the visiting
> proctologist for the recent back passage foray looking for Dubya's head.
You Facelift fan, you. :)
Not when that company is outside New Zealand and is complying with the laws of
it's host country.
Have you ever heard of the Mutual Legal Assistance Treaty ?
>Outsourcing a core competency of a company is rarely a good move for the
>companies customers. If Xtra can't do email, well I guess they are good
>at making ads.. nope outsourced.. how about helpdesk.. nope
>outsourced... well network.. no outsourced (to Telecom)... hmm
Plausible deniability ? :)
If you don't actually do anything then you can't be responsible if something
breaks, can you ? :)
> Lawrence D'Oliveiro wrote:
>> In message <46c78dc7$1...@news2.actrix.gen.nz>, Enkidu wrote:
>>
>>> Lawrence D'Oliveiro wrote:
>>>> In message <46c6cb96$1...@news2.actrix.gen.nz>, Enkidu wrote:
>>>>
>>>>> Jonathan Walker wrote:
>>>>>> On Sat, 18 Aug 2007 16:41:26 +1200, Mickey Mouse wrote:
>>>>>>
>>>>>>> I would think Asia-Pacific is a logical region code, even if domain
>>>>>>> names aren't assigned along similar lines to the EU.
>>>>>> Given that internet usage in Asia is growing quickly I think that it
>>>>>> is now time for IP addresses to be assigned to countries rather than
>>>>>> to the nebulous "asia pacific" region.
>>>>>>
>>>>> That would be difficult because you can have valid addresses in one
>>>>> country that are apparently allocated to another. This happens when a
>>>>> large global network provider (with IPs allocated in one country) has
>>>>> points of presence in another country.
>>>> But that hasn't stopped most existing IP addresses being assigned by
>>>> country. And such global networks can cross NIC allocation regions too,
>>>> so what.
>>> APNIC and the others do not allocate 'by country'.
>>
>> And yet the files that they make available recording the allocations _do_
>> record country/region codes for each block.
>
> So what?
So you're wrong.