You need to manualy configure the IPv6 DNS servers to use. The servers are 2001:5c0:1000:11::2 and 2001:5c0:1001::194.
In Windows it is easiest to add the servers to the virtual tunnel adapter under Network connections.
I have enabled dual stack on our core network and I can reach v6 island from my lab.
We just deployed a trial commercial v6 DNS resolver in our lab and I'd like to access all google content via v6.
I can access some v6 website such as kame.net via purely v6 client using this resolver. And my dig trace also show that our resolver is doing query on v6 transport properly.
Now, I need to let google white list my resolver address so that I can do AAAA query to google server. I have email google v6 team and also Lorenzo personally how to be white-listed with no reply even after a few weeks.
The plan is to have our internal trial users tunnel thru our lab, point their resolver to our trial DNS server and get surfing experience on v6 transport. Also to conduct more OS and applications related tests over v6 transport thru our own network as our access is not dual stack yet.
Anyone here have any ideas how to proceed? Is Google the only content provider on v6 at the moment?
I stand, myself, corrected. It's working now. I don't know if it took awhile or some combo of things I've done. Freenet6 has been down for authenticated until today sometime. So I was on anonymous. But earlier Google stuff started working in ipv6 anyway. And now that I'm back on authenticated it's definately working.
You can use Wireshark (formerly Ethereal) and capture on your Gogo6 interface and see the actual ipv6 traffic working. On your regular network interface (for most on wired ethernet it will be Local Area Connection in Windows, maybe "eth0" in Linux.) In my Local Area Connection now I see only the tunnel traffic in ipv4. I have to capture on the Gogo6 interface to see the ipv6 web traffic.