* Brian Krahmer (brian(a)krahmer.com) [040306 06:39]:
From: "Brian Krahmer" <brian(a)krahmer.com>
To: "Fedora (E-mail)" <fedora-test-list(a)redhat.com>
Subject: Re: disable IPV6?
Message-ID: <000c01c4030e$49050df0$0200a8c0@WARHOLE>
X-Mailer: Microsoft Outlook CWS, Build 9.0.6604 (9.0.2911.0)
Reply-To: fedora-test-list(a)redhat.com
Date: Fri, 5 Mar 2004 16:02:11 -0800
> Curious why more people haven't reported this. Is it card
> related? Network related? Is IPV6 on for everyone, but for
> some reason it's not causing everyone a problem?
Personally, I would like to see an option in the setup for whether you want
to enable IPV6 or not, with the default being Not. At least, until IPV6
becomes a reality for mainstream users.
I noticed that we are both on comcast. I didn't play around with nslookup
or dig, but perhaps comcast' dns servers are actually returning IPV6
addresses for some hosts. If we're getting v6 addresses, but can't connect
to them because we haven't got a tunnel set up, it would explain the delays,
as it attempts a v6 connection, fails, then falls back to v4.
brian
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
http://www.redhat.com/mailman/listinfo/fedora-test-list
I've found that
ad.doubleclick.net does not properly handle AAAA
queries. The progressively longer timeouts occur until the maximum
number arrive, and the requestor shrugs and continues in ipv4. The
problem is actually with doubleclick. If they'd just fix their
DNS...
--
Derek Tattersall | Accordion, n.: A bagpipe with pleats.
|
dlt(a)mebtel.net |
|
dlt666(a)yahoo.com |