Hi all, As announced<http://googleblog.blogspot.jp/2012/01/ipv6-countdown-to-launch.html>in January 2012, Google will activate IPv6 on most of its services, including Google Maps, on June 6, 2012 at 00:00 UTC. You can learn more on IPv6 at Google here<http://ipv4.google.com/support/websearch/bin/answer.py?answer=1299266&topic=8995&hl=en>. This page includes a link to a website <http://ipv6test.google.com/> to test your IPv6 compatibility, as well as suggested workarounds in case your connectivity to Google breaks on June 6.
*What are the technical details of the change?* In the DNS system, IPv6 addresses are associated to AAAA records, while IPv4 addresses are associated to A records. If your network stack is configured to use IPv6, it will request AAAA records, to resolve domains (e.g. maps.googleapis.com) to IPv6 addresses (e.g. 2001:0db8:85a3::8a2e:0370:7334). Currently, the Google DNS servers won’t return an AAAA record, even if asked for it, unless your ISP is part of the Google over IPv6 program <http://www.google.com/intl/en/ipv6/>. This means that your network stack currently always uses IPv4. On June 6, the Google DNS servers will start returning AAAA records, if asked for them. So if your network stack uses IPv6 in priority over IPv4, the connection to Google services will be made over IPv6. *Can I test the effects of the change now, before it is live?* Yes. You can choose one of these tests to see the effects of the change: 1. Switch to a different DNS resolver (most representative test, but most intrusive): HE’s DNS servers (ordns.he.net - IPs 74.82.42.42 and 2001:470:20::2) are part of the Google over IPv6 program, and currently answer with AAAA and A records for all Google domains. When you configure your systems to use these DNS servers, your setup will be representative of the situation after June 6, 2012. This solution lets you test real Maps API URLs with IPv6 resolution activated. 2. Test connectivity on domains that already return AAAA records 2.1. To test the connectivity from browsers, just visit http://ipv6test.google.com/. This page will dynamically fetch contents from a domain that currently returns AAAA records, and report self-explanatory results. 2.2. To test the connectivity outside of browsers (e.g. Web Services calls made from your application), then you can do a manual analysis: - Connect to http://ds.ipv6test.google.com/ip.js. This URL can currently be resolved with AAAA and A records - If the connections succeeds, you will get such an answer: - ipv6test.setIP('2620:0:1000:3201:226:b9ff:fe77:8de0'); - You can see in this example that the IP contains colons (:), so IPv6 was used for this test. IPv6 will then be used as well, from June 6, 2012, on Google services. Otherwise, you will continue using IPv4 after June 6, 2012. - If the connection does not succeed, this may be due to problems with your home router, operating system, or ISP. For help resolving these issues, visit the Google Help Center.<http://ipv4.google.com/support/websearch/bin/answer.py?answer=1299266&topic=8995&hl=en> *How does this change affect me?* The vast majority of Maps API users won’t notice the change, but if you are using a Maps API with an API Console <https://code.google.com/apis/console/>key, and you restricted the use of this API Console key to a list of IPs, you will need to add your IPv6 addresses, if any, to the list. Thank you for your cooperation as we take this next step forward for the future of the Internet! Cheers Chris on behalf on the Google Maps API team -- G+: http://chrisbroadfoot.id.au/+ Twitter: http://twitter.com/broady -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
