Of course after I posted it's behaving tonight.. after almost a week of problems.
Thanks for the 64.233.167.147 IP for google -- I'll use that next time it starts acting up.
Edit: GAH! Moments after I post that, it stops working. (Though manually connecting to 64.233.167.147 works fine) Here's the traceroute.
traceroute: Warning: www.google.com has multiple addresses; using 74.125.19.104
traceroute to www.l.google.com (74.125.19.104), 64 hops max, 40 byte packets
1 10.0.1.1 (10.0.1.1) 4.029 ms 3.801 ms 2.996 ms
2 * * *
3 ge-2-2-ur01.sanmateo.ca.sfba.comcast.net (68.87.198.21) 317.659 ms * *
4 te-9-1-ur02.sanmateo.ca.sfba.comcast.net (68.87.192.18) 104.467 ms 77.665 ms *
5 te0-7-0-5-ar01.oakland.ca.sfba.comcast.net (68.86.90.150) 172.582 ms 239.147 ms 324.084 ms
6 68.86.85.77 (68.86.85.77) 313.120 ms * 343.858 ms
7 comcast-ip.car2.sanjose1.level3.net (4.79.43.134) 332.399 ms 379.020 ms 349.017 ms
8 te-4-4.car2.sanjose1.level3.net (4.79.43.133) 354.420 ms 159.498 ms 282.233 ms
9 google-inc.car2.sanjose1.level3.net (4.79.43.146) 304.527 ms 108.784 ms 107.925 ms
10 209.85.251.98 (209.85.251.98) 95.072 ms 84.991 ms 72.881 ms
11 74.125.19.104 (74.125.19.104) 94.591 ms 265.911 ms 274.751 ms
I don't see any difference between the two.
Neighbor's traceroute (also not much difference):traceroute: Warning: www.google.com has multiple addresses; using 74.125.19.103
traceroute to www.l.google.com (74.125.19.103), 64 hops max, 40 byte packets
1 74.125.19.103 (74.125.19.103) 1.982 ms 1.818 ms 1.901 ms
2 * * *
3 ge-2-2-ur01.sanmateo.ca.sfba.comcast.net (68.87.198.21) 11.942 ms 11.467 ms 22.054 ms
4 te-9-1-ur02.sanmateo.ca.sfba.comcast.net (68.87.192.18) 14.744 ms 11.875 ms 9.355 ms
5 te0-7-0-4-ar01.oakland.ca.sfba.comcast.net (68.86.90.146) 15.363 ms 13.288 ms 16.894 ms
6 68.86.85.77 (68.86.85.77) 18.626 ms 19.239 ms 23.376 ms
7 comcast-ip.car2.sanjose1.level3.net (4.79.43.134) 22.269 ms 23.082 ms *
8 te-4-4.car2.sanjose1.level3.net (4.79.43.133) 207.336 ms 189.872 ms 221.180 ms
9 google-inc.car2.sanjose1.level3.net (4.79.43.146) 19.683 ms 23.279 ms 19.456 ms
10 209.85.251.98 (209.85.251.98) 26.360 ms 25.058 ms 23.406 ms
11 74.125.19.103 (74.125.19.103) 20.459 ms 25.415 ms 19.980 ms
Digs: (+trace timed out on mine)
My modem:; DiG 9.3.4 www.google.com
;; global options: printcmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id: 40327
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.google.com. IN A
;; ANSWER SECTION:
www.google.com. 603391 IN CNAME www.l.google.com.
www.l.google.com. 189 IN A 74.125.19.104
www.l.google.com. 189 IN A 74.125.19.147
www.l.google.com. 189 IN A 74.125.19.103
www.l.google.com. 189 IN A 74.125.19.99
;; Query time: 356 msec
;; SERVER: 10.0.1.1#53(10.0.1.1)
;; WHEN: Mon Oct 8 22:04:13 2007
;; MSG SIZE rcvd: 116
Neighbor's:; DiG 9.3.4 www.google.com
;; global options: printcmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id: 32035
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.google.com. IN A
;; ANSWER SECTION:
www.google.com. 603778 IN CNAME www.l.google.com.
www.l.google.com. 261 IN A 74.125.19.104
www.l.google.com. 261 IN A 74.125.19.147
www.l.google.com. 261 IN A 74.125.19.103
www.l.google.com. 261 IN A 74.125.19.99
;; Query time: 54 msec
;; SERVER: 68.87.78.130#53(68.87.78.130)
;; WHEN: Mon Oct 8 22:04:45 2007
;; MSG SIZE rcvd: 116
Attempt to use
wget on my line:
--22:11:32-- »
www.google.com/ => `index.html'
Resolving www.google.com... 74.125.19.104, 74.125.19.99, 74.125.19.103, ...
Connecting to www.google.com|74.125.19.104|:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.
Retrying.
Curl:curl: (52) Empty reply from server
Using either on the neighbor's line works fine, though wget has this different response:
Resolving www.google.com... 74.125.19.103, 74.125.19.147, 74.125.19.99, ...
Connecting to www.google.com|74.125.19.103|:80... connected.
Just for extra annoyance, trying 74.125.19.104 (which is what it tries to use on my network) works FINE on the neighbors, but trying .103 (which is what www.google.com resolves to on theirs) fails on mine.
And the stupid Airport Extreme won't let me add static routes or clone MAC addresses.
(Anyone have recommendations for a nice router that will, possibly even with link aggregation / failover dual WAN's? 802.11b/g/n might be nice but I can always just use the Airport as a WAP.. their WDS implementation is kinda handy..)