[oclug] re: google

[Adrian Irving-Beer]

On Tue, Mar 29, 2005 at 01:08:57PM -0500, chris h wrote:

> # traceroute www.l.google.com
> traceroute to www.l.google.com (64.233.161.104), 30 hops max, 40 byte packets

Have you 

  * tried just bringing up a web browser on it instead of traceroute,
    or doing 'telnet <address> 80'?
  * tried the -I switch to traceroute?
  * tried one of the 64.233.167.* addresses instead?
  * tried using a web browser on the 64.233.167.* addresses?

Remember, traceroutes can be blocked by any firewall, or have routing
issues of their own.  The best way to see if it's up is to actually try
connecting to port 80, either via a web browser or simple telnet.

Pings, traceroutes, etc., were all designed as basic network
diagnostic tools, and a lot of people respect that, but a lot
also don't.

>  1  192.168.1.1  0.529 ms   0.459 ms   0.582 ms
>  2  * * *
[...]
>  7  * * *
> 
> Definitely pooched DNS on my shub which used to be slnt1 but not sure anymore 
> as I have the new modem which I own and I believe it routes you differently, 
> not checked. 

I doubt that DNS is the problem here.  Traceroutes are all about
routing; if DNS fails, you'll just see numbers instead of names.

Google appears to have changed their IP block to 64.233.167.* instead
of 64.233.161.*, but both sets of addresses still function as Google,
because Google knows that it takes time for DNS updates to propagate.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://tux.oclug.on.ca/pipermail/oclug/attachments/20050329/b999e640/attachment.bin