On Fri, 12 Jan 2007 01:47:42 +0100, Rob van der Heij <[EMAIL PROTECTED]> wrote:
>On 1/12/07, Don Russell <[EMAIL PROTECTED]> wrote: > >> Something like this happened a few months ago (or was it years? It's a ll >> becoming a big blur) because the site moved to a new address and it to ok >> a while for the DNS records to get updated....a work around, until DNS >> changes were fully propagated, was to put a "redirect" on the old site .... > >From what I can see here, they removed one authorative name server but >some zone's still list it as such. I'm not sure how DNS resolvers are >supposed to handle that. > >Apart from that, the path to 204.146.134.18 dies somewhere inside >AT&T. And I'm not sure the web server would allow you to address it by >number. > >Rob >======================== ========================= ========== ============== http://204.146.134.18/ did not work from the Bank, either. Same results from my Mac at home. Neither http://www.vm.ibm.com/ nor http :// 204.146.134.18/ work. Traceroute shows, as Rob said, it dying somewhere i nside AT&T -- specifically: ar1-p3110.srcny.ip.att.net (12.123.192.198) 97.955 ms 113.290 ms 113.0 96 ms Unless IBM recently changed the IP address, I would guess that this is no t a DNS issue. Traceroute -n 204.146.134.18 died at the same IP address. Option -n means not to use the DNS.
