Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Computer Learning -- Ignore unavailable to you. Want to Upgrade?

To: Gottfried who wrote (49298)	1/27/2006 4:34:59 PM
From: Elsewhere	Read Replies (2) \| Respond to of 110655

Comcast DNS and the 2 DNS listed above all reject the story.news.yahoo.com link Congrats on the legwork you have done so far, I guess now you know more about name serving than you ever wanted to <g> Ok, on the XP command shell I "nslookup"ed the IP of story.news.yahoo.com - I get dailynews.yahoo2.akadns.net or 206.190.35.122 which probably means that Yahoo! distributes its content to Akamai for caching. You can try a nslookup on your machine, too: - If story.news.yahoo.com is resolved to the same IP number as above then we'll have to work from there. You might try a "tracert" with this IP. Here my hops behind the ISP: 8 23 ms 23 ms 23 ms as-1-0.bbr2.Frankfurt1.Level3.net [212.187.128.97] 9 126 ms 110 ms 111 ms ae-0-0.bbr1.Washington1.Level3.net [64.159.0.229] 10 113 ms 112 ms 110 ms ge-3-0-0-51.gar1.Washington1.Level3.net [4.68.121.2] 11 114 ms 113 ms 111 ms 63.210.29.230 12 112 ms 112 ms 110 ms t-3-1.bas2.re2.yahoo.com [206.190.33.95] 13 137 ms 112 ms 113 ms story1.news.vip.re2.yahoo.com [206.190.35.122] - If you get a different IP you can try to access my version, i.e. 206.190.35.122 Please also check the post by d:oug on possible host file manipulations: Message 22107351 investorshub.com

To: Gottfried who wrote (49298)	1/27/2006 5:09:29 PM
From: Elsewhere	Read Replies (1) \| Respond to of 110655

P.S. I went again through your reports and saw your "tracert" to Yahoo! News. Message 22103180 I did a tracert from my site which resulted in the following sequence behind my ISP: 8 24 ms 23 ms 23 ms as-1-0.bbr2.Frankfurt1.Level3.net [212.187.128.97] 9 181 ms 181 ms 189 ms as-0-0.bbr1.SanJose1.Level3.net [64.159.1.133] 10 190 ms 184 ms 183 ms so-14-0.hsa3.SanJose1.Level3.net [4.68.114.154] 11 186 ms 186 ms 186 ms 4.79.58.6 12 191 ms 196 ms 190 ms ten-1-3-bas1.scd.yahoo.com [66.218.82.217] 13 191 ms 192 ms 190 ms alteon14.68.scd.yahoo.com [66.218.69.9] 14 192 ms 185 ms 186 ms story1.news.vip.scd.yahoo.com [66.218.75.230] If you compare it with your version you'll see that your tracert stopped right at the hop before the destination, only the final host itself didn't respond. [Edit - I see that you've found a workaround.]