Daniel Roesen wrote:
Try:
ip -6 route del default dev eth0
and try wether you still get those timeouts.
Ok, I did that. Hmmmm, interesting....
nslookup
www.google.com
159.905296 192.168.0.100 -> 68.54.80.5 DNS Standard query A
www.google.com
164.906050 192.168.0.100 -> 68.54.80.5 DNS Standard query A
www.google.com
164.918972 68.54.80.5 -> 192.168.0.100 DNS Standard query response
CNAME
www.google.akadns.net A 64.233.161.104 A 64.233.161.99
nslookup
www.amazon.com199.788366 192.168.0.100 -> 68.54.80.5 DNS
Standard query A
www.amazon.com
199.800101 68.54.80.5 -> 192.168.0.100 DNS Standard query response A
207.171.185.16
Definitely makes a difference for some (most?) web pages, but not all.
cnn.com for instance took minutes to load, and spewed out hundreds of
dns lines in my ethereal trace.
lynx
www.google.com
620.363071 192.168.0.100 -> 68.54.80.5 DNS Standard query AAAA
www.google.com
620.374913 68.54.80.5 -> 192.168.0.100 DNS Standard query response
CNAME
www.google.akadns.net
620.392936 192.168.0.100 -> 68.54.80.5 DNS Standard query A
www.google.com
620.405477 68.54.80.5 -> 192.168.0.100 DNS Standard query response
CNAME
www.google.akadns.net A 216.239.37.147 A 216.239.37.104 A
216.239.37.99
620.430031 192.168.0.100 -> 68.54.80.5 DNS Standard query AAAA
www.google.com
625.432955 192.168.0.100 -> 68.54.80.5 DNS Standard query AAAA
www.google.com
625.445163 68.54.80.5 -> 192.168.0.100 DNS Standard query response
CNAME
www.google.akadns.net
625.445556 192.168.0.100 -> 68.54.80.5 DNS Standard query A
www.google.com
625.469632 68.54.80.5 -> 192.168.0.100 DNS Standard query response
CNAME
www.google.akadns.net A 216.239.37.99 A 216.239.37.147 A
216.239.37.104
Removing that default route certainly has an effect - but it doesn't
seem to be a consistent one. Does that output help?
(really appreciate you (daniel) and whoever else actually takes the time
to look at this!)
Thanks,
randy