The Internet Archive discovers and captures web pages through many different web crawls. At any given time several distinct crawls are running, some for months, and some every day or longer. View the web archive through the Wayback Machine.
Hi, Just thought I'd let you guys know, I just reported these two bugs: 7612070 Summary: As of Mac OS X 10.6, the system may ignore AAAA records in the DNS. If the system is running dual stack with IPv4 and IPv6, this means that it will use IPv4 to connect. When the bug isn't present and in earlier versions, IPv6 is preferred over IPv4. If there is only IPv6 connectivity no attempts to connect are made. Steps to reproduce: - connect to a network where a working IPv6 router is present - disable IPv4 - point to a working IPv6 DNS in the network settings (such as 2001:1af8:2:5::2) - open ipv4.runningipv6.net in Safari: this should fail for lack of IPv4 connectivity - open www.runningipv6.net in Safari: this should work with no trouble - open www.apnic.net in Safari Expected result: The APNIC website should load normally over IPv6. Actual result: The page fails to load. Workaround: - type traceroute6 www.apnic.net in the Terminal - open www.apnic.net in Safari: now, it will load without trouble Further details: The problem seems to occur with any application that uses the built-in name resolution library calls, including Safari, Firefox 3.5.3 and the command line telnet client. However, it doesn't occur in all situations. It consistently happens or doesn't happen for a given DNS name. Apparently, the problem only occurs when a name points to another name using a CNAME record, not when a name immediately maps to A and AAAA records. The system may also be triggered to exhibit the normal behavior by first forcing a lookup of the AAAA records, for instance, by typing "traceroute6 <name>". The included screenshot shows the result of trying to access Youtube over IPv6 even with the workaround in effect. 7612125 04-Feb-2010 05:30 PM Iljitsch van Beijnum: Summary: When the system only has IPv6 connectivity, iChat will claim there is no internet connection and not try to connect to any IM servers. However, if there is at least one IPv4 address configured on the system, iChat can use Jabber over IPv6. Steps to reproduce: - connect to a network where a working IPv6 router is present - disable IPv4 - point to a working IPv6 DNS in the network settings (such as 2001:1af8:2:5::2) - start iChat Expected result: Attempt to connect to IM servers. Actual result: iChat claims there is no network connectivity. Workaround: Have Parallels installed which creates virtual interfaces with IPv4 addresses. _______________________________________________ Do not post admin requests to the list. They will be ignored. Ipv6-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/ipv6-dev/email@hidden This email sent to email@hidden
